How do I fix error message "The specified domain either does not exist or could not be contacted"?

Upgraded from an old server to a new server and created a new Domain called Company.local (it was the exact same name as the old server) Server name is Company2003 and all workstations are XP SP2 Pro. Each workstation was disjoined from the old domain and joined to the new domain. A new machine was purchased after the install that never saw the old domain so I don't think that is the issue. None of my group policy items are being pushed down. All windows firewalls are turned off.

Here are the three Event ID's that pop up on all machines...

1.Event Type:      Error
Event Source:      Userenv
Event Category:      None
Event ID:      1054
Date:            10/6/2008
Time:            7:40:07 PM
User:            NT AUTHORITY\SYSTEM
Computer:      Computer02
Windows cannot obtain the domain controller name for your computer network. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted.

2.Event Type:      Error
Event Source:      AutoEnrollment
Event Category:      None
Event ID:      15
Date:            10/6/2008
Time:            7:40:23 PM
User:            N/A
Computer:      Computer02
Automatic certificate enrollment for local system failed to contact the active directory (0x8007054b).  The specified domain either does not exist or could not be contacted.
  Enrollment will not be performed.

3.Event Type:      Error
Event Source:      Userenv
Event Category:      None
Event ID:      1053
Date:            10/6/2008
Time:            7:48:01 PM
User:            NT AUTHORITY\SYSTEM
Computer:      Computer02
Windows cannot determine the user or computer name. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted.

I've already already turned the Autoentrollment Settings in GroupPolicy to "Do not enroll certificates automatically" under computer and user configuration. But when we do that they lose all network connections after the reboot!

Plese help!
Who is Participating?
mren08Connect With a Mentor Commented:

Ok so can I clarify.. your clients and servers are using your Linksys router as a DNS server?

DNS is an integral part of Active Directory. Domain services are dependent on SRV records being registered in DNS in order for clients to locate domain controllers, global catalogs and the like.. in fact.. DNS is a pre-requisite for Active Directory installation. DNS should be active and operational on your DC and your clients should really be pointing to the DNS installation on your domain controllers. Your DC's should then be configured to forward DNS as appropriate..
Unless this is a multihomed domain controller, the fix for the below link usually fixes the issue:

Multihomed is simply defined as a domain controller with two or more IPs on it. That can mean a single NIC with two IPs or multiple NICs.
How do your clients get their IP Addresses?
Can you verify that they have the right DNS server addresses?
Do you actually have a CA installed on the network?
Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

mortega1Author Commented:
Hey there ChiefIT thanks for the super quick response, funny thing you mention multiple NIC's... yes it does have two NICs. I just got home so I'll read your link tomorrow when I get to work...

Hey mren08, thank you as well for the super duper fast response... right now we only have a linksys router handling the firewall and DHCP with a DSL connection. The DNS records are in the router and I have all pc's (even thought we have DHCP turned on) setup using static IP's because of the issues we were having. Initially the static IP setup was, SM:, GW: (router IP) and DNS was the same DNS entries that were in the router, but i have since changed it to the router itself, both ways they are able to view the internet and use all network resources. All users were able to login to the domain and get authenticated. But some users had issues with "All applications locking up either early morning or at about 5pm" which is right were the times these Event IDs pop up. The main problem was the owner of the company saying that every evening he had to restart his computer to print via the network printer. I checked his setup and there was a local printer 955 deskjet that was not physically connected but he had it as his default printer. I deleted it and re-installed the network printer. We'll see if that was the issue tomorrow.

Thanks again to the two of you for the super duper responses... I'll keep you guys posted for tomorrow.
mortega1Author Commented:
Hey there mren08, If that's the case, then it's a big whoops on my part! I'll check it out tomorrow. Thanks!
funny thing you mention multiple NIC's

Also on that link is a method to straighten out your DNS SRV records.
You should point your computers to the IP address of the domain controller for DNS (assuming you have already set up DNS on the DC)

mortega1Author Commented:
Even if it doesn't handle DHCP?
ChiefITConnect With a Mentor Commented:

Let's get down and dirty on the problem. The problems you are seeing result from contacting the NIC outside your LAN IP space for DNS resolution.

(Domain does not exist or can not be contacted) usually always means one thing. DNS is having problems.

Let's first tackle the Multihomed Domain controller problems:
On the outside NIC, you must prevent it from registering its DNS records with DNS. Then, you must remove the SRV records of that NIC from DNS. So, in the NIC configuration on the outside NIC, disable "register this DNS connection". Then, remove the SRV  and HOST A records of that NIC from DNS. Then, flush the DNS cache of the server and client.

Step 1) Disable your outside NIC from registering its DNS connection. You do this by going into the NIC configuration>>TCP/IP properties>>DNS tab.

Step2) 2003 server has a quirk in it that will register the SRV records of both NICs when netlogon is restarted regardless of deselecting the "register this DNS connection" in the NIC configuration. To resolve this issue, you have to apply a hotfix.

There is a fix to the 2003 server. It is a patch.
Have a look at this:

Step 3) Once the above patch is installed, you must remove the Outside NIC instance of the SRV records. You can use the following article as a guide.

Step4) You must clean out the HOST A record of the DNS server's outside NIC. You don't want your workstations or servers trying to contact the outside NIC to resolve the DNS server's address.

Step5) clear both the server's and client's DNS cache to make sure no cached entries of that outside NIC are in DNS resolver cache. You do this by IPconfig /flushdns

Step 6) make sure your preferred DNS servers list on ALL NICs is your internal microsoft DNS servers, NOT THE GATEWAY/ROUTER OR AN OUTSIDE SERVER. To do this for DHCP recipients, go to the DHCP server snaping, expand it until you come to a folder called SCOPE OPTIONS. Right click Scope Options and navigate to DNS servers list. Edit that list to only include your DNS servers. For fixed IPs, you have to configure your Preferred DNS server's list manually by going to the NIC configuration>>TCP/IP properties.

Step 7) Make sure your DNS records for the LAN NIC are registered to itself and replicate your changes to other servers. To do so:
Type the following at the command prompt:
IPconfig /flushdns
IPconfig /registerdns
net stop netlogon
net start netlogon

Once the above information is followed, you may wish to force replicate your information from the PDC Emulator to the new DC. Replicating the Host A records and SRV records will allow you to share those records with other DNS servers that may have just come on line. If you do not force replicate from one server to another, it will happen automatically. However, you may have to wait up to eight hours per server. So, you may wish to replicate from your PDC emulator to the new DNS server.

To force replicate, and save yourself time:
a) go to the Active Directory Sites and Services Snapin
b) navigate to Default First Site>>Servers
c)Pick the server you want to replicate TO and expand it
d)right click what is showing (NTDS site?) and select "replicate now"

mortega1Author Commented:
Thanks to everyone that helped! It was a mistake on my part, and once I set the DNS and set everyone's PC to static IP's everything worked like a champ!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.