Client Connection Timeout Settings

[Guest]

Windows XP users connect via RDP to a Windows 2000 Terminal Server session.
They are getting disconnected after 20 minutes of idle time. I checked the
terminal server configuration under the Sessions tab and end a disconnected
session, active session limit, and idle session limit are all set to "Never."
Override user settings is checked for these 3 options and for "when session
limit is reached or connection is broken." If these settings are enabled,
how could a user's session become disconnected after only 20 minutes? Are
there settings somewhere else that could be overriding the server settings?
Our company implemented a new fireall configuration in our data center over
the weekend. Could that have effected these timeout settings? We are not
losing the local area network connection in our office anywhere. Please
advise.

 

[Robin Walker]

Windows XP users connect via RDP to a Windows 2000 Terminal Server
session. They are getting disconnected after 20 minutes of idle time.
I checked the terminal server configuration under the Sessions tab
and end a disconnected session, active session limit, and idle
session limit are all set to "Never." Override user settings is
checked for these 3 options and for "when session limit is reached or
connection is broken." If these settings are enabled, how could a
user's session become disconnected after only 20 minutes? Are there
settings somewhere else that could be overriding the server settings?
Our company implemented a new fireall configuration in our data
center over the weekend. Could that have effected these timeout
settings?

You do need to talk to your firewall people. Maybe they drop these
connections. Were there connection problems before the firewall
reconfiguration?