Questions about joining a domain 4

[jshurst]

I've set up a new domain controller using the manage my server wizard. I've also given it a static ip address under Network connections->Local Network->TCP/IP. I have my router handling DHCP and the router looks to my domain controller (and it appears to look for my ISP for DNS). Under the DNS manager I created 2 A Hosts in each forwarding zones to point to my ISP's dns (hopefully I did this correctly).

So my question is why can't I join my domain? It says that the domain can't be located. I can ping my server using it's name from my client, however I can't ping the FQDN. I can also ping my pc by name from the server. I have also turned off my firewall, so I don't think that is the issue.

Also, should I be letting the DC handle DHCP as well? Is there something else that I need to do here?

Thanks in advance,

J

 

[Talisa]

I am certainly no expert by any stretch of the imagination. I am more like an a Novice Dummies for Windows 2003 Book. I had a similar situation once, and there was several things I had to check.

Enusre under the DNS setup information for the PC that it does not show as having an additional .co.uk or whatever on the DNS Suffix. When I had a similar problem it turned out to be mydomainname.co.uk and then .co.uk again on the next line down.

Can you ping the PC (ping etc -a)by both name and IP address (Forward and Reverse?). I am no expert but sometimes it can be something really stupid.

When you attempted to join the PC to the domain, did you get as far as the enter account details of someone who has priveledges to add the PC or is it at that point it fails?

Regards

Toni

 

[jshurst]

Everything looks good there. I can ping each way. The error is the following.

"An attempt to resolve the DNS name of a DC in the domain being joined has failed. Please verify this client is configured to reach a DNS server that can resolve DNS names in the target domain.

 

[DgtlLgk]

As it seems ur problem indeed is the DNS(local).Since u have a local DC u should install also a DNS!!Isnt it??So most probaply u have to say to ur clients which is ur local DNS(either by declare it to ur DHCP or type it in ur TCP/IP properties on each client,give them static ip settings if they arent too many)

 

[porkchopexpress]

Ok first i would recommend running DHCP on your Windows server that way you can take advantage of dynamic DNS. You need to specify your ISP's IP address in the forwarders tab not by using an address record. Finally your clients need to point to your Windows DNS server for name resolution as this will tell them how to locate your Active Directory so thay can join the domain.

Take a look at this link.

http://support.microsoft.com/kb/323380

When you are the IT director, it's your job to make sure the IT works. If it does work they know already and if it doesn't, they don't want to hear your pathetic excuses.

 

[LWComputingMVP]

To put it another way, DHCP does NOT have to run on your server... but it really makes little sense having it run on the router. The server has a much easier graphical interface and is almost always more configurable. You don't need to use Windows DHCP to take advantage of Dynamic DNS, but it can make things easier.

All your clients should be pointing to ONLY the Windows Server for DNS. Likewise, the Windows Server, in it's network settings area, should ONLY be pointing to itself for DNS. The Windows DNS server itself CAN (but typically doesn't have to) point to your ISPs DNS as DNS Forwarders.

For more information and my favorite link, "10 DNS Errors That Will Kill Your Network", see my web site under Common Problems and Troubleshooting.

http://www.lwcomputing.com/tips/static/dns.asp

 

[jshurst]

Thanks to everyone for the advice and the links. I wound up using my server for DHCP instead of the router and everything seems to be working fine now. I guess it was a problem with the router.

Thanks,

j