Tom Diehl on 5 Mar 2004 06:54:02 -0000 |
On Thu, 4 Mar 2004, kaze wrote: > When I ssh over the Internet from home to this Linux box I'm setting up as a > SpamAssassin server elsewhere the session just hangs there, and will > timeout. > > If I remotely access a Windows box at that same location and ssh with the > Putty client to the box I'm one router hop away and can log in fine. Once > this ssh session (from the Windows box at the same location) is up, the > original one from home directly to the box will work - even if I start the > one from home first it just hangs there, but once the local one logs in the > remote one pops up with the logon prompt. > > What's going on here? Is this by design or just some weirdness? Could be several things. Is port 22 open through the firewall/router? If using NAT is port 22 forwarded to the machine you are trying to reach? What do you see if you do ssh -vvv machine_name? Is it even trying to connect or is something blocking it. If you have the lft program try lft -d 22 machine_name. See where it craps out. Just because windoze remote desktop works does not mean ssh will. Windows remote desktop uses port 3398 by default. ssh uses port 22. HTH, Tom ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|