Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

XP Very Slow logging into Win2K Domain

Status
Not open for further replies.

NikeGuy23

MIS
Jun 17, 2002
108
CA
I have just updated our PDC from NT4.0 to Win2k. Ever since doing that any XP Box that tried to log into the domain takes anywhere from 1.5 min to 5 min to log in. I have checked our switch setting and set them from Auto to 100mb and it changed nothing. Anyone have any other ideas?
Thanks
 
Take a look at the profiles you're using - that's one of the likely candidates for lengthy logins, particularly if you're using a roaming profile. You'll need to change the "My Documents" mapping to point to a global location instead of a local one.
Shaith
Network Engineer
MCP, Windows XP
 
When we upgraded our network from NT4.0 to WIN2K our WIN2K and XP workstations both became VERY slow to log in. The problem was the DNS server address had changed and we had to correct that to solve the problem. Now they log on better than when we had NT.

 

PBWarrior:

I am very new at this and I have had the same problem. How do I CORRECT the DNS Server address?

We also upgraded and it takes WinXP 2-4 minutes to login to Win2KServer.

Thanks!


Francis
 
Shaith - I am curious as to your comment about the profiles and the My Document settings. What do you mean by having a global location instead of a local one. I would think that by having it local it would be faster however if I am wrong please correct me.
Thanks
 
What a f'ed up problem this is. But finally solved. My issue was when using a hardware vpn client with an XP client behind it (specifically an XP client with a built in wireless card) the login would not be able to find the domain controller or Active Directory. It would take 5 to 45 minutes to boot up. I could ping the domain controller, and it could ping me..."wtf" i said.... some boxes worked but some didn't ...tottally weird. Well well....so check this out...i sniffed the traffic and found that when i was sending my UDP kerberos packets i would not get any response. comparing registry between the machine that worked and the one that didn't found that there was a key that was missing. see microsoft doc Q244474 !!!!!! add that paramaters key, reboot, and it will work. Basically what it does is force that since the UDP packet being sent is larger then 1Byte, switch to TCP and use it... it works!
 
I experienced the same problem. 1.5 - 2 minutes logons. I found that the DNS of the XP machine must be the IP Address of the PDC. Make sure you set up your forwarders properly on your W2K server to use the DNS of your ISP. Logons become normal.
 
I have an XP client on a Windows NT 4 domain.
He keeps getting messages that his roaming profile cannot be found and his local profile cannot be found.

Is there a way to turn this off?
We do not need roaming profiles? GlennA
MIS






 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top