ERROR! ( The specified domain either does not exist or could not be contacted. )

[Guest]

Hi all

I have a problem with our main DC. It is a Windows 2000 AD, and we also have two more Windows 2003 AD DCs. When I try NETDOM QUERY /DOMAIN:MYDOMAIN /VERIFY DC , I receive following error

Machine Status/Domain Domain Controlle
======= ============= ================
\\BGDDC ERROR! ( The specified domain either does not exis
or could not be contacted.
\\BGD03 MYDOMAIN.CO.YU. \\BGDDC.MYDOMAIN.CO.Y
\\NSAD MYDOMAIN.CO.YU. \\BGDDC.MYDOMAIN.CO.Y

BGDDC is Windows 2000 'main' DC and other two are Windows 2003 A
Netdiag and Dcdiag report no errors whatsoever. I tried to reset machine account (as per MS KB about this procedure) couple of times but no use

I would very much appreciate any help about this...

 

[Guest]

One more question,

Is this happening to a newly installed standalone DC? Meaning this behaviour is normal?!?

 

[David Brandt [MSFT]]

This was posted as a "new" post, so the original explanation and reply/s
were not there, but what I can tell you about that msg is that 99.9% of the
time it is generated because of name resolution, which in the case of win2k
means dns, and no, it is not normal if dns is installed and functioning
properly and the machines can resolve the domain name and other dc/s
properly.
If you'll post/reply again with the original problem and circumstances where
you're seeing this, I'll do my best to answer it for you.

--
David Brandt
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send e-mail directly to this alias. This alias is for
newsgroup purposes only.

One more question,

Is this happening to a newly installed standalone DC? Meaning this

behaviour is normal?!?

 

[Guest]

Hello David

Thank you for response. The reason for second post is that I had a chance to test this on a standalone PC with fresh install of Windows 2003 server. It is AD DC and DNS is installed on it. PC has one NIC with static IP address and its DNS points to itself. Domain name i

ADTEST.CO.Y

And both AD and DNS were installed with defaults. This is single PC in its own domain. It has one network card
Both DCDIAG /c /v and NETDIAG /DEBUG report no errors whatsoever, but

NETDOM QUERY /domain:ADTEST.CO.YU /VERIFY D

report

ERROR! ( The specified domain either does not exist or could not be contacted.


an


NLTEST /sc_query:ADTEST.CO.Y

report

I_NetLogonControl failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAI


I also setup Debug log file for DNS server but when I start NETDOM or NLTEST there are no packets detected in the log file (I flushed DNS resolver cache previously of course). Are those commands query DNS at all

What other reasons are for this error

P.S. NETDOM and DCDIAG are from Windows Server 2003 Support Tools

 

[Guest]

Hello David,

Thank you for response. The reason for second post is that I had a chance to test this on a standalone PC with fresh install of Windows 2003 server. It is AD DC and DNS is installed on it. Domain name is

ADTEST.CO.YU

And both AD and DNS were installed with defaults. This is single PC in its own domain. It has one network card.
Both DCDIAG /c /v and NETDIAG /DEBUG report no errors whatsoever, but

NETDOM QUERY /domain:ADTEST.CO.YU /VERIFY DC

reports

ERROR! ( The specified domain either does not exist or could not be contacted. )



and



NLTEST /sc_query:ADTEST.CO.YU

reports

I_NetLogonControl failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN




I also setup Debug log file for DNS server but when I start NETDOM or NLTEST there are no packets detected in the log file (I flushed DNS resolver cache previously of course). Are those commands query DNS at all?

What other reasons are for this error?


P.S. NETDOM and DCDIAG are from Windows Server 2003 Support Tools