AD/DNS Error

  • Thread starter Thread starter harry
  • Start date Start date
H

harry

How do I solve this AD and/or DNS problem? I freshly installed W2K and now
find this problem. Main symptom is client pc's cannot connect after a few
hours - need to reboot to reconnect.

I can't see anything wrong with DNS entries - all of which were created
during install.

Thanks
Harry

Here's output of dcdiag and netdiag /DNS

C:\Program Files\Support Tools>dcdiag

DC Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial non skippeable tests

Testing server: Default-First-Site-Name\CO3050825-B
Starting test: Connectivity
CO3050825-B'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
(f2665990-1090-4345-88f5-e40447317c50._msdcs.OMC) couldn't be
resolved, the server name (co3050825-b.OMC) resolved to the IP
address
(192.168.0.4) and was pingable. Check that the IP address is
registered correctly with the DNS server.
......................... CO3050825-B failed test Connectivity

Doing primary tests

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

Running enterprise tests on : OMC
Starting test: Intersite
......................... OMC passed test Intersite
Starting test: FsmoCheck
......................... OMC passed test FsmoCheck

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

C:\Program Files\Support Tools>netdiag /test:DNS

..........

Computer Name: CO3050825-B
DNS Host Name: co3050825-b.OMC
System info : Windows 2000 Server (Build 2195)
Processor : x86 Family 15 Model 0 Stepping 10, GenuineIntel
List of installed hotfixes :
KB820888
KB822343
KB822831
KB823182
KB823559
KB824105
KB825119
KB826232
KB828035
KB828741
KB828749
KB832359
KB835732
KB837001
KB839643
Q147222
Q828026


Netcard queries test . . . . . . . : Passed



Per interface results:

Adapter : Local Area Connection

Netcard queries test . . . : Passed


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{BB3FE3F0-C169-4C59-A082-F0DC93EDE221}
1 NetBt transport currently configured.


DNS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative DNS server for the
name
'co3050825-b.OMC.'. [RCODE_SERVER_FAILURE]
The name 'co3050825-b.OMC.' may not be registered in DNS.
[WARNING] The DNS entries for this DC are not registered correctly on
DNS se
rver '192.168.0.4'. Please wait for 30 minutes for DNS server replication.
[FATAL] No DNS servers have the DNS records for this DC registered.
 
In
harry said:
How do I solve this AD and/or DNS problem? I freshly
installed W2K and now find this problem. Main symptom is
client pc's cannot connect after a few hours - need to
reboot to reconnect.

I can't see anything wrong with DNS entries - all of
which were created during install.

Thanks
Harry

Here's output of dcdiag and netdiag /DNS

C:\Program Files\Support Tools>dcdiag

DC Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial non skippeable tests

Testing server: Default-First-Site-Name\CO3050825-B
Starting test: Connectivity
CO3050825-B'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

(f2665990-1090-4345-88f5-e40447317c50._msdcs.OMC)
couldn't be resolved, the server name (co3050825-b.OMC)
resolved to the IP
address
(192.168.0.4) and was pingable. Check that the
IP address is registered correctly with the DNS
server. ......................... CO3050825-B
failed test Connectivity

Doing primary tests

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

Running enterprise tests on : OMC
Starting test: Intersite
......................... OMC passed test
Intersite Starting test: FsmoCheck
......................... OMC passed test
FsmoCheck

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

C:\Program Files\Support Tools>netdiag /test:DNS

.........

Computer Name: CO3050825-B
DNS Host Name: co3050825-b.OMC
System info : Windows 2000 Server (Build 2195)
Processor : x86 Family 15 Model 0 Stepping 10,
GenuineIntel List of installed hotfixes :
KB820888
KB822343
KB822831
KB823182
KB823559
KB824105
KB825119
KB826232
KB828035
KB828741
KB828749
KB832359
KB835732
KB837001
KB839643
Q147222
Q828026


Netcard queries test . . . . . . . : Passed



Per interface results:

Adapter : Local Area Connection

Netcard queries test . . . : Passed


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{BB3FE3F0-C169-4C59-A082-F0DC93EDE221}
1 NetBt transport currently configured.


DNS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative
DNS server for the name
'co3050825-b.OMC.'. [RCODE_SERVER_FAILURE]
The name 'co3050825-b.OMC.' may not be
registered in DNS. [WARNING] The DNS entries for this
DC are not registered correctly on
DNS se
rver '192.168.0.4'. Please wait for 30 minutes for DNS
server replication. [FATAL] No DNS servers have the
DNS records for this DC registered.

