Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win

x
?
Solved

DCDIAG failing - 2008 DC in an existing 2003 Domain

Posted on 2012-04-03
8
Medium Priority
?
1,299 Views
Last Modified: 2012-05-08
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
0
Comment
Question by:ccfcfc
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 5
  • 2
8 Comments
 
LVL 21

Expert Comment

by:motnahp00
ID: 37804244
Please take a screen cap of your Active Directory Sites and Services settings.
0
 
LVL 10

Expert Comment

by:Prashant Girennavar
ID: 37804645
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://secure.experts-exchange.com/questionUpgrade.jsp?qid=22997530&redirect=/OS/Microsoft_Operating_Systems/Server/2003_Server/Q_22997530.html

Regards,

_Prashant_
0
 

Author Comment

by:ccfcfc
ID: 37804848
See screen capture of sites and services attached
Hope this helps.
site-and-services.docx
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 

Author Comment

by:ccfcfc
ID: 37804854
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
0
 

Author Comment

by:ccfcfc
ID: 37805713
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.
0
 
LVL 10

Expert Comment

by:Prashant Girennavar
ID: 37827102
"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_
0
 

Accepted Solution

by:
ccfcfc earned 0 total points
ID: 37927968
Initial problem was that a tick was applied to "DNS suffix for this conenction"

There is also an issue with non-microsoft services loaded at startup. So having to go through these via MSCONFIG
0
 

Author Closing Comment

by:ccfcfc
ID: 37940810
This was the potential fix and have raised a call with Microsoft
0

Featured Post

Tech or Treat!

Submit an article about your scariest tech experience—and the solution—and you’ll be automatically entered to win one of 4 fantastic tech gadgets.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

After seeing many questions for JRNL_WRAP_ERROR for replication failure, I thought it would be useful to write this article.
Resolving an irritating Remote Desktop connection that stops your saved credentials from being used.
Attackers love to prey on accounts that have privileges. Reducing privileged accounts and protecting privileged accounts therefore is paramount. Users, groups, and service accounts need to be protected to help protect the entire Active Directory …
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…
Suggested Courses

604 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question