Windows XP - 5 Minute Login

[srobinson 0]

I have done a clean install of Windows XP Professional. When I login to my Windows 2000 Advance Server domain it take about 5 minutes to apply my personal settings. Any ideas? Here are my specs:

 

AMD Athlon 800Mhz

Asus K7V

1 gig PC133 memory

Hercules GeForce 3

Sound Blaster Audigy

Linksys Network card

 

All replies are greatly appreciated!

[Atreyu 0]

Assuming you are using DHCP on your network...

 

 

Most likely your problem is occuring as a result of DHCP issues. At startup your XP machine is looking for all the IP information it needs to connect to your domain and the internet etc. If there are any problems with your DHCP settings in either your client or your DHCP server (e.g. your DHCP server is not authorized in the Active Directory), then your XP machine will take forever to start up and allow you to log on. Are you getting stuck where it says "Applying computer settings" or something like that?

 

If so, DHCP configuration is most likely your problem. Try manually entering an IP in your XP machine that would be recognized on your network and see if you have the same problem. If it starts right up, you willknow your problem is DHCP.

[smedegaard 0]

B]HELP[/b]

 

I have the exact same problem but I can't seem to solve the problem.

I have tried to alter the IP number maually but nothing happens. Still that long waiting period. Do you have more possible solutions to this ?

 

Thank you very much in advance

Peter

[Hed 0]

I'm also having the same problem. It takes 5 minutes to login and seems to hang while "Applying personal settings"

[Hed 0]

I found the answer!

 

I had the primary DNS as an outside DNS. Make sure that the server responsible for your Active Directory is the same as the client's primary DNS server. I switched this ONE thing and it fixed it! Instant login now!

[Atreyu 0]

Well, when I was having this problem, it was because my XP machine was having tons of trouble logging into my network (my domain) because it was not talking to the DHCP server. Turned out, I hadn't registered my DHCP server on my Active Directory and that was the problem. It was looking for a DHCP server but couldn't find one. Try playing with your network settings... I'm not sure what else to say, since when I had this problem it was because of DHCP. Your problem may not be the same, but most likely the problem is similar.

[Atreyu 0]

Well if you have active directory installed, then by default you MUST have DNS installed (for the domain). Set up your domain controller (dns server) to not only work for DNS on your LAN, but then set it up to forward requests that are not found in your LAN. That way you can call the DNS server in your DOMAIN, but also be able to get onto the internet etc... as your DNS server will forward you outside of your LAN if your request does not match any of the IPs of your local machines.

[Hed 0]

Ok, futher testing yields more results...

 

I didn't even have my server listed as any of the DNS server. Now it is the secondary one (my ISP's is the primary) and it still works while haveing quick Internet connectivity.

[Atreyu 0]

That might make accessing your local machines a tad slower though since you are searching the web first for the IP of your local machines. The way I have it set up is that my DNS server is first, and if an IP is not found on my 3 machines, THEN it hits the net. But hey.. it might not make a difference. It just seems this way is more efficient.

[Atreyu 0]

Oh and my ISP's DNS isn't even listed in my primary and secondary DNS fields... my LOCAL primary and secondary DNS machines are. I have forwarding set up so they can find what they are looking for if it's not local.

 

yadda yadda.....