xp client takes a long time to log in to 2003 domain 4

[itharvest]

My XP clients take between 1 and 5 minutes to login to the 2003 domain. THe PCs are pretty similar desktop hardware and software. Is this wait normal or is RAM a factor?

I read somewhere that disabling the webclient service would help, but I worry they won't be able to use the internet properly.

 

[rharmeson]

Are you using Roaming Profile in Group Policy on the Domain? If so, likely the client machines are restoring each of their profiles during the login proces which creates a delay. Of cource, profile size is an issue as well providing you have this enabled.

 

[pagy]

Check the DNS settings on the XP clients. They should be pointing to whichever server does your DNS resolution. Depending on your setup this is probably the domain controller for your domain.

 

[tfg13]

pagy and rharmeson both have the right idea for your issues. I'm leaning more towards pagy's solution, but rharmeson solution should not be overlooked.

Good solution guys!

 

[MarkatLMFJ]

I had a similar problem at one place I was doing some work, the router they were using did have DHCP turned off but was set to do DNS and the person who had configured DHCP for AD put the router as the primary DNS and the domain controller as the secondary DNS machine, when i changed this up things logged in faster.

I agree your GPO settings and Roaming Profiles if your DNS is setup right would be the right place to trouble shoot.

Check out gpresult /v and see exactly what is being applied to the machine once you login.

Mark

 

[itharvest]

THanks for those ideas. I haven't set up any roaming profiles, so it can't be this unless I did it inadvertently, will check on monday.

However, I think the DNS thing could be it. Basically I have a router which does the DHCP and all the XP clients and the server point to the router for primary and secondary DNS server. Are you saying the XP clients should have the DC as the primary DNS, then the router for secondary DNS?

DNS is a hazy area for me. Please spell it out me....

 

[MarkatLMFJ]

itharvest,

I would disable DNS and DHCP on your router completly, setup DHCP and DNS on a Windows Server box that is on your AD and configure DHCP and DNS to work for active directory --- if you do this on a domain controller I think it will do this for you anyway. In your DHCP scope options it to put the gateway as the address of your router and DNS as your server, you can push have it use your router as a secondary DNS if you want but your primary should be your AD box running DNS.

In your DNS zone configuration set your forward and I think your reverse lookups to be the address of whatver DNS your router uses from your ISP, your clients will look at your server for requests, if it doesn't know then your server goes to your outside server to get the request and supply it back.

ML

 

[pagy]

The PCs should only point to your server for DNS.
The server should then be configured to forward all queries it cannot resolve to your ISPs DNS servers.

 

[itharvest]

The DNS server was the problem as Mark and Pagy both pointed out, and I am very grateful for their post. Thanks guys!