Discussion Locked

Time error on windows 2000 server

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am running a windows 2000 server with 6 clients. If we do not keep a program open the server fails to see the users after 16 minutes on the sessions screen. You then have a couple of minutes to open a program or the server times you out and you lose your credentials and have to reboot client to get back on server. I have set the user accounts to no time out limits but it seems the server is timing out the computer not the user. If we leave a program open the server will not time out even though there is no activity. How do I stop the server from timing us out with out leaving a program open and sucking up rescources.

7 replies

by michealirwin

Hi Doug,

You can control hw long a session can stay active, how long it can stay disconnected before being terminated, etc.

Go to the User's Properties Sheet (in Computer Management | Local Users & Groups | Users) and the Sessions tab; it sounds like you need to set your Active Session Limit and Idle Session Limit settings to either "Never" or, if that's what they are now, to something like "1 Day" - there's a drop-list to choose from.

The annoying thing is that it seems like you'll have to do this for every single user, as there isn't an equivalent setting for the groups within which users exist :(

Of course, once you've done it once, you can look at the registry to see what changed and write a .reg script to automate it ...

by douga

I have done that and it does not work. That affects the clients I think not thier computers. I believe that the computers are timing out not the users.

This discussion is closed to new replies.