D
Dan
Guest
We have 3 2003 Enterprise Edition SP2 Terminal Servers. We are having a
problem with when a user is working remotely and the internet drops. When
the users line drops the session should go to disconnected right. Instead
the session is completely logged off the server.
I have a policy set for our terminal servers in AD to set keep alives and
auto reconnection and we have idle and disconnected session limits of 3 hours
but it logs the session off within 2 minutes after the users loses a network
connection. 2 of these servers are in a load balancing config with session
directory and are experiencing the same issue.
It works fine if the user disconnects the session by clicking on x. So what
gives? Any ideas why the session won't go to a disconnected state is you drop
the network connection?
problem with when a user is working remotely and the internet drops. When
the users line drops the session should go to disconnected right. Instead
the session is completely logged off the server.
I have a policy set for our terminal servers in AD to set keep alives and
auto reconnection and we have idle and disconnected session limits of 3 hours
but it logs the session off within 2 minutes after the users loses a network
connection. 2 of these servers are in a load balancing config with session
directory and are experiencing the same issue.
It works fine if the user disconnects the session by clicking on x. So what
gives? Any ideas why the session won't go to a disconnected state is you drop
the network connection?