Debugging failed connection attempt.

Debugging failed connection attempt.

[Roland Roberts]

My old ISP has dropped shell support, so I've moved to a new ISP. I've been connecting to news using nntp-open-connection-function nntp-open-via-rlogin-and-telnet and
thought I should only need to change the host information:

(setq gnus-secondary-select-methods
       '((nntp "new-alias"
              (nntp-open-connection-function nntp-open-via-rlogin-and-telnet)
              (nntp-never-echoes-commands t)
              (nntp-via-address "new-shell-host")
              (nntp-address "new-nntp-server")
              (nntp-record-commands t)
              (nntp-end-of-line "\n")
              (nntp-via-rlogin-command "ssh")
              (nntp-via-rlogin-command-switches ("-t" "-e" "none")))))

However, I always get an error when connecting. The " *nttpd*" buffer is empty, there
is no *nntp-log* buffer (with or without a leading space). Additionally, if I run ps
from the shell to see what command is running, it looks fine. I can even cut-and-paste
that command and get dropped to a telnet prompt from which I can open a connection to
"new-nntp-server".

What are my options for debugging this?

roland

Re: Debugging failed connection attempt.

[Lars Ingebrigtsen]

Roland Roberts <rroberts@panix.com> writes:

>              (nntp-open-connection-function nntp-open-via-rlogin-and-telnet)

`nntp-open-via-rlogin-and-netcat' is usually recommended, because it's
more reliable...

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/