Discussion Locked

Workstations can't join domain

0 helpful
21 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Just when you everything kind of figured out... I created a new domain... created DNS..forward zone, forwarders, DHCP etc. When the new workstations (everything W2K) try joining to domain... can't find domain. Run nslookup...non existant domain. It could be a DNS issue but don't know how to solve it. In DNS, I created my forward zone but I don't have the other folders (_MSdcs,_sites,-tcp,_udp)I expect they are important but don't know how to create them.
All workstations can obtain an address f/dhcp and they can ping the server but can't join domain

21 replies

by widgey woo

Sounds to me like your DNS Zone is not an Active Directory Integrated Zone and it also might not be configured for Dynamic Updates. You need to change your Standard Primary Zone to an AD integrated Zone. It would also be wise to create an AD integrated Reverse Lookup Zone too

by whatme?

No... I don't think so. The (.folder)(root) is not there. That is the first place I looked

by homer simpson instructor at large

is the workstation or server you are trying to join the domain to getting the IP address of the DNS servers in the IP config options. You can check this with an ipconfig /all command. if the DNS options are blank or have the wrong IP...this could be a reason why your workstations can't resolve names. If it is misconfigured, go to your DHCP server and enter the appropriate DNS server options..in Win2k that are scope options 006 DNS server and 015 domain name. Do an IPconfig /release and /renewon the clients...make sure you are doing it as an administrator. Shouldn't make a difference whether it is an Active Directory Integrated zone or Primary....shouldn't matter whether you still have the root zone in there either.

hope it helps
homer

by whatme?

Yes, DHCP is configured OK. When workstations boot they piock up all the necessary info. When I try NSLOOKUP I get error message can't find server or domain... even though ipconfig /all shows server name and all the rest of the correct entries

by d.walker5

I understand your frustration. In your question you say everything is Win2K, but are you running in mixed mode? Are there any NT Server Domains? I am asking because the error ?The specified domain either does not exist or could not be contacted ? occurs most often when a Win2k based computer is unable to resolve the NetBIOS name of the Windows NT 4.0 PDC. Since you can ping you know you have a good connection.

I suggest using WINS to resolve NetBIOS names, make sure that the IP addresses of the WINS servers are configured correctly on Windows 2000-based computers, and that NetBIOS over TCP/IP is enabled.

This should solve your problem.

by d.walker5

I understand your frustration. In your question you say everything is Win2K, but are you running in mixed mode? Are there any NT Server Domains? I am asking because the error ?The specified domain either does not exist or could not be contacted ? occurs most often when a Win2k based computer is unable to resolve the NetBIOS name of the Windows NT 4.0 PDC. Since you can ping you know you have a good connection.

I suggest using WINS to resolve NetBIOS names, make sure that the IP addresses of the WINS servers are configured correctly on Windows 2000-based computers, and that NetBIOS over TCP/IP is enabled.

This should solve your problem.

by curlergirl

It sounds to me like your DNS service is not installed or working properly. The fact that you don't have the auxiliary folders in your DNS zone indicates that something is wrong. You could, as someone else suggested, use WINS for name resolution instead, but not having your DNS zone working properly can cause a lot of other problems down the line, so I suggest fixing it. I think the simplest thing to do would be to reinstall DNS. Here's a link to a Technet article that describes how to do this:

http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B294328

(remove any spaces in the above URL)

Hope this helps!

by whatme?

This seems to be the most logical. It hasn't worked yet but I just know it is my DNS. Thanks
admin@nulas.ca

by Member 29100181

Maybe the problem are very simple - I have similiar problem when DNS on server with Active Directory is not a primary DNS for your workstation. For example if You use more than one DNS server to resolve names, it is suggested to use your active directory DNS server as primary DNS server.

by reference

I agree with answer # 7
First DNS needs to be running and configured properly on server, then workstations need to have server ip as primary dns server. I've seen the error and every time is was because a problem with dns or not primary dns on workstation.
If you installed dns on your server without being connected to the internet it would have considered itself the root server and added a folder named " . " First this needs to be deleted, then rebuild dns. If you still don't get your other folders (msdcs..etc ) try running "netdiag /fix" command (this utility can be found in the support folder on the win2k server cd under tools.
Hope it helps

by mikelazz

I know this might sound dumb, but I still have to ask, Did you run dcpromo to make it a domain controller?

by mikelazz

I know this might sound dumb, but I still have to ask, Did you run dcpromo to make it a domain controller?

This discussion is closed to new replies.