Session disconnecting from terminal server

I am connecting through a MN-500 base station via XP Pro
remote desktop to a Win2K terminal server session. My
session keeps timing out when inactive and I have to sign
in like 20 times a day and it drives me nuts. If I'm on
the phone for 10-15 minutes with a customer and I then
need to access the server database to answer one of their
questions, I have to make them wait while I re-connect
and although it's only a minute, it's clumsy.
I haved checked the server's terminal service
configuration and all the idle session/timeout settings
are set to "never" and other clients are not experiencing
the session timeouts, so I suspect that my base
station/router is the culprit. I have gone through all of
the base station management tool settings and cannot find
any obvious way to correct this. Apparently (according to
a tech doc I read elsewhere online) routers will close a
socket when it doesn't detect any activity and terminal
server is a very low bandwidth connection...help?

You could setup persistent port forwarding which would stop the router
from closing the port on you.

Darren wrote:

> I am connecting through a MN-500 base station via XP Pro
> remote desktop to a Win2K terminal server session. My
> session keeps timing out when inactive and I have to sign
> in like 20 times a day and it drives me nuts. If I'm on
> the phone for 10-15 minutes with a customer and I then
> need to access the server database to answer one of their
> questions, I have to make them wait while I re-connect
> and although it's only a minute, it's clumsy.
> I haved checked the server's terminal service
> configuration and all the idle session/timeout settings
> are set to "never" and other clients are not experiencing
> the session timeouts, so I suspect that my base
> station/router is the culprit. I have gone through all of
> the base station management tool settings and cannot find
> any obvious way to correct this. Apparently (according to
> a tech doc I read elsewhere online) routers will close a
> socket when it doesn't detect any activity and terminal
> server is a very low bandwidth connection...help?