ccfcfc
asked on
DCDIAG failing - 2008 DC in an existing 2003 Domain
I have recently just added a 2008 DC to an exisiting 2003 Domain
When I run DCDIAG I get the following errors, not sure why and what I need to do to fix :-
Running enterprise tests on : ldc.intamac.co.uk
Starting test: LocatorCheck
......................... ldc.intamac.co.uk passed test LocatorCheck
Starting test: Intersite
Doing intersite inbound replication test on site LDR-INSIDE:
Remote bridgehead LDR-INSIDE\LDR-DC-01 also couldn't be contacted
by dcdiag. Check this server.
***Error: The remote site Default-First-Site-Name, has no servers
the local site LDR-INSIDE for the writeable NC ForestDnsZones.e and
Replication will not continue until this is resolved.
***Error: The remote site Default-First-Site-Name, has no servers
the local site LDR-INSIDE for the writeable NC DomainDnsZones.e and
Replication will not continue until this is resolved.
Doing intersite inbound replication test on site
Default-First-Site-Name:
*Warning: Remote bridgehead LDR-INSIDE\LDR-DC-01 has some
replication syncs failing. It will be 1 hours 59 minutes and 0
failed replication attempts before the bridgehead is considered
ineligible to be a bridgehead.
Remote bridgehead LDR-INSIDE\LDR-DC-01 also couldn't be contacted
by dcdiag. Check this server.
......................... ldc.intamac.co.uk passed test Intersite
When I run DCDIAG I get the following errors, not sure why and what I need to do to fix :-
Running enterprise tests on : ldc.intamac.co.uk
Starting test: LocatorCheck
......................... ldc.intamac.co.uk passed test LocatorCheck
Starting test: Intersite
Doing intersite inbound replication test on site LDR-INSIDE:
Remote bridgehead LDR-INSIDE\LDR-DC-01 also couldn't be contacted
by dcdiag. Check this server.
***Error: The remote site Default-First-Site-Name, has no servers
the local site LDR-INSIDE for the writeable NC ForestDnsZones.e and
Replication will not continue until this is resolved.
***Error: The remote site Default-First-Site-Name, has no servers
the local site LDR-INSIDE for the writeable NC DomainDnsZones.e and
Replication will not continue until this is resolved.
Doing intersite inbound replication test on site
Default-First-Site-Name:
*Warning: Remote bridgehead LDR-INSIDE\LDR-DC-01 has some
replication syncs failing. It will be 1 hours 59 minutes and 0
failed replication attempts before the bridgehead is considered
ineligible to be a bridgehead.
Remote bridgehead LDR-INSIDE\LDR-DC-01 also couldn't be contacted
by dcdiag. Check this server.
......................... ldc.intamac.co.uk passed test Intersite
Please take a screen cap of your Active Directory Sites and Services settings.
By Looking at the logs It seems to me a DNS misconfiguration problem. How the DNS setup in your domain.
Best Practice,
1. Make sure each DC is pointing to itself (With its IP Address not loopback) , Provided it is also actings AS DNS server.
2. DC should not be multihomed , so disabel additional NIC on DC (which are not in use).
I would suggest you to run IPconfig /all on the domain controller and post the results here.
Also refer belwo article which might help you to narrow down the problem./
http://www.pcreview.co.uk/forums/long-dcdiag-error-win2k3-t1456826.html
https://www.experts-exchange.com/questionUpgrade.jsp?qid=22997530&redirect=/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_22997530.html
Regards,
_Prashant_
Best Practice,
1. Make sure each DC is pointing to itself (With its IP Address not loopback) , Provided it is also actings AS DNS server.
2. DC should not be multihomed , so disabel additional NIC on DC (which are not in use).
I would suggest you to run IPconfig /all on the domain controller and post the results here.
Also refer belwo article which might help you to narrow down the problem./
http://www.pcreview.co.uk/forums/long-dcdiag-error-win2k3-t1456826.html
https://www.experts-exchange.com/questionUpgrade.jsp?qid=22997530&redirect=/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_22997530.html
Regards,
_Prashant_
ASKER
ASKER
Screen shot from ipconfig/all
Windows IP Configuration
Host Name . . . . . . . . . . . . : LDR-DC-01
Primary Dns Suffix . . . . . . . : ldc.intamac.co.uk
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ldc.intamac.co.uk
in1r.edison.sgns.net
Ethernet adapter NIC1 - Production Network Inside:
Connection-specific DNS Suffix . : in1r.edison.sgns.net
Description . . . . . . . . . . . : vmxnet3 Ethernet Adapter
Physical Address. . . . . . . . . : 00-50-56-87-01-B3
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.144.25.6(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.144.25.1
DNS Servers . . . . . . . . . . . : 10.144.25.6
192.168.50.2
127.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Windows IP Configuration
Host Name . . . . . . . . . . . . : LDR-DC-01
Primary Dns Suffix . . . . . . . : ldc.intamac.co.uk
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ldc.intamac.co.uk
in1r.edison.sgns.net
Ethernet adapter NIC1 - Production Network Inside:
Connection-specific DNS Suffix . : in1r.edison.sgns.net
Description . . . . . . . . . . . : vmxnet3 Ethernet Adapter
Physical Address. . . . . . . . . : 00-50-56-87-01-B3
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.144.25.6(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.144.25.1
DNS Servers . . . . . . . . . . . : 10.144.25.6
192.168.50.2
127.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
ASKER
I have noticed the DNS was not set to AD integrated. So I changed it to , or attempted to and it returned
"The Replication scope could not be set.
The name limit for thr local computer network adapter card was exceeded.
"The Replication scope could not be set.
The name limit for thr local computer network adapter card was exceeded.
"The Replication scope could not be set.
The name limit for thr local computer network adapter card was exceeded.
Above forced me to think about duplicate AD Integrated zone in your AD. Did you check for them.
If they exists please go ahead and delete the duplicate zones.
Below is the article which you can refer too.
https://msmvps.com/blogs/acefekay/archive/2009/09/02/using-adsi-edit-to-resolve-conflicting-or-duplicate-ad-integrated-dns-zones.aspx
http://www.winvistatips.com/re-name-limit-local-computer-network-adapter-card-exc-t733439.html
Regards,
_Prashant_
The name limit for thr local computer network adapter card was exceeded.
Above forced me to think about duplicate AD Integrated zone in your AD. Did you check for them.
If they exists please go ahead and delete the duplicate zones.
Below is the article which you can refer too.
https://msmvps.com/blogs/acefekay/archive/2009/09/02/using-adsi-edit-to-resolve-conflicting-or-duplicate-ad-integrated-dns-zones.aspx
http://www.winvistatips.com/re-name-limit-local-computer-network-adapter-card-exc-t733439.html
Regards,
_Prashant_
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This was the potential fix and have raised a call with Microsoft