Originally Posted by marko
SSH's verbose mode is showing you the problem when it says
you did this:
Yes - that's the message of concern ....
ssh -v MYHOST
But the syntax that ssh wants is either:
ssh -v username@MYHOST
ssh -v -l username MYHOST
Nope - wrong. The "-l login_name" is optional and the user part of "[user@]host" is optional. That is NOT the problem. The man pages shows thatthe CURRENT local user name is used if none is supplied.
The OP should re-run the ssh command as ...
ssh -vvv MYHOST
and he should also carefully note WHERE i nthe strea mof verbose messages any bit time delay occurs.
I strongly suspect the problem is that his system(s) are trying several authentication methods that are not supported on his systems.
debug1: An invalid name was supplied
Cannot determine realm for numeric host address
refer the the Kerberos REALM. Unless this OP want to use Kereros authentication this is a waste of time.
debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
debug1: Next authentication method: gssapi-keyex
debug1: No valid Key exchange context
debug1: Next authentication method: gssapi-with-mic
indicate that gssapi (sort of a secure RPC based on Kerberos) is being tried.
So for most home users the ONLY sorts of ssh authentication they will ever want is password and public-key. If this is the case ,then the solution is to change the ssh or sshd configuration.
If the OP controls the server (the Ubuntu sshd server) then he can modify the /etc/ssh/sshd_config file.
Adding these lines to the TOP of that file and restarting the server will limit the accepted authentication methods:
Then reboot server or restart the sshd service.
You can also control the Auth order this from the client. On the client you can edit the /etc/ssh/ssh_config file and change the contents to contain this line.