I have a simple dedicated debian server at a hosting facility. It has been happily allowing me to manually enter both username and password for access via ssh for many years as I haven't needed to bother with Public Key Authentication to access the box.
I no longer can login to the system via ssh. I am prompted for my username, which I enter, wait 20 seconds, before I am dropped by my box.
Things i've tried: PuTTY 0.63 from a Windows 8.1 system and ssh OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011 from terminal on an OS X Mavericks install.
The system is responding with: 22/tcp open ssh OpenSSH 6.4p1 Debian 2 (protocol 2.0)
Over the weekend my dedicated server was physically migrated to a new data center and fired back up with the same dedicated IPs. Nothing changed on the box by me before a 'shutdown -h now' was issued in preparation of the system's movement.
The system is back up now and all Apache, MySQL, FTP, and various other services are up and running again. I can access them all with the credentials I have always used, except... ssh.
I have been able to determine the server's time is 4 hours 55 minutes behind EST via timestamps of dummy files placed via ftp and I have synchronized my local system to this time.
I have also started to have the issue that while PuTTY gets a username prompt and then twenty seconds of nothing, the "proper" terminal ssh from OS X Mavericks doesn't get any response at all.
I have a ticket open with the dedicated server company, but this is after having my first ticket closed with "I was able to SSH into your system and after doing some troubleshooting everything seems to be up and working fine." I reopened the ticket as nothing has changed for me.
Anyone have any ideas?