Dcdiag / Netdiag Problems

[Tezdread]

Hi,

I started running through the prelim steps to install Exchange2003 on my Win2k Server (PDC) and when I came to run dcdaig and netdiag I get these error in the logs.

====================== Dcdiag ======================
Testing server: Default-First-Site\ABSOSERVER
Starting test: Connectivity
ABSOSERVER's server GUID DNS name could not be resolved to an IP address. Check the DNS server, DHCP, server name, etc Although the Guid DNS name (e68e26a6-4226-49a6-8a76-b2f1b9672b0a._msdcs.DreadZone.local) couldn't be resolved, the server name (absoserver.DreadZone.local)resolved to the IP address (192.168.1.101) and was pingable. Check that the IP address is registered correctly with the DNS server.
......................... ABSOSERVER failed test Connectivity

====================== Netdiag ======================
DNS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative DNS server for the name 'absoserver.DreadZone.local.'. [RCODE_SERVER_FAILURE] The name 'absoserver.DreadZone.local.' may not be registered in DNS.
[WARNING] The DNS entries for this DC are not registered correctly on DNS server '192.168.1.101'. Please wait for 30 minutes for DNS server replication.
[FATAL] No DNS servers have the DNS records for this DC registered.
-----------------------------------------------------

I've tried getting help with the DNS issue in another forum but to no avail so far so I thought I'd try here.

Basically I can't say I've noticed any issues with DNS until I ran these files, and all my other PC's connect to the web fine and logon to the PDC for roaming profiles etc.

The question now is, will these errors need sorting before
I install Exchange 2003?

The other post is here (thread96-951442) hope this is ok but it could be either...

Any advise appreciated.
Thanks

Tezdread
"With every solution comes a new problem"

 

[Anonym0us]

Make sure you have both Forward Lookup Zones and Reverse Lookup Zones set up in DNS. Forward lookups will resolve a hostname into an IP address. Reverse lookups will resolve an IP address to a hostname. To verify, type the following in a Command Prompt window (this will do a foward lookup):

C:\>nslookup absoserver

Next, type the following in Command Prompt window (this will do a reverse lookup):

C:\>nslookup 192.168.1.101

If you get an errors, then your DNS is still not properly set up.

 

[Tezdread]

Thanks Anonym0us,

The Reverse Lookup Zone wasn't setup, I've now done this and this is the output of nslookup absoserver:

Server: absoserver
Address: 192.168.1.101

*** absoserver can't find absoserver: Non-existent domain

and nslookup 192.168.1.101

Server: absoserver
Address: 192.168.1.101

Name: absoserver
Address: 192.168.1.101

When I run Dcdiag and Netdiag I still get those same errors?

Tezdread
"With every solution comes a new problem"

 

[Anonym0us]

Good. Now, check your Forward Lookup Zones. There should be an entry that looks like this:

[b]Name[/b]          [b]Type[/b]          [b]Data[/b]
absoserver    Host (A)      192.168.1.101

If not, then add it with the New Host (A)... selection (right-click DreadZone.local under Forward Lookup Zones).

Try the nslookup queries (from above) again.

 

[Tezdread]

this is the DNS tree I have

|-DNS
|--ABSOSERVER
|
|---|Forward lookup Zones
| |
| |-dreadzone
|
|
|--|Reverse Lookup Zones
|
|-192.168.1.x Subnet

The only entries in Lookup Zones are 3 Hosts with non fixed IP's and absoserver with 192.168.1.101 and my router with 192.168.1.100, Start of Authority and Name Server. In the properties of the later 2 absoserver.dreadzone.local and the correct IP address is setup.

Tezdread
"With every solution comes a new problem"

 

[Anonym0us]

Your DNS namespace doesn't look right (dreadzone vs. dreadzone.local):

http://support.microsoft.com/?kbid=254680

Since you don't have that many DNS entries, I would just delete both the Forward Lookup Zones and Reverse Lookup Zones and start again:

http://support.microsoft.com/kb/172953/EN-US/

 

[Tezdread]

Ok I think I've got a little further Not sure how much though!

I totally removed DNS & DHCP from the server and reinstalled them from scratch and set them up again.

This is what I get when I run DCDiag:

DC Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial non skippeable tests

Testing server: Default-First-Site\ABSOSERVER
Starting test: Connectivity
......................... ABSOSERVER passed test Connectivity

Doing primary tests

Testing server: Default-First-Site\ABSOSERVER
Starting test: Replications
......................... ABSOSERVER passed test Replications
Starting test: NCSecDesc
......................... ABSOSERVER passed test NCSecDesc
Starting test: NetLogons
......................... ABSOSERVER passed test NetLogons
Starting test: Advertising
......................... ABSOSERVER passed test Advertising
Starting test: KnowsOfRoleHolders
......................... ABSOSERVER passed test KnowsOfRoleHolders
Starting test: RidManager
......................... ABSOSERVER passed test RidManager
Starting test: MachineAccount
......................... ABSOSERVER passed test MachineAccount
Starting test: Services
......................... ABSOSERVER passed test Services
Starting test: ObjectsReplicated
......................... ABSOSERVER passed test ObjectsReplicated
Starting test: frssysvol
......................... ABSOSERVER passed test frssysvol
Starting test: kccevent
......................... ABSOSERVER passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x8000003E
Time Generated: 11/20/2004 14:22:42
(Event String could not be retrieved)
An Error Event occured. EventID: 0xC00009C4
Time Generated: 11/20/2004 14:22:49
Event String: The server failed to start due to an

An Error Event occured. EventID: 0xC00001E1
Time Generated: 11/20/2004 14:22:49
Event String: Site Server LDAP Service cannot initialize the

......................... ABSOSERVER failed test systemlog

Running enterprise tests on : DreadZone.local
Starting test: Intersite
......................... DreadZone.local passed test Intersite
Starting test: FsmoCheck
......................... DreadZone.local passed test FsmoCheck


-------------------------------------------------------
-------------------------------------------------------

Netdiag: Reported no problems

The only errors in the Event logs that might have something to do with this are 2 from the System Log:

Site Server LDAP Service cannot initialize the following object: GetLastError()=997 : Init LdapExtension.

and

The server failed to start due to an initialization error. Verify the configuration. Error description is: GetLastError()=997 : CreateAccount for Anonymous users.

Both relating to LDAPSVCX but I don't think this has ever been setup...Do I need this sorted before installing Exchange 2003?

Tezdread
"With every solution comes a new problem"

 

[jcdoit7]

try running;
netdiag /fix
dcdiag /fix