Solved

500 Easy Points - See URL below.

Posted on 2006-10-28
10
982 Views
Last Modified: 2008-01-09
http://www.experts-exchange.com/Operating_Systems/Q_22040753.html

I have 5 DCs in a WAN environment.  Yesterday my Root DC stopped replying to one of those DCs.  Now the servers do send/receive information but the Root doesn't replicate with the one DC anymore.  The DC that cannot replicate states that the Root DC's RPC isn't available.  All of the other DC's work properly and do not report any problems replicating.

I have tried removing and re-adding the site in sites and services, I have tried having that server added to a different site to see if it could replicate with any other of the DC's but that gives another error.

More information supplied at the question in the URL above.

Thank You  
0
Comment
Question by:EnclosAdmin
  • 6
  • 2
10 Comments
 
LVL 8

Expert Comment

by:nitadmin
ID: 17830863
Go to Event Viewer and look at all the Event Logs, System, Application. Everything.
There has to be some error events associated with your problem.

Let us know what you find.

Also run dcdiag test. And copy and paste the result here.

Cheers,
NITADMIN
0
 
LVL 2

Author Comment

by:EnclosAdmin
ID: 17833367
The attempt to establish a replication link for the following writable directory partition failed.
 
Directory partition:
DC=enclos,DC=glass,DC=com
Source domain controller:
CN=NTDS Settings,CN=MSPROOT,CN=Servers,CN=Enclos-HQ,CN=Sites,CN=Configuration,DC=enclos,DC=glass,DC=com
Source domain controller address:
44418113-2098-45d3-a3f9-a847a20d599b._msdcs.enclos.glass.com
Intersite transport (if any):
CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=enclos,DC=glass,DC=com
 
This domain controller will be unable to replicate with the source domain controller until this problem is corrected.  
 
User Action
Verify if the source domain controller is accessible or network connectivity is available.
 
Additional Data
Error value:
1722 The RPC server is unavailable.
0
 
LVL 2

Author Comment

by:EnclosAdmin
ID: 17833394
C:\WINDOWS>dcdiag /test:netlogons

Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests

   Testing server: STL\STLDC1
      Starting test: Connectivity
         ......................... STLDC1 passed test Connectivity

Doing primary tests

   Testing server: STL\STLDC1
      Starting test: NetLogons
         ......................... STLDC1 passed test NetLogons

   Running partition tests on : ForestDnsZones

   Running partition tests on : DomainDnsZones

   Running partition tests on : Schema

   Running partition tests on : Configuration

   Running partition tests on : enclos

   Running enterprise tests on : enclos.glass.com

C:\WINDOWS>dcdiag /test:replications

Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests

   Testing server: STL\STLDC1
      Starting test: Connectivity
         ......................... STLDC1 passed test Connectivity

