Ssh2 connect error:
"client disconnect: no further authentication methods available"
Check that you are using a login that is valid on the server machine.
If you don't specify a login name on the command line, ssh sends your current loginID
as the one to try to login as on the server.
Ssh hostname *l loginID
Check that /etc/ssh2/sshd2_config has RequireReverseMapping set to 'no' if the server
doesn't have DNS capability
General Troubleshooting:
Can't connect to site
Are your packets getting TO the site? Is the site responding at all?
/usr/sbin/tcpdump -i eth0 'port 22 and host yourhostname'
You will see what port the client is sending on, and you should see messages coming
back to you at the same port, from the server. If no answer from the server, check
router configurations for both your outgoing ports allowed, and the server side for
incoming/outgoing on your port.
Use the -P flag to request ssh send on unpriviledged ports, otherwise it chooses 1023.
Ssh -P -v -l loginname xxx.xxx.xx.xx
If the ssh attempt hangs on the 'event loop', look at tcpdump to verify that packets
are being sent back and forth.
>>> Ken Scott <[EMAIL PROTECTED]> 01/26 6:32 AM >>>
Hi all.
I apologize in advance for asking about this, because I know it's been
asked before--I've seen it in the archive--but I've never seen an
answer. I've just installed ssh-2.0.13 (Red Hat 6.1, via the RPM), and
all seemed to go well. However, when attempting to connect to any remote
machine, I get nothing but the "no further authentication methods
available" message. I gather this is some sort of client-configuration
issue, but can't figure out what needs to be changed. If anyone could
offer any suggestions, it would be greatly appreciated.
Thanks.
--
Ken,
[EMAIL PROTECTED]