The problem is caused by your single-label DNS domain name, single-label
domain names have no hierarchy to follow so it causes problems with DNS.
Starting with Win2kSP4, WinXP and Win2k3 registration is not possble in top
level domains without making registry entries. Even after making the
registry entries there will still be problems but this problem will go away.
In addition, it is required that you only use the local DNS in TCP/IP
properties, this is the rule for all active directory domain members.

300684 - Information About Configuring Windows 2000 for Domains with
Single-Label DNS Names
http://support.microsoft.com/default.aspx?scid=kb;en-us;300684

826743 - Clients cannot dynamically register DNS records in a single-label
forward lookup zone: http://support.microsoft.com/?id=826743

247681 - Microsoft DNS Server Cannot Resolve Some Domain Names
http://support.microsoft.com/default.aspx?scid=kb;en-us;247681
 
Thanks for your help. I'll try the changes now.

Kevin D. Goodknecht Sr. said:
In
harry said:
How do I solve this AD and/or DNS problem? I freshly
installed W2K and now find this problem. Main symptom is
client pc's cannot connect after a few hours - need to
reboot to reconnect.

I can't see anything wrong with DNS entries - all of
which were created during install.

Thanks
Harry

Here's output of dcdiag and netdiag /DNS

C:\Program Files\Support Tools>dcdiag

DC Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial non skippeable tests

Testing server: Default-First-Site-Name\CO3050825-B
Starting test: Connectivity
CO3050825-B'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

(f2665990-1090-4345-88f5-e40447317c50._msdcs.OMC)
couldn't be resolved, the server name (co3050825-b.OMC)
resolved to the IP
address
(192.168.0.4) and was pingable. Check that the
IP address is registered correctly with the DNS
server. ......................... CO3050825-B
failed test Connectivity

Doing primary tests

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

Running enterprise tests on : OMC
Starting test: Intersite
......................... OMC passed test
Intersite Starting test: FsmoCheck
......................... OMC passed test
FsmoCheck

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

C:\Program Files\Support Tools>netdiag /test:DNS

.........

Computer Name: CO3050825-B
DNS Host Name: co3050825-b.OMC
System info : Windows 2000 Server (Build 2195)
Processor : x86 Family 15 Model 0 Stepping 10,
GenuineIntel List of installed hotfixes :
KB820888
KB822343
KB822831
KB823182
KB823559
KB824105
KB825119
KB826232
KB828035
KB828741
KB828749
KB832359
KB835732
KB837001
KB839643
Q147222
Q828026


Netcard queries test . . . . . . . : Passed



Per interface results:

Adapter : Local Area Connection

Netcard queries test . . . : Passed


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
List of NetBt transports currently configured:
NetBT_Tcpip_{BB3FE3F0-C169-4C59-A082-F0DC93EDE221}
1 NetBt transport currently configured.


DNS test . . . . . . . . . . . . . : Failed
[WARNING] Cannot find a primary authoritative
DNS server for the name
'co3050825-b.OMC.'. [RCODE_SERVER_FAILURE]
The name 'co3050825-b.OMC.' may not be
registered in DNS. [WARNING] The DNS entries for this
DC are not registered correctly on
DNS se
rver '192.168.0.4'. Please wait for 30 minutes for DNS
server replication. [FATAL] No DNS servers have the
DNS records for this DC registered.

The problem is caused by your single-label DNS domain name, single-label
domain names have no hierarchy to follow so it causes problems with DNS.
Starting with Win2kSP4, WinXP and Win2k3 registration is not possble in top
level domains without making registry entries. Even after making the
registry entries there will still be problems but this problem will go away.
In addition, it is required that you only use the local DNS in TCP/IP
properties, this is the rule for all active directory domain members.

300684 - Information About Configuring Windows 2000 for Domains with
Single-Label DNS Names
http://support.microsoft.com/default.aspx?scid=kb;en-us;300684

826743 - Clients cannot dynamically register DNS records in a single-label
forward lookup zone: http://support.microsoft.com/?id=826743

247681 - Microsoft DNS Server Cannot Resolve Some Domain Names
http://support.microsoft.com/default.aspx?scid=kb;en-us;247681
 
Back
Top