Here is my problem. I am trying to log in to my linux box remotely running Red Hat 9.0. I do a port scan using nmap and it says that port 22 is open with the ssh service running.

I use the ssh client on the linux box itself pointing to it's ip address (192.168.0.30 which is reserved for this machine through by Linksys router) or using the localhost address on 127.0.0.1 and it works fine.

I try using putty on my windows laptop on the intranet and point it to 192.160.0.30 and I get an "Unknown network error". I look at the log on the linux box and I do not see any entries that there was a problem. I know that the putty client on my windows box works because I am able to log in the linux box that I have at home with no problems( Both remotely and locally).

I have configured the router at work to point all requests to port 22 to the linux box I am trouble with. So I tried to point both my laptop from home (using putty) and my linux box (using ssh) to the IP address (it is a dynamic IP address so I keep track of it using DynDNS.org). I get the same "Unknown network error" with putty and the conection times out using ssh.

Any suggestions or troubleshooting techniques would be appreciated. Thanks, Gene

How do you connect from your client to your linux box? From the sounds of the ip addresses, you appear to be on a LAN. Can you ping the linux box from the windows machine?

Yes, I am connected from to a LAN when I connect using the 192.168.0.30 address to start the client on my windows box. I have also tried it from my home.

I believe the networking portion(at least some portion) of it is working because I am using it for a web server that is running apache/mysql. It is function properly from both the internet as well as from the LAN.

I am back at home an will not be able to ping the linux box from my LAN until tomorrow in the morning. If I ping it from my house the router is set up to respond to a ping at the dynamic IP address so that will not tell me anything. Will pinging the linux box from the LAN tell me something that the fact that a functioning httpd does not? If it does I will swing by the office in the morning and try it. Thanks for getting back to me. Gene

I had a similar problem from work, and it turned out that they have some sort of firewall or other security in place which does not allow ssh traffic out. I was able to do it from reflectionx, which is an xterm emulator for winblows, but had to do a runsocks command preceding the ssh command in order to get out. Putty simply will not work, and IT guys told me there's nothing I can do about it.


Point is, it could just be the LAN at your work blocking you. I too run httpd and can, of course, always get to the website from anywhere. It not only uses a different port ( which is allowed out of the network) but obviously different protocols and security measures.

Good luck anyways...