Discussion Locked

Network Time Out

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I'm having a problem with a couple win95 pc's timing out on an NT based LAN. When I reboot the machine and attempt to log in for the first time it takes a much longer than on other machines and doesn't map all of the network drives. After that initial login procedure, when I log off, and then back on again I log in fast with everything mapped just fine. The NIC's are running at 100mbs so they should be logging in lightning fast every time.

9 replies

by _degan_

I've seen something similiar. We found some users with roaming profiles who had changed out their desktop backgrounds and cursor themes to make their roaming profiles extremely large (60MB +). This slowed their logins until they were forced to a local profile.

by curlergirl

This problem could be caused by your workstations timing out on name resolution. The reason the second logon is faster is because the host IPs are already in the local cache at that point (the local cache, however, only lasts about 10 minutes). Are you using WINS? If so, first make sure the TCP/IP properties include both primary and secondary WINS servers (even if they're both the same IP address). Second, if this is already OK, try adding a HOSTS or LMHOSTS file to the workstations that arehaving problems. Hope this helps!

by jacky chin

If you do have this WINS server, then you need to check the functionality of the WIN server.
User's roaming profile (if the profile too large in MB) also with cause the similar problem like slow respond for the initial login.
Good luck.

by tmw2001

Here is a 30 second fix that has helped me with logon timeouts countless times...
Add this line to the workstation's lmhosts file to preload the domain controller's info:
[IP address] (space) [servername] (space} #PRE #DOM:[DomainName](enter)

This discussion is closed to new replies.