Slow logon to domain
Windows 2000 server is set with Active directory in pure (non-mixed) mode. This is a small network with less than 10 users. There is only one 16 port 10/100 switch, not a lot of traffic. When logging on with Windows 2000 Pro SP1, the workstations take a really long time during the Loading Personal Settings part.
Windows 2000 server is set with Active directory in pure (non-mixed) mode. This is a small network with less than 10 users. There is only one 16 port 10/100 switch, not a lot of traffic.
When logging on with Windows 2000 Pro SP1, the workstations take a really long time during the "Loading Personal Settings" part. Is there a way to speed this up?
When logging on with Windows 2000 Pro SP1, the workstations take a really long time during the "Loading Personal Settings" part. Is there a way to speed this up?
Participate on our website and join the conversation
This topic is archived. New comments cannot be posted and votes cannot be cast.
Responses to this topic
The other reason I really want DHCP is I work on repairs off this network, and need to plug random computers into the LAN and get internet access without a whole lot of setup and reboot issues. With DHCP, most machines just boot with internet access immediately and I can download patches, virus defs etc. A brand new Win98se install can download up to 50+mb from the Windows Update web site. Wouldn't want to do that with a modem, so the DSL works out very nice.
Win2K is a little lighter on the patches, but either way, any machine I work on typically needs the access for a little while.
Thanks to all for your help. I must say it did NOT seem like an intuitive solution, because it appeared to me that there was a hangup on the profile, and pinging the server seemed instantaneous. Internet access was fine for all machines, and browsing the network seemed OK as well.
Sigh. So much for intuition...
Win2K is a little lighter on the patches, but either way, any machine I work on typically needs the access for a little while.
Thanks to all for your help. I must say it did NOT seem like an intuitive solution, because it appeared to me that there was a hangup on the profile, and pinging the server seemed instantaneous. Internet access was fine for all machines, and browsing the network seemed OK as well.
Sigh. So much for intuition...
I had the same problem but a different cause. The clients were looking to the DC and because I have DNS forwarding in winroute on, it sent the DNS query to my isp's DNS server. Fixed it by stopping winroute, stopping the dns service, then restarted the DNS service. Then restarted winroute and that fixed the problem.
