Connection to host lost - ssh, telnet

[Tom Post]

When I log into a server via ssh(putty) or telnet and run a command on
the server that takes a while to process like rundig, I get the
followingg error after about 5 minutes. (Connection to host lost) If I
simultaneously have another window up just sitting at a unix prompt,
it will not timeout, it only happens when running a script that takes
long to run. This is not isolated to logging into a specific server or
a specific script, it happens anytime I am running something for a few
minutes without user interaction. I tried updating the XP registry and
bumping up TcpMaxDataRetransmissions to 10, and rebooted, but it had
no effect.

Thanks!

 

[Guest]

Hi Tom:

I have a similar post on the same link:

<clip>

Hello:

Trying to do port forwarding to a remote host on a seperate network. I only
have ssh open on the remote network. The firewall on the remote network
translates the following ports for us

XP client
|
|
firewall 2087 port translated to 80 --------IIS host

3389 port translated to 50000 ---- Terminal Server

On the XP client using the Putty utility use port forwarding as well to
complete the connection.

Ports are connecting and I could telnet to the ports.

Here is a Netstat -an showing the ports connected.

TCP 127.0.0.1:1200 127.0.0.1:2087 ESTABLISHED
TCP 127.0.0.1:2087 0.0.0.0:0 LISTENING
TCP 127.0.0.1:2087 127.0.0.1:1200 ESTABLISHED
TCP 127.0.0.1:50000 0.0.0.0:0 LISTENING
TCP 127.0.0.1:50000 127.0.0.1:1199 TIME_WAIT

I reviewed the network policies and the domain is still NT 4.0 my end.
Doesn't appear using gpresults any policies are changing the default
behavior. Also a colleague has tried XP as a stand alone machine and it
fails.

The puzzling thing about this is that Windows 2000 clients can make this
translation without any issue. Also Sun clients do not have a problem. So we
are trying to figure out what is different in XP?

With some expert guidance, I tried the following registry change.

Try disabling the following options on the XP client as a test.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]

"SackOpts"=dword:00000
"Tcp1323Opts"=dword:00000

However, the results were still the same, not able to connect via a web
browser or RDP.

Any thoughts or suggestions are greatly appreciated.

Regards

<end clip>

If you find anything else out - please let me know.

regards,
s