SSH connection refused from one computer, but not another?

[ouch]

Currently messing around with a new (potential) home server, got Debian on it, and running it headless up in the loft.

Recently reassigned the IP address, by reserving the address against its mac address on my router, which does the DHCP for my LAN.

Rebooted the server, it responds to pings on the new address, however I cannot ssh onto it from my daily windows workstation. I can, however, ssh onto a raspberry pi which I also have on the network, and from that ssh on to my sulky server without issue.

So what's going on here then? I've re-booted my windows workstation, to no effect, I'm reluctant to go messing with ip addresses again, just yet.

Any thoughts anyone?

 

[kanewolf]

What ssh client? Can you clear the key repository? Your ssh client might be confused because the IP address changed but the server is presenting keys it has seen before.

 

[ouch]

Windows client is putty, will look into clearing they keys this evening if I get a chance..

 

[ouch]

Windows client is putty, will look into clearing they keys this evening if I get a chance..

 

[ouch]

Cleared the keys stored in the registry (http://forum.kodi.tv/showthread.php?tid=147781) yet still no joy, also tried:

increasing the 'Seconds between keepalives' parameter...
http://superuser.com/questions/294824/putty-network-error-software-caused-connection-abort

Preventing reverse DNS lookup...
http://serverfault.com/questions/599507/problems-with-putty-while-establishing-ssh-connection-ubuntu-server


Any other ideas?

 

[kanewolf]

OK, since this is windows, do you have more than one login defined on that computer? We could see if it something about your windows login rather than your windows machine.

 

[ouch]

No I don't, but I could set up another login and try that at some point (not for a day or so, the offending computer has been dismantled due to leaky roof above it).
I also tried a different ssh client last night after posting (winSCP) and that connected okay, so I' m fairly sure it's a putty thing.

 

[kanewolf]

No I don't, but I could set up another login and try that at some point (not for a day or so, the offending computer has been dismantled due to leaky roof above it).
I also tried a different ssh client last night after posting (winSCP) and that connected okay, so I' m fairly sure it's a putty thing.

If a different client connected OK, then that accomplishes the same goal as a different windows login. I concur, something in Putty. But, if clearing the keys didn't do it, I don't know what to suggest.

 

[ouch]

I'll try uninstall putty and run CCleaner to empty any other registry keys I might have missed and try again. Assuming the water feature in the conservatory has been fixed and I can re-assemble my computer..
Will post up any developments, but if anyone else has any thoughts, please share..

 

[ouch]

okay, that's weird.

My computer has been disconnected for a couple of days whilst I cleaned up the office area, and re-did some cable management. Hooked it up this morning, and for the hell of it, tried reconnecting to my sulky server.

Bingo, putty connection established!

Thanks for your thoughts Kanewolf
I guess the server in question just needed a bit of time out to think about life and stuff, so now we're talking again and everything is peachy.