Tom's Guide | Tom's Hardware | Tom's Games
![]() |
![]() |
![]() |
I have a small network with one server running active directory, when i try to access group policy for the domain or domain controller either from administrative tools or within ad users & comps, i get an error message, it is either 'the network name could not be found' or 'the specified domain does not exist or could not be contacted'. I thought it might be DNS but i have run netdiag /debug and everything passed (DNS was OK) except for these two errors:-
**************************
Domain membership test . . . . . . : Failed
[WARNING] Ths system volume has not been completely replicated to the local machine. This machine is not working properly as a DC.
Machine is a . . . . . . . . . : Primary Domain Controller Emulator
Netbios Domain name. . . . . . : EX1
Dns domain name. . . . . . . . : ex1.local
Dns forest name. . . . . . . . : ex1.local
Domain Guid. . . . . . . . . . : {6CDD97A3-C7E9-4169-9DF1-3CA6B8E9AA18}
Domain Sid . . . . . . . . . . : S-1-5-21-1659004503-1682526488-1060284298
Logon User . . . . . . . . . . : administrator
Logon Domain . . . . . . . . . : EX1
*********************************
*********************************
DC discovery test. . . . . . . . . : FailedFind DC in domain 'EX1':
[FATAL] Cannot find DC in domain 'EX1'. [ERROR_NO_SUCH_DOMAIN]
DC list test . . . . . . . . . . . : Failed
'EX1': Cannot find DC to get DC list from [test skipped].
List of DCs in Domain 'EX1':
Trust relationship test. . . . . . : Skipped
Kerberos test. . . . . . . . . . . : Skipped
'EX1': Cannot find DC to get DC list from [test skipped].
LDAP test. . . . . . . . . . . . . : Failed
Cannot find DC to run LDAP tests on. The error occurred was: The specified domain either does not exist or could not be contacted.
**************************
**************************Any suggestions
Thanks

the machine should be able to recognize itself; something sounds torched.add another DC to your forest and see if this repairs replication. otherwise, you could try formatting and remaking the AD domain as you are on a small network anyway.

You could as well try unloading the WINS service, erase all the files located on %systemroot%\system32\wins and restart your server to see if it solves the problem.
Andrés

![]() |
![]() |
![]() |

This post is quite old and has been locked from receiving new replies. Please create a new posting instead.
| Ads by Google |