DCdiag and netdiag test error

[gino]

Can anyone help me with this error? I an running one DC
in a its own Domain. there is no connection to a ISP, or
Internet. It's a stand alone Domain.

C:\>dcdiag

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\myservername
Starting test: Connectivity
An error that is usually temporary occured
during DNS host lookup,
Please try again later.
Although the Guid DNS name
(1695d7a3-f42a-4edb-b388-
be8511b8ecaa._msdcs.corp.mydomainname.com)

couldn't be resolved, the server name
(myservername) resolved to the
IP address (xxx.xxx.x.x) and was pingable.
Check that the IP address
is registered correctly with the DNS server.
......................... myservername failed
test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\myservername
Skipping all tests, because server myservername is
not responding to directory service requests

Running enterprise tests on : corp.mydomain.com
Starting test: Intersite
......................... corp.mydomain.com
passed test Intersi
te
Starting test: FsmoCheck
......................... corp.mydomain.com
passed test FsmoChe
ck

C:\>cd Program Files\Support Tools

C:\Program Files\Support Tools>netdiag.exe
[FATAL] Failed to get system information of this machine.

C:\Program Files\Support Tools>

Thank you the help

 

[Kevin D. Goodknecht [MVP]]

In gino <[email protected]> posted a question
Then Kevin replied below:
: Can anyone help me with this error? I an running one DC
: in a its own Domain. there is no connection to a ISP, or
: Internet. It's a stand alone Domain.
:
: C:\>dcdiag
:
: Domain Controller Diagnosis
:
: Performing initial setup:
: Done gathering initial info.
:
: Doing initial required tests
:
: Testing server: Default-First-Site-Name\myservername
: Starting test: Connectivity
: An error that is usually temporary occured
: during DNS host lookup,
: Please try again later.
: Although the Guid DNS name
: (1695d7a3-f42a-4edb-b388-
: be8511b8ecaa._msdcs.corp.mydomainname.com)
:
: couldn't be resolved, the server name
: (myservername) resolved to the
: IP address (xxx.xxx.x.x) and was pingable.
: Check that the IP address
: is registered correctly with the DNS server.
: ......................... myservername failed

Post an unedited ipconfig /all please.



:
: C:\Program Files\Support Tools>netdiag.exe
: [FATAL] Failed to get system information of this machine.
:
: C:\Program Files\Support Tools>
:
: Thank you the help

Netdiag need the remote registry service running.

 

[Guest]

Thanks for the info on netdiag Kevin but do you have a
idea of what going on with dcdiag?

 

[Kevin D. Goodknecht [MVP]]

In (e-mail address removed) <[email protected]>
posted a question
Then Kevin replied below:
: Thanks for the info on netdiag Kevin but do you have a
: idea of what going on with dcdiag?
:
That's why I asked for the unedited ipconfig /all.

 

[Gino]

Kevin, I resolved this issue by recreating the DNS zone.
I could not get you the ipconfig /all because at the time
I was at a diff. site which had no internet access and I
didn't think of getting that info at that time. Once I
recreated the zone, instead of just using corp. I used
corp.mydomain.com and wow what a difference in
performance it made! Login and access to file on the
server are fast again.
Thanks again for the help
Gino

-----Original Message-----
In (e-mail address removed)