On Tue, 2012-11-06 at 21:50 +1300, Nick Rout wrote: > For a while now I cannot log into my office ssh server from home. I have it > on a non standard port 2022. > > I get "connection refused" > > nick@envy ~ $ ssh address -p2022 > ssh: connect to host address port 2022: Connection refused > > nick@envy ~ $ nmap -PN address > > Starting Nmap 5.21 ( http://nmap.org ) at 2012-11-06 21:45 NZDT > Nmap scan report for address (xxx.xxx.xxx.xxx) > Host is up (0.011s latency). > Not shown: 998 filtered ports > PORT STATE SERVICE > 53/tcp open domain > 2022/tcp closed down > > Nmap done: 1 IP address (1 host up) scanned in 10.97 seconds > > > Work network is a little complex, a Vigor ADSL modem which passes port 2022 > to the WBR-6800 router which passes port 2022 to port 22 on the server. > > It used to work and I can't think that I changed anything. > > How can I diagnose further where exactly the connection is "refused" ? > _______________________________________________ > Linux-users mailing list > [email protected] > http://lists.canterbury.ac.nz/mailman/listinfo/linux-users
ADSL or other network device on the route going to sleep? Had this recently on a site with an ADSL, the problem was intermitent, the connection would come back up if a computer or server would request an update and then I could connect remotely. No firmware update fixed the problem and there was no setting to help with it, so in the end the vendor send another ADSL and problem solved. HTH, Adrian _______________________________________________ Linux-users mailing list [email protected] http://lists.canterbury.ac.nz/mailman/listinfo/linux-users
