On Tue 06 Nov 2012 21:50:09 NZDT +1300, Nick Rout wrote: > nick@envy ~ $ ssh address -p2022 > ssh: connect to host address port 2022: Connection refused
> It used to work and I can't think that I changed anything. Something *did* change. > How can I diagnose further where exactly the connection is "refused" ? Only by examining each node in the network. Start with the target host (ssh server). tcpdump is good, as that ignores any packet filter stuffups, which may not necessarily get logged to syslog. Next is the consumer junk in between. Do you have admin access? Check their logs. Run tcpdump on them - oh, never mind. Many of those make it hard to save configurations, but happily run on RAM config for months - then they get powercycled, and drats, problem exists. Always test this junk with a poweroff after any config change. Volker -- Volker Kuhlmann http://volker.dnsalias.net/ Please do not CC list postings to me. _______________________________________________ Linux-users mailing list [email protected] http://lists.canterbury.ac.nz/mailman/listinfo/linux-users