Doing primary tests

   Testing server: STL\STLDC1
      Starting test: Replications
         REPLICATION-RECEIVED LATENCY WARNING
         STLDC1:  Current time is 2006-10-30 07:33:38.
            DC=ForestDnsZones,DC=enclos,DC=glass,DC=com
               Last replication recieved from YULDC1 at 2006-10-28 01:07:02.
               Last replication recieved from MSPROOT at 2006-10-28 00:56:45.
               Last replication recieved from SNADC1 at 2006-10-28 00:45:02.
               Last replication recieved from BWIDC1 at 2006-10-28 00:45:02.
               Last replication recieved from PLSDC1 at 2006-10-28 00:45:03.
               Last replication recieved from MNLDC1 at 2006-10-28 00:45:02.
               Last replication recieved from LAXDC1 at 2006-10-28 00:45:02.
            DC=DomainDnsZones,DC=enclos,DC=glass,DC=com
               Last replication recieved from YULDC1 at 2006-10-28 01:07:02.
               Last replication recieved from MSPROOT at 2006-10-28 00:56:45.
               Last replication recieved from SNADC1 at 2006-10-28 00:45:00.
               Last replication recieved from BWIDC1 at 2006-10-28 00:45:00.
               Last replication recieved from PLSDC1 at 2006-10-28 00:45:01.
               Last replication recieved from MNLDC1 at 2006-10-28 00:45:01.
               Last replication recieved from LAXDC1 at 2006-10-28 00:45:00.
            CN=Schema,CN=Configuration,DC=enclos,DC=glass,DC=com
               Last replication recieved from YULDC1 at 2006-10-28 01:06:40.
               Last replication recieved from MSPROOT at 2006-10-28 00:56:45.
               Last replication recieved from SNADC1 at 2006-10-28 00:44:58.
               Last replication recieved from BWIDC1 at 2006-10-28 00:44:58.
               Last replication recieved from PLSDC1 at 2006-10-28 00:44:58.
               Last replication recieved from MNLDC1 at 2006-10-28 00:44:57.
               Last replication recieved from LAXDC1 at 2006-10-28 00:44:58.
            CN=Configuration,DC=enclos,DC=glass,DC=com
               Last replication recieved from YULDC1 at 2006-10-28 01:06:40.
               Last replication recieved from MSPROOT at 2006-10-28 00:56:44.
               Last replication recieved from SNADC1 at 2006-10-28 00:44:53.
               Last replication recieved from BWIDC1 at 2006-10-28 00:44:55.
               Last replication recieved from PLSDC1 at 2006-10-28 00:44:57.
               Last replication recieved from MNLDC1 at 2006-10-28 00:44:56.
               Last replication recieved from LAXDC1 at 2006-10-28 00:44:54.
            DC=enclos,DC=glass,DC=com
               Last replication recieved from YULDC1 at 2006-10-28 01:06:39.
               Last replication recieved from MSPROOT at 2006-10-28 00:56:44.
               Last replication recieved from SNADC1 at 2006-10-28 00:44:59.
               Last replication recieved from BWIDC1 at 2006-10-28 00:44:59.
               Last replication recieved from PLSDC1 at 2006-10-28 00:45:00.
               Last replication recieved from MNLDC1 at 2006-10-28 00:44:51.
               Last replication recieved from LAXDC1 at 2006-10-28 00:44:59.
         REPLICATION-RECEIVED LATENCY WARNING
          Source site: CN=NTDS Site Settings,CN=BWI,CN=Sites,CN=Configuration,DC=enclos,DC=glass,DC=com
          Current time: 2006-10-30 07:33:39
          Last update time: 2006-10-28 00:18:26
          Check if source site has an elected ISTG running.
          Check replication from source site to this server.
         REPLICATION-RECEIVED LATENCY WARNING
          Source site: CN=NTDS Site Settings,CN=Enclos-HQ,CN=Sites,CN=Configuration,DC=enclos,DC=glass,DC=com
          Current time: 2006-10-30 07:33:39
          Last update time: 2006-10-28 00:34:49
          Check if source site has an elected ISTG running.
          Check replication from source site to this server.
         REPLICATION-RECEIVED LATENCY WARNING
          Source site: CN=NTDS Site Settings,CN=LAX,CN=Sites,CN=Configuration,DC=enclos,DC=glass,DC=com
          Current time: 2006-10-30 07:33:39
          Last update time: 2006-10-28 00:14:49
          Check if source site has an elected ISTG running.
          Check replication from source site to this server.
         REPLICATION-RECEIVED LATENCY WARNING
          Source site: CN=NTDS Site Settings,CN=MNL,CN=Sites,CN=Configuration,DC=enclos,DC=glass,DC=com
          Current time: 2006-10-30 07:33:39
          Last update time: 2006-10-28 00:20:08
          Check if source site has an elected ISTG running.
          Check replication from source site to this server.
         REPLICATION-RECEIVED LATENCY WARNING
          Source site: CN=NTDS Site Settings,CN=SNA,CN=Sites,CN=Configuration,DC=enclos,DC=glass,DC=com
          Current time: 2006-10-30 07:33:39
          Last update time: 2006-10-28 00:01:09
          Check if source site has an elected ISTG running.
          Check replication from source site to this server.
         REPLICATION-RECEIVED LATENCY WARNING
          Source site: CN=NTDS Site Settings,CN=YUL,CN=Sites,CN=Configuration,DC=enclos,DC=glass,DC=com
          Current time: 2006-10-30 07:33:39
          Last update time: 2006-10-28 00:47:24
          Check if source site has an elected ISTG running.
          Check replication from source site to this server.
         REPLICATION-RECEIVED LATENCY WARNING
          Source site: CN=NTDS Site Settings,CN=PLS,CN=Sites,CN=Configuration,DC=enclos,DC=glass,DC=com
          Current time: 2006-10-30 07:33:39
          Last update time: 2006-10-28 00:03:55
          Check if source site has an elected ISTG running.
          Check replication from source site to this server.
         ......................... STLDC1 passed test Replications

   Running partition tests on : ForestDnsZones

   Running partition tests on : DomainDnsZones

   Running partition tests on : Schema

   Running partition tests on : Configuration

   Running partition tests on : enclos

   Running enterprise tests on : enclos.glass.com

