Clients can't see new 2003-based domain

[LaraM]

Hi,

I had just set up a 2003 Active Directory server and while trying to add a computer to the domain I got the following error : "domain controller for the [xyz] domain could not be contacted"

This client site uses it's ISP's DHCP for IP resolution and DNS. The name of the new domain is not private (not registered with external DNS). How do I set up DNS to resolve the issue? Set it up on the 2003 server and manually update each client's TCP/IP properties? Or could the issue be resolved via WINS? I never had to do it before, so detailed instructions would be appreciated.

Thanks!
LaraM

 

[ChicagoTechNet]

when you said that "This client site uses it's ISP's DHCP for IP resolution and DNS", do you mean you are using the public IPs? Since you have DC, you should setup your DHCP and DNS. If all computers are windows 2000 or above, you should not need WINS.

Robert Lin, MS-MVP, MCSE & CNE
Windows, Network, Internet, VPN, Routing and How to at

http://www.ms-mvps.com

 

[ljCharlie]

Your client computers should use your domain server's DNS otherwise your client will not see your domain server. You will need to setup your own DNS on your new domain server. I believed you can go to any search engine and search for how to setup dns in windows 2003 server.

ljCharlie

 

[LaraM]

Thanks for your replies. I am leaving IP resolution as it is, so there will be no internal DHCP. With DNS configured on the 2003 DC, I was planning to manually update clients' IP configuration to point to this DNS server as primary, and ISP's DNS as secondary. Will this work?

LaraM

 

[ljCharlie]

I believed it will work as long as your client computer is using your domain server's dns. I have a similar setup on my network as well. I want my client computers to use my ISP IP address but using my own domain server's dns. In this way, my client computers is able to join and see my domain server. However, I believed you know this too, you will have to manually go to each client computer and enter your domain server's dns as primary and use your ISP's dns as secondary. At least this works on my network. Hope this helps!

ljCharlie

 

[LaraM]

Thanks for your help, ljCharlie. This is exactly what I was looking for. I will have a chance to test the settings next week. Will post the outcome.

LaraM

 

[LaraM]

An update: issue resolved with clients set to use local DNS as primary and ISP's DNS as secondary.

Thanks for your help, guys!