I just started a new Systems Administrator position this week and am seeing some pre-existing issues on the Domain Controller. It is a Windows Server 2003 Standard Edition Domain Controller, there is only one PDC, no Backup Domain Controllers have been set up yet. I see this error going back for several months in the System Event Logs.
I am seeing the following netlogon error on my domain controller.
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 3097
Date: 12/22/2005
Time: 12:09:47 PM
User: N/A
Computer: HDOM01
Description:
This computer is configured to be the primary domain controller of its domain. However, the computer CORPDEV01 is currently claiming to be the primary domain controller of the domain.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
The unusual thing here is that the server CORPDEV01 is running Suse Linux! I'm not sure what, if any, services being run on linux could appear to a Windows Domain Controller to be another PDC, or if there is a setting somewhere on the PDC telling the PDC that CORPDEV01 has a PDC role.
Along with this error in the System Even Log I am seeing another Netlogon Error. This error shows up in the System Event log at about the same date that the above error shows up:
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5741
Date: 12/22/2005
Time: 12:09:47 PM
User: N/A
Computer: HDOM01
Description:
Netlogon could not register the HSOFTWARE <1B> name for the following reason:
\Device\NetBT_Tcpip_{C710F
362-381B-4
3C1-9DEA-5
C6C3030AF6
5}
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: bd 00 00 c0 ½..À
This error is also showing up on the same starting date at the two above errors:
Event Type: Error
Event Source: NetBT
Event Category: None
Event ID: 4321
Date: 8/12/2005
Time: 8:27:43 AM
User: N/A
Computer: HELMDOM01
Description:
The name "HSOFTWARE :1d" could not be registered on the Interface with IP address 10.1.1.50. The machine with the IP address 10.1.1.99 did not allow the name to be claimed by this machine.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 04 00 56 00 ......V.
0008: 00 00 00 00 e1 10 00 c0 ....á..À
0010: 01 01 00 00 01 00 00 c0 .......À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
10.1.1.50 is the IP of the DC, 10.1.1.99 is the IP of CORPDEV, the linux Server.
After seeing all this in the System Event Log I ran a DCDiag from the Domain Controller, it failed its FSMO test with the following error:
Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355.
Here are the full results of my dcdiag test, which I ran with the following switches - dcdiag /e /c /v /f:logfile.txt
(i hope this is not overkill as far as the amount of information i am supplying!):
Domain Controller Diagnosis
Performing initial setup:
* Verifying that the local machine HDOM01, is a DC.
* Connecting to directory service on server HDOM01.
* Collecting site info.
* Identifying all servers.
* Identifying all NC cross-refs.
* Found 1 DC(s). Testing 1 of them.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\HD
OM01
Starting test: Connectivity
* Active Directory LDAP Services Check
* Active Directory RPC Services Check
......................... HDOM01 passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\HD
OM01
Starting test: Replications
* Replications Check
* Replication Latency Check
* Replication Site Latency Check
......................... HDOM01 passed test Replications
Starting test: Topology
* Configuration Topology Integrity Check
* Analyzing the connection topology for DC=ForestDnsZones,DC=hsoft
ware,DC=co
m.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for DC=DomainDnsZones,DC=hsoft
ware,DC=co
m.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for CN=Schema,CN=Configuration
,DC=hsoftw
are,DC=com
.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for CN=Configuration,DC=hsoftw
are,DC=com
.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the connection topology for DC=hsoftware,DC=com.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
......................... HDOM01 passed test Topology
Starting test: CutoffServers
* Configuration Topology Aliveness Check
* Analyzing the alive system replication topology for DC=ForestDnsZones,DC=hsoft
ware,DC=co
m.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for DC=DomainDnsZones,DC=hsoft
ware,DC=co
m.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for CN=Schema,CN=Configuration
,DC=hsoftw
are,DC=com
.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for CN=Configuration,DC=hsoftw
are,DC=com
.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
* Analyzing the alive system replication topology for DC=hsoftware,DC=com.
* Performing upstream (of target) analysis.
* Performing downstream (of target) analysis.
......................... HDOM01 passed test CutoffServers
Starting test: NCSecDesc
* Security Permissions check for all NC's on DC HDOM01.
* Security Permissions Check for
DC=ForestDnsZones,DC=hsoft
ware,DC=co
m
(NDNC,Version 2)
* Security Permissions Check for
DC=DomainDnsZones,DC=hsoft
ware,DC=co
m
(NDNC,Version 2)
* Security Permissions Check for
CN=Schema,CN=Configuration
,DC=hsoftw
are,DC=com
(Schema,Version 2)
* Security Permissions Check for
CN=Configuration,DC=hsoftw
are,DC=com
(Configuration,Version 2)
* Security Permissions Check for
DC=hsoftware,DC=com
(Domain,Version 2)
......................... HDOM01 passed test NCSecDesc
Starting test: NetLogons
* Network Logons Privileges Check
Verified share \\HDOM01\netlogon
Verified share \\HDOM01\sysvol
......................... HDOM01 passed test NetLogons
Starting test: Advertising
The DC HDOM01 is advertising itself as a DC and having a DS.
The DC HDOM01 is advertising as an LDAP server
The DC HDOM01 is advertising as having a writeable directory
The DC HDOM01 is advertising as a Key Distribution Center
The DC HDOM01 is advertising as a time server
The DS HDOM01 is advertising as a GC.
......................... HDOM01 passed test Advertising
Starting test: KnowsOfRoleHolders
Role Schema Owner = CN=NTDS
Settings,CN=HDOM01,CN=Serv
ers,CN=Def
ault-First
-Site-Name
,CN=Sites,
CN=Configu
ration,DC=
hsoftware,
DC=com
Role Domain Owner = CN=NTDS
Settings,CN=HDOM01,CN=Serv
ers,CN=Def
ault-First
-Site-Name
,CN=Sites,
CN=Configu
ration,DC=
hsoftware,
DC=com
Role PDC Owner = CN=NTDS
Settings,CN=HDOM01,CN=Serv
ers,CN=Def
ault-First
-Site-Name
,CN=Sites,
CN=Configu
ration,DC=
hsoftware,
DC=com
Role Rid Owner = CN=NTDS
Settings,CN=HDOM01,CN=Serv
ers,CN=Def
ault-First
-Site-Name
,CN=Sites,
CN=Configu
ration,DC=
hsoftware,
DC=com
Role Infrastructure Update Owner = CN=NTDS
Settings,CN=HDOM01,CN=Serv
ers,CN=Def
ault-First
-Site-Name
,CN=Sites,
CN=Configu
ration,DC=
hsoftware,
DC=com
......................... HDOM01 passed test KnowsOfRoleHolders
Starting test: RidManager
* Available RID Pool for the Domain is 1602 to 1073741823
* HDOM01.hsoftware.com is the RID Master
* DsBind with RID Master was successful
* rIDAllocationPool is 1102 to 1601
* rIDPreviousAllocationPool is 1102 to 1601
* rIDNextRID: 1184
......................... HDOM01 passed test RidManager
Starting test: MachineAccount
Checking machine account for DC HDOM01 on DC HDOM01.
* SPN found :LDAP/HDOM01.hsoftware.com
/hsoftware
.com
* SPN found :LDAP/HDOM01.hsoftware.com
* SPN found :LDAP/HDOM01
* SPN found :LDAP/HDOM01.hsoftware.com
/hsoftware
* SPN found :LDAP/b347e487-cca8-44a7-b
41b-62134b
a473a2._ms
dcs.hsoftw
are.com
* SPN found :E3514235-4B06-11D1-AB04-0
0C04FC2DCD
2/b347e487
-cca8-44a7
-b41b-6213
4ba473a2/h
software.c
om
* SPN found :HOST/HDOM01.hsoftware.com
/hsoftware
.com
* SPN found :HOST/HDOM01.hsoftware.com
* SPN found :HOST/HDOM01
* SPN found :HOST/HDOM01.hsoftware.com
/hsoftware
* SPN found :GC/HDOM01.hsoftware.com/h
software.c
om
......................... HDOM01 passed test MachineAccount
Starting test: Services
* Checking Service: Dnscache
* Checking Service: NtFrs
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: RpcSs
* Checking Service: w32time
* Checking Service: NETLOGON
......................... HDOM01 passed test Services
Starting test: OutboundSecureChannels
* The Outbound Secure Channels test
** Did not run Outbound Secure Channels test
because /testdomain: was not entered
......................... HDOM01 passed test OutboundSecureChannels
Starting test: ObjectsReplicated
HDOM01 is in domain DC=hsoftware,DC=com
Checking for CN=HDOM01,OU=Domain Controllers,DC=hsoftware,D
C=com in domain DC=hsoftware,DC=com on 1 servers
Object is up-to-date on all servers.
Checking for CN=NTDS
Settings,CN=HDOM01,CN=Serv
ers,CN=Def
ault-First
-Site-Name
,CN=Sites,
CN=Configu
ration,DC=
hsoftware,
DC=com in domain
CN=Configuration,DC=hsoftw
are,DC=com
on 1 servers
Object is up-to-date on all servers.
......................... HDOM01 passed test ObjectsReplicated
Starting test: frssysvol
* The File Replication Service SYSVOL ready test
File Replication Service's SYSVOL is ready
......................... HDOM01 passed test frssysvol
Starting test: frsevent
* The File Replication Service Event log test
......................... HDOM01 passed test frsevent
Starting test: kccevent
* The KCC Event log test
Found no KCC errors in Directory Service Event log in the last 15 minutes.
......................... HDOM01 passed test kccevent
Starting test: systemlog
* The System Event log test
An Error Event occured. EventID: 0xC00010E1
Time Generated: 12/22/2005 11:32:00
Event String: The name "hsoftware :1b" could not beregistered on the Interface with IP address10.1.1.50. The
machine with the IP address10.1.1.99 did not allow the name to be claimed bythis machine.
An Error Event occured. EventID: 0xC00010E1
Time Generated: 12/22/2005 11:47:00
Event String: The name "hsoftware :1b" could not beregistered on the Interface with IP address10.1.1.50. The
machine with the IP address10.1.1.99 did not allow the name to be claimed bythis machine.
An Error Event occured. EventID: 0xC00010E1
Time Generated: 12/22/2005 12:02:00
Event String: The name "hsoftware :1b" could not beregistered on the Interface with IP address10.1.1.50. The
machine with the IP address10.1.1.99 did not allow the name to be claimed bythis machine.
An Error Event occured. EventID: 0xC00010E1
Time Generated: 12/22/2005 12:09:47
Event String: The name "hsoftware :1b" could not beregistered on the Interface with IP address10.1.1.50. The
machine with the IP address10.1.1.99 did not allow the name to be claimed bythis machine.
An Error Event occured. EventID: 0x0000166D
Time Generated: 12/22/2005 12:09:47
Event String: Netlogon could not register the hsoftware<1B>name for the following reason:
\Device\NetBT_Tcpip_{C710F
362-381B-4
3C1-9DEA-5
C6C3030AF6
5}
An Error Event occured. EventID: 0x00000C19
Time Generated: 12/22/2005 12:09:47
Event String: This computer is configured to be the primarydomain controller of its domain. However, thecomputer
CORPDEV01 is currently claiming to bethe primary domain controller of the domain.
An Error Event occured. EventID: 0xC00010E1
Time Generated: 12/22/2005 12:09:47
Event String: The name "hsoftware :1b" could not beregistered on the Interface with IP address10.1.1.50. The
machine with the IP address10.1.1.99 did not allow the name to be claimed bythis machine.
......................... HDOM01 failed test systemlog
Starting test: VerifyReplicas
......................... HDOM01 passed test VerifyReplicas
Starting test: VerifyReferences
The system object reference (serverReference) CN=HDOM01,OU=Domain Controllers,DC=hsoftware,D
C=com and
backlink on CN=HDOM01,CN=Servers,CN=De
fault-Firs
t-Site-Nam
e,CN=Sites
,CN=Config
uration,DC
=hsoftware
,DC=com
are correct.
The system object reference (frsComputerReferenceBL) CN=HDOM01,CN=Domain System Volume (SYSVOL
share),CN=File Replication Service,CN=System,DC=hsoft
ware,DC=co
m and backlink on CN=HDOM01,OU=Domain
Controllers,DC=hsoftware,D
C=com are correct. The system object reference (serverReferenceBL)
CN=HDOM01,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=hsoft
ware,DC=co
m and
backlink on CN=NTDS
Settings,CN=HDOM01,CN=Serv
ers,CN=Def
ault-First
-Site-Name
,CN=Sites,
CN=Configu
ration,DC=
hsoftware,
DC=com are correct.
......................... HDOM01 passed test VerifyReferences
Starting test: VerifyEnterpriseReferences
......................... HDOM01 passed test VerifyEnterpriseReferences
Starting test: CheckSecurityError
* Dr Auth: Beginning security errors check!
Found KDC HDOM01 for domain hsoftware.com in site Default-First-Site-Name
Checking machine account for DC HDOM01 on DC HDOM01.
* SPN found :LDAP/HDOM01.hsoftware.com
/hsoftware
.com
* SPN found :LDAP/HDOM01.hsoftware.com
* SPN found :LDAP/HDOM01
* SPN found :LDAP/HDOM01.hsoftware.com
/hsoftware
* SPN found :LDAP/b347e487-cca8-44a7-b
41b-62134b
a473a2._ms
dcs.hsoftw
are.com
* SPN found :E3514235-4B06-11D1-AB04-0
0C04FC2DCD
2/b347e487
-cca8-44a7
-b41b-6213
4ba473a2/h
software.c
om
* SPN found :HOST/HDOM01.hsoftware.com
/hsoftware
.com
* SPN found :HOST/HDOM01.hsoftware.com
* SPN found :HOST/HDOM01
* SPN found :HOST/HDOM01.hsoftware.com
/hsoftware
* SPN found :GC/HDOM01.hsoftware.com/h
software.c
om
[HDOM01] No security related replication errors were found on this DC! To target the connection to a specific
source DC use /ReplSource:<DC>.
......................... HDOM01 passed test CheckSecurityError
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : hsoftware
Starting test: CrossRefValidation
......................... hsoftware passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... hsoftware passed test CheckSDRefDom
Running enterprise tests on : hsoftware.com
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope provided by the command line arguments
provided.
......................... hsoftware.com passed test Intersite
Starting test: FsmoCheck
GC Name: \\HDOM01.hsoftware.com
Locator Flags: 0xe00003fc
Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
A Primary Domain Controller could not be located.
The server holding the PDC role is down.
Time Server Name: \\HDOM01.hsoftware.com
Locator Flags: 0xe00003fc
Preferred Time Server Name: \\HDOM01.hsoftware.com
Locator Flags: 0xe00003fc
KDC Name: \\HDOM01.hsoftware.com
Locator Flags: 0xe00003fc
......................... hsoftware.com failed test FsmoCheck
Starting test: DNS
Test results for domain controllers:
DC: HDOM01.hsoftware.com
Domain: hsoftware.com
TEST: Authentication (Auth)
Authentication test: Successfully completed
TEST: Basic (Basc)
Microsoft(R) Windows(R) Server 2003, Standard Edition (Service Pack level: 1.0) is supported
NETLOGON service is running
kdc service is running
DNSCACHE service is running
DNS service is running
DC is a DNS server
Network adapters information:
Adapter [00000009] MAC Bridge Miniport:
MAC address is 02:11:43:D7:FA:7D
IP address is static
IP address: 10.1.1.50
DNS servers:
10.1.1.50 (<name unavailable>) [Valid]
Warning: 69.26.226.2 (<name unavailable>) [Invalid]
The A record for this DC was found
The SOA record for the Active Directory zone was found
The Active Directory zone on this DC/DNS server was found (primary)
Root zone on this DC/DNS server was not found
TEST: Forwarders/Root hints (Forw)
Recursion is enabled
Forwarders Information:
69.26.226.2 (<name unavailable>) [Invalid]
Root hint Information:
Name: a.root-servers.net. IP: 198.41.0.4 [Invalid]
Name: b.root-servers.net. IP: 192.228.79.201 [Invalid]
Name: c.root-servers.net. IP: 192.33.4.12 [Invalid]
Name: d.root-servers.net. IP: 128.8.10.90 [Invalid]
Name: e.root-servers.net. IP: 192.203.230.10 [Invalid]
Name: f.root-servers.net. IP: 192.5.5.241 [Invalid]
Name: g.root-servers.net. IP: 192.112.36.4 [Invalid]
Name: h.root-servers.net. IP: 128.63.2.53 [Invalid]
Name: i.root-servers.net. IP: 192.36.148.17 [Invalid]
Name: j.root-servers.net. IP: 192.58.128.30 [Invalid]
Name: k.root-servers.net. IP: 193.0.14.129 [Invalid]
Name: l.root-servers.net. IP: 198.32.64.12 [Invalid]
Name: m.root-servers.net. IP: 202.12.27.33 [Invalid]
TEST: Delegations (Del)
No delegations were found in this zone on this DNS server
TEST: Dynamic update (Dyn)
Dynamic update is enabled on the zone hsoftware.com.
Test record _dcdiag_test_record added successfully in zone hsoftware.com.
Test record _dcdiag_test_record deleted successfully in zone hsoftware.com.
TEST: Records registration (RReg)
Network Adapter [00000009] MAC Bridge Miniport:
Matching A record found at DNS server 10.1.1.50:
HDOM01.hsoftware.com
Matching CNAME record found at DNS server 10.1.1.50:
b347e487-cca8-44a7-b41b-62
134ba473a2
._msdcs.hs
oftware.co
m
Matching DC SRV record found at DNS server 10.1.1.50:
_ldap._tcp.dc._msdcs.hsoft
ware.com
Matching GC SRV record found at DNS server 10.1.1.50:
_ldap._tcp.gc._msdcs.hsoft
ware.com
Matching PDC SRV record found at DNS server 10.1.1.50:
_ldap._tcp.pdc._msdcs.hsof
tware.com
Error: Missing A record at DNS server 69.26.226.2 :
HDOM01.hsoftware.com
Error: Missing CNAME record at DNS server 69.26.226.2 :
b347e487-cca8-44a7-b41b-62
134ba473a2
._msdcs.hs
oftware.co
m
[Error details: 9501 (Type: Win32 - Description: No records found for given DNS query.)]
Error: Missing DC SRV record at DNS server 69.26.226.2 :
_ldap._tcp.dc._msdcs.hsoft
ware.com
[Error details: 9501 (Type: Win32 - Description: No records found for given DNS query.)]
Error: Missing GC SRV record at DNS server 69.26.226.2 :
_ldap._tcp.gc._msdcs.hsoft
ware.com
[Error details: 9501 (Type: Win32 - Description: No records found for given DNS query.)]
Error: Missing PDC SRV record at DNS server 69.26.226.2 :
_ldap._tcp.pdc._msdcs.hsof
tware.com
[Error details: 9501 (Type: Win32 - Description: No records found for given DNS query.)]
Error: Record registrations cannot be found for all the network adapters
Summary of test results for DNS servers used by the above domain controllers:
DNS server: 69.26.226.2 (<name unavailable>)
2 test failures on this DNS server
This is a valid DNS server.
Name resolution is not functional. _ldap._tcp.hsoftware.com. failed on the DNS server 69.26.226.2
[Error details: 9501 (Type: Win32 - Description: No records found for given DNS query.)]
DNS server: 128.63.2.53 (h.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server
128.63.2.53
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
DNS server: 128.8.10.90 (d.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server
128.8.10.90
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
DNS server: 192.112.36.4 (g.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server
192.112.36.4
[Error details: 9002 (Type: Win32 - Description: DNS server failure.)]
DNS server: 192.203.230.10 (e.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server
192.203.230.10
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
DNS server: 192.228.79.201 (b.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server
192.228.79.201
[Error details: 9002 (Type: Win32 - Description: DNS server failure.)]
DNS server: 192.33.4.12 (c.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server
192.33.4.12
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
DNS server: 192.36.148.17 (i.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server
192.36.148.17
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
DNS server: 192.5.5.241 (f.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server
192.5.5.241
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
DNS server: 192.58.128.30 (j.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server
192.58.128.30
[Error details: 9002 (Type: Win32 - Description: DNS server failure.)]
DNS server: 193.0.14.129 (k.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server
193.0.14.129
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
DNS server: 198.32.64.12 (l.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server
198.32.64.12
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
DNS server: 198.41.0.4 (a.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server
198.41.0.4
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
DNS server: 202.12.27.33 (m.root-servers.net.)
1 test failure on this DNS server
This is not a valid DNS server. PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server
202.12.27.33
[Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
DNS server: 10.1.1.50 (<name unavailable>)
All tests passed on this DNS server
This is a valid DNS server.
Name resolution is funtional. _ldap._tcp SRV record for the forest root domain is registered
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
__________________________
__________
__________
__________
________
Domain: hsoftware.com
HDOM01 PASS WARN FAIL PASS PASS FAIL n/a
......................... hsoftware.com failed test DNS
I am also noticing errors when I try to open the Group Policy Editor. I don't know when this error began but I think it is directly related to the errors mentioned above. When I attempt to open the Default Domain Policy from Active Directory Users and Computers I get an error stating:
DC for group policy operations is not available, You may cancel this operation for this session or retry using one of the following DC choices:
The one w/ Operations Master Token for the PDC emulator
The one used by AD Snap-ins
use any DC
If I choose the Operations Master Token for the PDC emulator role then i receive an error stating the PDC could not be contacted. If I coose the Use Any DC option I am able to connect to and manage the Default Domain Policy. I have been able to determing that the Policy is in effect for several Windows XP workstations I set up on my first day.
I have not been able to open the Domain Controller's Security Policy and can only open the Default Domain GPO by using the Choose any DC option in the error listed above.
I tried to resolve this issue by using the ntdsutil utility to seize the PDC role. After my attempts I receive a message stating that the seize was unnecessary as the PDC is already managing that role but none of my errors were resolved.
Please keep in mind that I will be out of the office for the weekend and may not be able to answer follow-up questions until after the Holiday Weekend. Thanks in Advance!
jmdowling
Start Free Trial
