Windows 2000 Server and Windows XP

[mcalder]

We have a network with 25 clients, and 1 server with Active Directory on it. We also have several (most) machines running Windows XP. The typical login time for our Windows 2000 machines is approx. 30 seconds from actual login. The typical time for login for our Windows XP machines is closer to around 3 to 5 mins. There should not be this difference when loggin both on to a domain. Something has to be different between the way the server is allowing access to the clients. The server is not running DHCP, WINS, nor IIS. It's acting as a simple server. Has anyone noticed a problem similar to this or know what it could occur or maybe provide a place to start looking?

 

[LiLithTecH]

Have you DISABLED the WebClient Service?

 

[azev]

check DNS and make sure it is working correctly. Most logon problem attributed to DNS is not configured correctly.

 

[azev]

check DNS and make sure it is working correctly. Most logon problem attributed to DNS is not configured correctly.

 

[Nothinman]

check DNS and make sure it is working correctly. Most logon problem attributed to DNS is not configured correctly.

Yes, 9 times out of 10 DNS is misconfigured.

 

[mcalder]

I'll add a little more information I probably forgot to add earlier, don't know if it'll make a difference or not. I am on a University system, so all the DNS is actually done by another server housed at a seperate location. From what I am aware of ISS is not on the machine, but I'll have to recheck it.

 

[Saltin]

It's definetly your DNS then.

You should install DNS on one of your DC's, and then point all machines in the Domain to that DNS server. Have your DNS server forward to the University DNS server youare using now.

Your logon times will improve greatly.

 

[mcalder]

Any idea why this is seems to be only on XP and not the Windows 2000 workstation machines?

 

[Saltin]

The 2k machines are likely defaulting to NTLM authentication, which doesnt require DNS functionality.

The XP machines are likely defaulting to Kerberos authentication, which does require a properly configured DNS infrastructure.