Problems Connecting to a Domain - Possible DNS Problem

Problems Connecting to a Domain - Possible DNS Problem

Hi,

I hope some one can help me with this,

I have 2 computers:


1. Windows 2000 server + SP2
2. Windows 2000 Pro

On the Win2k server machine which I have made a domain controller I have installed and configured the standard things: DHCP, DNS, and Active Directory all the services run fine. When I try to get the Win2k pro machine to join the domain I get this error box:



(Some of you may not be able to see the image as the image code is turned off but the link will work it will open a new window and display the image. This picture is taken from the Windows 2000 site)

I have gone to the link that it says and done what is there but I still cannot get it to join, on the error box it says "This condition may be caused by a DNS lookup problem" the fact that it uses the words "˜may be’ leads me to believe that this is the most common cause and other problems can cause this error.

I also have another domain controller running through the hub but with a different domain name this one is bringing up the same error box, but this one I am not so worried about as I am going to do something else with this.


I will be very grateful for any help or suggestions that are posted.

Thanks

Sparkey

 

How do you have your dns settings set. what is the domain name that your are using in your private network?

 

I went through the install wizard to set DNS up. The domain name I am using is Haze.com (I do not own this domain name at all, I needed a name and the first thing I saw was the air freshener on my desk)

The name of the server: SERVER02
Type: Active directory Integrated
Allow Dynamic update: Yes
Primary server: server02.haze.com
Server IP addresses: 192.168.0.2
Forwards set: None
If there are any other settings you need just say.

Thanks


Sparkey

 

Is your Win2k client picking up the DNS server address if assigned by DHCP (use ipconfig /all to check)? Does nslookup work?

 

And if you have a connection with the outside world, the fact that haze.com does exist can be causing you some problems. Registered out of Tortola in the Virgin Islands.

The standard setup may not have set your server as the root server for your domain (especially if it could see the internet and thus the real haze.com) which could easily cause the problems you are seeing.

 

I suspect that Newt is right

If the server can "see" the haze.com server when it is setup then this will cause all kinds of problems

I suggest re-running DCPROMO to take AD off the server, remove all DNS zones and start again

Its best to do DCPROMO from a prompt, rather than use the configure your server wizard thingy anyway as the wizard is a genius at guessing things to do with DNS etc that you would far rather configure for yourself

 

I will try it and get back to you on that one.

Can I call it some thing like "haze.local" as it is only a local network.

Ta


Sparkey

 

you can call it anything you like 9with a few cavetas that arent important right now)

When running DCPROMO the installer will come back and say it cant find the root server for your domain but will continue rgeardless

Either have the server connected to the internet when you do this or, if you dont, you will need to delete the root zone that it annoyingly creates as it assumes if it cant see the internet you are a root server. Crazy but true