Ok Guys. This problem has stumped me for some time now. Lets see who can come up with the solution.
Im the Net Admin for a cybercafe near where i live. We have 30+ workstations and 2 NT4 servers that do domain logins, fileserving, DHCP, etc. These machines also distribute the config.pol windows policy files. For some time now, we have been seeing some significant delays during all logons and logoffs from the client machines.
Here is a step through of the problem.
1 - Computer is turned on, or logoff is chosen from start menu of a user already logged in.
2 - Wait 15-20 seconds.
3 - MS Networks Logon screen appears (Username, password, Domain).
4 - User types in name and password, hits enter.
5 - User has to wait 15-25 seconds for the login to be verified.
In steps 2 and 5, there is obviously something wrong. it shouldnt take the NT machines that long to authorize domain users. The HD's of the client machines are not busy, so i dont think its some background process causing the delays. I cant figure it out.
Could there be some misconfiguration on the part of Domain Servers? or maybe on the client side? I cant find anything that is out of order. There is also a slight delay when the win98 machines go to network neighboorhood, however, i always just thought that this was win98 looking for broadcasts. Also, a good point to make is that any NT machine i have had on this network logs on and off with no hitch, none at all. Another point is that once the user has logged on, there is very fast network capability (We do gaming, etc.)
Note - we use policies, but not profiles. I wonder if this might be some sort of the cuase of these problems.
Just a thought... you are using just TCP/IP right? How about putting a HOSTS file on one of these machines with the IP address of your server in it? I don't know if that is the problem, but if it is, the HOSTS file should make it much faster. If it doesn't work, just delete the file.
Hmmm... normally, this is caused by the use of Profiles, specifically, roaming profiles. In the case of roaming profiles, each time a user logs on and off, their whole profile (including such directories as Temporary Internet Files, Personal and Desktop) are uploaded (on Logoff) and downloaded (on Logon). The nature of these directories is to sometimes be VERY large, and that upload/download time is normally the time culprit.
But, as you say, you use Policies, not profiles.
Next, what we look at is, exactly where and when the delay is occuring. On the logon delay, are you left with a blank screen for a while, or is the desktop displayed but access denied for a while? Do you run any logon scripts? Do you notice that the delays are more prevalent during busy times of the day, or when there is only one person using the network?
See, what it might be is network traffic. Since the logon process is not a very high priority process, it can get queued for a while. Is the internet connection through BOTH servers, or just the one? If it is just through the ONE server, then that server should be a Member server, and not be responsible for logons. It is very busy replying to internet requests, and would queue a logon request for a while. In the meantime, the other server would sit idly by, waiting for requests.
Just a thought
------------------ Reuel Miller
Windows NT Moderator (yes, that does make me biased )
We run a 100TX network over 3com switches. All have unique real IP's, and we do not control the IP's. The gateway and all TCP/IP internet fucntions are thru the ISP. We only assign IP's thru DHCP.
The PDC does primary logons and DHCP
the BDC does file serving, print serving, and backup logons.
We run no logon scripts, and the delay occurs both Right after you log off, and right after you have finished entering the username/password and hit enter. There is no activity on the local machine, so i see only a problem with the servers.
The PDC should be quicker, becuase it isnt doing much else other than logins and DHCP. I think it holds a time clock that the computer hook up to once a week too, but thats like negligible amount of bandwidth.
Were the machines always slow? Or is this only a recent problem? If it is recent, have you tried deleting all the files in the Temp directory, and all the Temporary Internet Files on each machine?
Also, how often do the PCs get rebooted? Win98 is a fickle beast, and likes to be reset every so often (at least once a day, sometimes twice). NT can soldier on for weeks, and Win2K can go for months without the need for a reboot (MikeV, don't say a word about Linux only needing to be rebooted once a year
).
This is a vexing problem
------------------ Reuel Miller
Windows NT Moderator (yes, that does make me biased )
I run a pretty tight operation. We use Norton Ghost, and ghost down clean images every couple days. On these images, there is nothing extra, registry is clean, no extra startup progs (using msconfig), no temp, cookies, or other.
Everything is as it should on the win98 boxes, i think. Someone suggested that i try a hosts file with the servers and IP's. I dont think this will change, because i dont think its TCP/IP.
Actually, profiles might be slower. In a profile, you download the entire HKEY_CURRENT_USER registry hive, where as with policies you only download a few key registry settings. Not to mention at the directories you download.
You may want to perhaps look at your policy files. If they were created on a Win95 machine, it might be taking them a while to be intergrated into the Win98 system, which is different, as far as policy files are concerned.
Cheers
------------------ Reuel Miller
Windows NT Moderator (yes, that does make me biased )
A forum community dedicated to tech experts and enthusiasts. Come join the discussion about articles, computer security, Mac, Microsoft, Linux, hardware, networking, gaming, reviews, accessories, and more!