C:\WINDOWS>
0
 
LVL 2

Author Comment

by:EnclosAdmin
ID: 17833435
C:\WINDOWS>nltest.exe /dsregdns
Flags: 0
Connection Status = 1311 0x51f ERROR_NO_LOGON_SERVERS
The command completed successfully
0
How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

 
LVL 2

Author Comment

by:EnclosAdmin
ID: 17833683
When restarting Netlogon Service on the troubled DC many of the following error occur for each Record:

The dynamic registration of the DNS record 'ForestDnsZones.enclos.glass.com. 600 IN A 172.16.101.10' failed on the following DNS server:  

DNS server IP address: 172.16.77.121
Returned Response Code (RCODE): 5
Returned Status Code: 10060  

For computers and users to locate this domain controller, this record must be registered in DNS.  

USER ACTION  
Determine what might have caused this failure, resolve the problem, and initiate registration of the DNS records by the domain controller. To determine what might have caused this failure, run DCDiag.exe. You can find this program on the Windows Server 2003 installation CD in Support\Tools\support.cab. To learn more about  DCDiag.exe, see Help and Support Center. To initiate registration of the DNS records by  this domain controller, run 'nltest.exe /dsregdns' from the command prompt on the domain  controller or restart Net Logon service. Nltest.exe is available in the Microsoft Windows  Server Resource Kit CD.
  Or, you can manually add this record to DNS, but it is not recommended.  

ADDITIONAL DATA
Error Value: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
0
 
LVL 2

Author Comment

by:EnclosAdmin
ID: 17843751
This problem has been solved.

It was a  corrupted Riverbed Steelhead.  It caused just enough of a transmission problem that RPC couldn't resolve to the troubled server.

I bypassed the Steelhead and I was able to add the server back into the Domain, DCPromo it back to a DC.

So if you use Riverbed Steelheads be watchful.  If the RED light comes on, that means the Steelhead has a problem.  Do NOT trust the passthru switch!  Either get it fixed or bypass it until it can be fixed.

I have these on 3 of my DC connections, when they are working they work great!  Now I know what to look for if my DC starts falling apart.

Thanks to all of those that tried helping!
0
 
LVL 8

Expert Comment

by:nitadmin
ID: 17844576
What is Riverbed Steelheads?

NITADMIN
0
 
LVL 2

Author Comment

by:EnclosAdmin
ID: 17844661
Riverbed Steelheads are Netowrk caching devices.  Basically they contain Harddrives and they cache the network files between sites.  Obviously the HD size depends on the sites size.

For example,  you have two sites that need to share a Finance Share.  One site hosts the Finance share locally.  Both sites have Steelheads installed.  When users at the remote site access files from the Finance share, those files are technically copied to the Steelhead.  They make changes to that file and the Steelhead send back only the tiny block changes.  That makes the use of shared files much quicker as each user can open the files locally.

Keep in mind that the Steelheads are really using the files from the shared folder - so two users can't have the same file open and writable at the same time similar to a LAN.
0
 
LVL 1

Accepted Solution

by:
kodiakbear earned 0 total points
ID: 17975459
Closed, 20 points refunded.
kb
Experts Exchange Moderator
0

Featured Post

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

I guess it is not common knowledge to most Wintel engineers/administrators: If you have an SNMP-based monitoring system in your environment (and it's common to have SNMP or Syslog) it's reasonably easy to enable monitoring of the Windows Event logs,…
A quick step-by-step overview of installing and configuring Carbonite Server Backup.
Illustrator's Shape Builder tool will let you combine shapes visually and interactively. This video shows the Mac version, but the tool works the same way in Windows. To follow along with this video, you can draw your own shapes or download the file…
Polish reports in Access so they look terrific. Take yourself to another level. Equations, Back Color, Alternate Back Color. Write easy VBA Code. Tighten space to use less pages. Launch report from a menu, considering criteria only when it is filled…

705 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

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now