Windows Forum

Ask something
Discussion Locked

Domain name is invalid or doesn't exist

0 helpful
11 replies

by curtisinterruptus

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a single domain controller on my Windows 2000 network. When I try to add a computer to the domain, I get the following message, "The domain name "xxxx.com" is either invalid or does not exist". I recently lost my SYSVOL share, but now with MS's help, have it restored, however, my original problem still exists. I can't add computers or servers to the current domain.

11 replies

by cg it

A particularly troublesome problem. Defeats the purpose of having a network. Is the sysvol volume shared? [Has to be shared] A few questions, What server O/S? NT? W2K? Are you using Active Directory? have you tried logging in to the domain on a client computer using the admin account. Check the event viewer for log on event errors. Sometimes that will tell you what the problem may be.

by cg it

To answer your question about removing AD, actually no it won't cause you more problems because you don't have a DNS server running and as Tim said, incomplete AD installation. Configuring your server as a DNS server in W2K isn't such a big deal. Open admin tools then go to "configure your server". Under networking, click on DNS. The Confgure New Server wizard will start and just follow the prompts. Once you have your DNS server configured, then install AD. Create the user accounts you want. Then those users can "log on" to the created domain.

by curtisinterruptus

Yes, I finally had to contact MS support, but the sysvol is shared.
The server is Win2K and all clients are Win2K Pro.
Yes, the server in question is the domain controller and it is running Active Directory.
Yes, I can log in as admin on a client.
The only error in the event log right now involves the System Log and it is 5774 NETLOGON errors.
I currently do not have a local DNS server running. Was asked to try and get it going, but I cannot get it to install.

by timwalsh

DNS is your problem.

Active Directory requires access to a DNS server that accepts dynamic updates.

This means that Active Directory essentially needs a local DNS server in order to work properly. When Active directory is installed it makesnumerous changes to the DNS server (adds several new resource records) that hosts your domain. Thes records basically tell every computer searching Active Directory where the Domain Controllers are.

If you are trying to use an ISP's DNS server, than chances are very good that it rejected all the changes that Active Directory tried to make. While the version of DNS the ISP uses may be capable of dynamic updates, no ISP is going to allow these updates to be added to their DNS tables or they would quickly be overwhelmed.

Essentially you have an incomplete Active Directory installation.

At this point, the following needs to happen:
1. Since you AD installation is not working properly anyway, I would run dcpromo to remove AD fromyour server.
2. You need to install a local DNS server.
3. After installation of DNS, point your server to itself for Primary DNS.
4. In order to be able to reach the Internet, you need to specify your ISP's DNS server as a forwarder (DO NOT enter your ISP's DNS as the Alternat DNS server in TCP/IP properties).
5. Run dcpromo again (to reinstall AD). When asked specify your DNS server as the hosting your DNS zone.

DNS-wise, essentially what happens is that all AD-related local DNS queries (to include the location/identity of DCs) will be resolved by your DNS server. All DNS queries for resources outside your domain (i.e. for the Internet) will be forwarded to the ISP's DNS server for resolution.

Hope this helps.

by curtisinterruptus

Thanks Tim! It looks like a nasty job, but I can follow those instructions pretty well. Thanks for all the emails and the time you spent!

Curt

by curtisinterruptus

Comment for tim.walsh@cos.sparta.com on Answer 2: If I remove my only AD, isn't this going to cause me a bigger problem, or can it be restored?

by maharajv

I agree with Tim Walsh. DNS is difinitely the issue. You client cannot contact a DNS server to query the GC for the domain controller of that domain that you want to join. Install DNS, setup the forwarding rules, and you're away. AD relies, if not totally, then mostly on DNS to function.

by curtisinterruptus

concerning: Comment from DR The Corporate Groups on 12/3/02:

You say removing the AD won't be a problem - OK, then you mention manually re-adding my users. If I have to do this manually for several hundred users, computers and servers, I would say this qualifies as a LOT OF WORK! As I have said, I am a rookie with AD, but is there not a way to restore all these settings once I have setup the DNS service without having to manually add each one? I think I am going to faint!

Curt

This discussion is closed to new replies.