[fun_gary]

I have recently set up an AD domain controller on a windows 2003 server. The other PCs I have tried see the DC, but it takes them a loooooong time to join the domain and even longer time (about 15 minutes) to log in to the domain after joining. I have AD and DNS running on the main server. Static IP on the server and the PCs are all DHCPd by my router. I have tried static IPs all around, but the same problem persists. Any suggestions would be more than appreciated.


BTW... all units are connected through a 16 port netgear 10/100 switch on a 192.168.0.x network.


thanks in advance,
Derrell Simpson

 

[Mithrilhall]

Are you running any software firewalls on the computers connecting to the domain controller?

 

[fun_gary]

no firewalls running

 

[Rockn]

Are you absolutely sure your AD accounts and DNS are working properly? Windows XK is very dependant on DNS and if name resolution fals you can see there would be a huge lag. Look in the DNS admin and make sure it is caching all of the connections from the clients and registering their names. Have you also defined the DNS server in the IP configuration on these clients with a computername and a domainname.com??

 

[fun_gary]

yes and yes, and possibly yes if there are three questions there. But still getting the same latency. Im getting stumped here. thanks for the suggestions though!!

Derrell

 

[Rockn]

You never did state what your network clients were. Have you also tested all of your cabling?

 

[fun_gary]

I have tried two windows XP boxes and a laptop which had 2000 pro. Im sure the cabling is ok as i have no trouble transferring data in peer to peer. might try a crossover between two though and see what happens....

thanks for the reply..

Derrell

 

[steve65]

First of all I would suggest using the WIN 2003 DHCP server to assign your IP addresses. When you use the Windows box to assign your IP addresses, it will automatically update DNS for better connections.

Make sure that you have the proper A, SOA, and NS records configured in DNS referencing your domain controller. Win 2000, and XP rely on these to tell them who the local domain controller is. If these are not correct it will definitely cause problems in your logins.

If you are going to use the router to assign addresses, make sure that you are correctly pointing the clients to your internal DNS server. (by default the router will point to itself as the DNS server)

Finally, if none of that helps, add the domain controller to the HOSTS and LMHOSTS files on one of the client machines (C:\windows\system32\drivers\ect) add the IP address and names at the top of the file. For LMHOST file, add it in this format.

<IPADDRESS> <servername> #PRE #DOM:<domain_name>
<IPADDRESS> "<Domain_Name >0x1b" #PRE

Note add spaces after the domain name to equal 16 spaces total.

Steve