Server 2000 problem

Really a wierd problem. I have a server running Server 2000. Installed it about a year ago and everything was fine. We are on a Domain and while everyone can access the server, it takes about 2 to 3 minutes to get logged on after you enter your User ID/Password. Another problem ... after being on line for about 30 minutes if you try and access data/files from the server, eg ... using Windows Explorer and clicking on the file, there is a long delay upwards of a full minute before you see the results of this. It's almost like you have lost connectivity with the server and are trying to get it back again. Rebooting the PC & reestablishing connectivity restores things but only for about 30 minutes. I don't have any perameters on the server set to disconnect users from the network after a certain period of time. Does anyone know if this is a common problem with Server 2000? Microsoft seems to have discontinued support for this product.

Thanks in advance
Rick Goodman

 

Are any of the clients using any drive mappings? Also, after this 30min period, have you tried any ping test? What are the results (before and after is establishes a connection?

Are you running any log on scripts?

To answer your question, no, it's not a known problem with Win2K. You have an underlying issue. How many clients are you talking about?

Scott
http://www.AAApcMechanic.com

 

I would definately run a performance monitor on that machine for the CPU, MEM and DISK IO perhaps connection info too.-

A long login is unfortunately a side effect if you have roaming profiles and many users loging in at the same time like coming to work in the AM.

 

Note that support for Win2k Server hasn't been discontinued at all: http://www.microsoft.com/windows2000/support/lifecycle/

My first thoughts are also with Kodo that it has to do with the number of users logged in or the performance of the server system.

What are the specs of the server, how big is your domain, and what roles does your current server play? It may be worthwhile to move most roles (file and print serving, IIS, SQL, firewall, etc.) to a second server, or to set up a second server as just a domain controller. It might even have to do with LAN speeds. A simple Linux samba server would take care of most file and print serving, and cut the load on the DC considerably.

Try this on a weekend/after hours. Log everybody else off, and then log just one user on. Try to log on a second user after an hour.

Also make sure your server is running SP4 with all applicable hotfixes.

 

Check the lsass.exe on your processes.