M
Matthew Harris [MVP]
Enable keep alives. That'll solve your problem.
support.microsoft.com/default.aspx?scid=kb;en-us;216783
The problem is that some routers/firewalls will close a
socket that doesn't have traffic come across it. Because
terminal services is a low bandwidth protocol, it won't
send any packets across the wire if the connection/user is
idle. Thus, the firewall thinks the connection is dead,
and terminated the socket.
Enabling keep alives will send a heartbeat packet ever so
often to the client to make sure the client is still
there. This will let the firewall/router also know to
keep that socket open.
-M
support.microsoft.com/default.aspx?scid=kb;en-us;216783
The problem is that some routers/firewalls will close a
socket that doesn't have traffic come across it. Because
terminal services is a low bandwidth protocol, it won't
send any packets across the wire if the connection/user is
idle. Thus, the firewall thinks the connection is dead,
and terminated the socket.
Enabling keep alives will send a heartbeat packet ever so
often to the client to make sure the client is still
there. This will let the firewall/router also know to
keep that socket open.
-M