XP takes too long to logon to domain

[ironique]

I have a small network setup at work with a server running on win2K server and aroung 10 client PCs all running on WinXP pro. The server is setup as a domain controller, users on the client PCs login to accounts I've created for them in active directory.

I have only one problem, it takes almost 2 minutes to login on the client PCs! Copying files to the client PCs from the server also takes too long! It takes me around 10mins to copy a mere 50MB! The network runs at 100mbps - switches and NIC - sure of that. Are these too problems related. Any idea how I can resolve this? Help appreciated.

 

[stash]

Is the client configured to use the domain controller as its primary DNS server? Also if it has an alternate DNS server configured, it should be removed.

 

[ironique]

The client PCs are not configured to use the domain controller as primary DNS, they had an alternate DNS server configured, which I removed as suggested, but the problem still persists. Any other suggestions on what I can do?

 

[stash]

Yes. Point them to the the domain controller for their primary DNS server. Leave alternate blank.

 

[ironique]

Ok stash, did that but it still takes long to logon. Got a suggestion from someone to try setting the NIC transmission speed to 100MBps full duplex manually instead of using auto-negotiate, did that and now copying files across the network is a lot faster. But it still takes ages to logon to a client PC.

 

[BeanDip]

I second Stash's diagnosis. You have a DNS problem somewhere.

The server and the client's DNS should point to the server's IP address.

If the server is not pointing to itself it will not setup the Active Directory records in DNS that the clients need when logging into the network and for looking up computer names.

Check your DNS and you should have a forward lookup zone for your domain. What Server OS are you using? You might have to run the DCDIAG and NETDIAG tools to determine where the problem lies.

 

[ironique]

I Think ur right guys, definately have a problem with DNS. Ran DCDIAG and got this:

C:\Program Files\Support Tools>dcdiag

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site\VMTIGAD
Starting test: Connectivity
VMTIGAD's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(e67d5dc7-3d1f-486b-bd4d-d6519a91de13._msdcs.vmt.igad.com) couldn't be
resolved, the server name (vmtigad.vmt.igad.com) resolved to the IP
address (217.30.18.106) and was pingable. Check that the IP address
is registered correctly with the DNS server.
......................... VMTIGAD failed test Connectivity

Doing primary tests

Testing server: Default-First-Site\VMTIGAD
Skipping all tests, because server VMTIGAD is
not responding to directory service requests

Running enterprise tests on : vmt.igad.com
Starting test: Intersite
......................... vmt.igad.com passed test Intersite
Starting test: FsmoCheck
......................... vmt.igad.com passed test FsmoCheck

C:\Program Files\Support Tools>

Anyone understand that?

 

[ironique]

Ok, fixed it. Set the server's DNS to point to itself like you guys suggested and now the client PCs are logging on almost instantly! Thanx guys, your help is much appreciated.

 

[BeanDip]

No problem. Been there and learned that the hard way too. Now when I hear a problem like yours I immediately think "fix the DNS"

Glad ya got it working