How about checking your mtu? I've had very strange SSH behavior with MTU too large. Try setting 1300 or so.
On Wed, Jan 7, 2009 at 11:29 AM, John Summerfield <[email protected]> wrote: > Mirko Vukovic wrote: > >>> >>> Check tcp_wrappers (/etc/hosts.allow and/or /etc/hosts.deny) and iptables >>> for rules that deny access to remote networks but not local networks. >> >> /etc/hosts.allow and hosts.deny do not list any machines whatsoever. >> Is that OK? Maybe this stuff is in another file? >> >> As for iptables, I tried two or three times to read the relevant >> chapter in RH Unleashed, and never got the concepts straight (I was >> not trying very hard though). Maybe I should try again. > > iptables isn't likely to cause this problem; if you block the packets sshd > won't see them, and your client will either timeout or get "connection > refused." > > > >> >>> I'd also verify that you are using the correct username from your laptop. >>> If you aren't supplying one, it will likely default to the xp username. >>> If >>> that user doesn't exist on the RH box, you'll get a Permission denied. >> >> I guess that is the equivalent of `is the power on'. It is :-) >>> >>> Hugh > > Try putty. It's another Windows ssh client, the one I generally use as it > doesn't require any other software. > > > -- > > Cheers > John > > -- spambait > [email protected] [email protected] > -- Advice > http://webfoot.com/advice/email.top.php > http://www.catb.org/~esr/faqs/smart-questions.html > http://support.microsoft.com/kb/555375 > > You cannot reply off-list:-) _______________________________________________ rhelv5-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/rhelv5-list
