Christopher Copeland wrote: > > On 27 Nov 2007, at 10:19, Mick wrote: > >> Hi All, >> >> I have noticed this problem when I try to connect to two different >> machines in >> two different continents. One is on cable (US) the other on ISDN ADSL >> (Greece). In the evening and sometimes weekends ssh connections from my >> laptop to these two PCs are either taking ages or time out. This is ssh >> connections to sshd which is listening to random ports in the 200+ or >> 12000+ >> ranges. If I eventually manage to connect the latency is ridiculous >> - up to >> 5 seconds! Sometimes I enter a passwd, if I can get that far and >> then wait >> for hours with no response. Eventually, I have to close the terminal. >> >> Tracerouting does not get through although some clever tcptraceroute >> strings >> may on occasions (intermittently) get through. >> >> Both servers run on domestic networks. BTW, ssh-ing to servers in >> datacenters >> with their big fiber-optic pipes, although relatively slow in peak >> times, >> always gets through. >> >> The strange thing is that there is no problem talking to these boxen >> while >> they run Google-Talk, it's only the ssh connection that seems to suffer. >> >> Have you come across such a problem before? How can I troubleshoot >> it? In >> this day and age of broadband connections it seems strange to get worse >> performance than on a dialup network . . . I mean I have run VNC >> connections >> over a 56k dial up with more responsiveness than this! >> -- >> Regards, >> Mick > > I've run across the same kind of issues on certain ISPs when using > non-standard ports for sshd. Given other connections (Gtalk) are > working, the first thing I would try in your position is to see if > there is a difference when using 22 versus your random port. With > certain ISPs in the UK I've found SSH connections to be unusable on > anything but the default port. Of course it has everything to do with > the "smart" traffic shaping at the ISP and there was nothing I could > do about it. > -- > Christopher
I also ran into something like this on a local network. I corrected this by adding the remote systems to my hosts file and putting the entry in the host file on the remote system. I'm not sure what affect this had but it worked like a charm after that. I guess it lets each other know who the other is or something. Hope that helps. Dale :-) :-) :-) :-) -- [EMAIL PROTECTED] mailing list
