We have a client that has a Win2K server running TS and we are using the Windows Remote Desktop client to access their server and do work for them.
We can connect just fine. But after about 5 minutes of inactivity (if the RDC session is minimized and something else is done on the machine), the connection drops out.
We are on a *very* slow network (128K frame relay shared by 16 active computers).
We initially were using the ActiveX web interface to it, then moved to using the XP Pro version, and then moved to using the Win2K3 version (is newer and has a few new features). We used one feature that says that it will "Reconnect if connection is dropped."
Still have the problem.
I have seen mention that it is likely due to a router somewhere along the way that sees no activity on the line and cuts the connection to conserve resources - and then apparently if "KeepAlives" are activated on the server, that will send a heartbeat out to us and the router will see that the connection is still alive and not kill it.
Supposedly the server admin has activated these (he hasn't gotten back to me today and he keeps recommending I try things that are only issues if you can't login at all).
I have also read that the KeepAlive setting in the registry doesn't always fix it - this is what I'm worried about.
I have done all I can on this side (even adjusted timeouts on our firewall in case that was the issue - no help), and I'm not sure what else to try.
Has anyone else had this issue - if so, did you resolve it? How?
Any help would be greatly appreciated.
We can connect just fine. But after about 5 minutes of inactivity (if the RDC session is minimized and something else is done on the machine), the connection drops out.
We are on a *very* slow network (128K frame relay shared by 16 active computers).
We initially were using the ActiveX web interface to it, then moved to using the XP Pro version, and then moved to using the Win2K3 version (is newer and has a few new features). We used one feature that says that it will "Reconnect if connection is dropped."
Still have the problem.
I have seen mention that it is likely due to a router somewhere along the way that sees no activity on the line and cuts the connection to conserve resources - and then apparently if "KeepAlives" are activated on the server, that will send a heartbeat out to us and the router will see that the connection is still alive and not kill it.
Supposedly the server admin has activated these (he hasn't gotten back to me today and he keeps recommending I try things that are only issues if you can't login at all).
I have also read that the KeepAlive setting in the registry doesn't always fix it - this is what I'm worried about.
I have done all I can on this side (even adjusted timeouts on our firewall in case that was the issue - no help), and I'm not sure what else to try.
Has anyone else had this issue - if so, did you resolve it? How?
Any help would be greatly appreciated.