Discussion Locked

Very slow WINNT network login.

0 helpful
10 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Some of the PCs I support (WINNT Workstation) are very slow to login once they get to the WINNT login (DOS) window. They just sit there and do nothing for about 2 or 3 minutes then finally complete the login and everything works normal. I've checked the start-up folders in all profiles and tried looking in the registry for problems to no avail.

10 replies

by syscokid

Don't know how big your organization is but here's our scenario. My BDC is in my local office in Massachusetts. My PDC is in New York. Sometimes at login the workstation can't find the BDC so it goes to the PDC to log in. We can tell which serveris running the logon.bat because it's in the title of the DOS windows. This results in the slow login time like you're experiencing. The workstation then "remembers" this connection and continues to authenticate there. A reboot usually solves the problem because the ws now finds the BDC again.

by stillatit

Take a look at where the login script is coming from and ask yourself how the workstation finds the computer with the script.

From the delay time you are falling back on DNS, and the first DNS server in the computer's list is bad, causing it to time out before finding the second entry.

If you have Netbeui enabled, have a specific entry for the computer with the script in the LMHOSTS file of every workstation. The entry should have the #PRE tag.

If you are only using tcp/ip, put an entry in the HOSTS file for the computer with the script. Also, check that every DNS server in the list the workstation is using is actually a working DNS server which is reachable from that workstation.

Good luck.

by stillatit

Another thought: Read the script and see what is being mounted. The workstation needs to find each of those machines as well, and they will need LMHOSTS or HOSTS file entries to make it easier.

by mbraffor

Try releasing the Ip address with "ipconfig /release" and see if that helps in finding a differing DNS #.

by arniej

One cause of this could be a large profile folder. Check the size of the profiles that your workstations are downloading when you log on. If you use a proxy server and shared Internet connection, check that the Temporary Internet Files aren't being cached to the profile, then being written back to the server when people log off. The more they surf the bigger the profile gets!

This discussion is closed to new replies.