The specified domain does not exist or could not be contacted.

I took over an office, that had a 2000 Server and a 2003 Server. The 2003 Server was suppose to be the domain controller, and we found that it wasnt. I went through all the steps to migrate from a 2000 Domain to 2003. I transfered the FSMO roles, and seized ones that werent able to transfer. So i took down the other server, and now the new DC when I double click users and computers. I get a message

Naming information cannot be located because:
The specified domain does not exist or could not be contacted.

I searched for the error and could be something with Group policy problem, so i ran dcgpofix. I got errors on this.
Any suggestions?
TJacoberger1Asked:
Who is Participating?
 
e_vanheelConnect With a Mentor Commented:
So all is good??
0
 
KCTSCommented:
Sounds like a DNS issue - make sure that the clients are pointing to the new DC/DNS server as their preferred DNS server
0
 
TJacoberger1Author Commented:
I'm getting this message on the DC, when I open up Active Directory users and computers.
0
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

 
bkellyboulderitCommented:
Have you pointed DNS on the servers NIC back to itself, and flushed/re-registered DNS?
0
 
e_vanheelCommented:
Look at the following:
- Is DNS installed on the 2003 box?
- Is DNS setting on the DC point to itself?
- Does the _msdtc subzone in DNS contain the srv record accounts that point to the new DC?
- Do you have a Global Catalog configured (Active Directory Sites and Services)
- Do all the computers point to the same DNS servers
- Is the DNS Zone configured to be Active Directory Integrated?  If so, is it replicating the the DCs or the DNS servers
0
 
TJacoberger1Author Commented:
The DNS is pointed to itself in the NIC properties, and the flushDNS /registerdns did nothing.
0
 
bkellyboulderitCommented:
What event errors are you getting?

what does dcdiag say?

http://go.microsoft.com/fwlink/?LinkId=100114
0
 
TJacoberger1Author Commented:
-DNS is installed on the 2003 box
-DNS is pointing to iteself
-No the new server does not have a srv record
-if i click on sites, and services i'm getting the same error. I can connect to the domain controller though, i dont see the global catalog.
-All the machines are pointing to the new dns server, i have it set in DHCP. I released and renewed the IP's on each machine.
-The DNS zone is configured to be active directory integrated, its replicating to DNS servers only.
0
 
TJacoberger1Author Commented:
This in in application event
Event ID 1054
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.

A lot of things failed on dcdiag, which i dont understand. When I transfered the roles, it said it passed fine.
0
 
e_vanheelCommented:
Is the 2000 box still a DC?  It's possible the the 2003 box did not fiinish replicating and that the SYSVOL share did not mount.  Do a NET SHARE at the command prompt and see if SYSVOL and NETLOGON are present.  If not, there is a registry tweak I can get you that will force them to load.
0
 
TJacoberger1Author Commented:
No the 2000 server is not a DC since i had to seize some of the roles. They are not present,
0
 
e_vanheelCommented:
Try this:
1. Stop the File Replication service on the domain controller.
2. Start Registry Editor (Regedt32.exe).
3. Locate and then click the BurFlags value under the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup
4. On the Edit menu, click DWORD, click Hex, type D4, and then click OK.
5. Quit Registry Editor.
6. Move data out of the PreExisting folder.
7. Restart the File Replication Service.
0
 
TJacoberger1Author Commented:
Do you want me to edit the Burflags value, or create a new dword under edit. Dword is under new task then dword.
0
 
e_vanheelCommented:
Edit the Burflags and change the value to D4 (make sure that you have the Hex button checked).  This setting forces the domain controller not to wait for replication before activating the domian services.
0
 
TJacoberger1Author Commented:
ok, i just wanted to make sure. Not trying to sound retarded, and one more question, what folder am I moving data from. in regedit under the process at startup.
0
 
e_vanheelCommented:
No data is being moved.  You are simply making a value change in the registry.  The steps above come directly from Microsoft.
0
 
TJacoberger1Author Commented:
oh ok, I just wanted to make sure.
0
 
TJacoberger1Author Commented:
ok, the error is not coming up. Will this make the server pickup as the DC, or should I be looking at something else.
0
 
e_vanheelCommented:
Do a NET SHARE and see if SYSVOL is listed.  If so make sure you can get into sites and services and such to test AD.
0
 
TJacoberger1Author Commented:
I can get in to sites, and services, users and computers with the error. Sysvol is present now.
0
 
TJacoberger1Author Commented:
Its all good, Thanks for your all help. Your the man, deserve every point and more.
0
All Courses

From novice to tech pro — start learning today.