Question : Newly promoted DC is unable to enable Replication; Event 13508

We have been having a problem with backing up AD, so just to get it backed up, we installed a second copy of Windows Server 2003 Standard on a second computer, promoted it to a DC, backed up AD, unplugged it, and performed a metadata cleanup. Now we want to install a demo of Windows Server 2003 R2 Enterprise and promote it to a DC, but we keep receiving a 13565 event, followed by two 13508 events without 13509 in the File Replication Service Log.

Our troubleshooting has led us to believe the problem occurs because NETLOGON and SYSVOL are not sharing, but we can't figure out why. We have already demoted and promoted the server once to no effect

The problematic server fails 3 dcddiag tests:

      Starting test: NetLogons
         Unable to connect to the NETLOGON share! (\\*****\netlogon)
         [*****] An net use or LsaPolicy operation failed with error 1203, No network provider accepted the given network path..
         ......................... ***** failed test NetLogons
      Starting test: Advertising
         Warning: DsGetDcName returned information for \\*****.local, when we were trying to reach *****.
         Server is not responding or is not considered suitable.
         ......................... ***** failed test Advertisin

       Starting test: frsevent
         There are warning or error events within the last 24 hours after the

         SYSVOL has been shared.  Failing SYSVOL replication problems may cause

         Group Policy problems.
         ......................... ***** failed test frsevent

It is important that we get this computer running as a domain controller asap - any help would be appreciated! Thanks!

Answer : Newly promoted DC is unable to enable Replication; Event 13508

Well, we found the problem - the upstream DC was in JRNL_WRAP_ERROR. Once we fixed this, SYSVOL was shared automatically and without difficulty. Funny this wasn't mentioned in any of the Microsoft troubleshooting articles for event 13508. It was only when we started investigating the JRNL_WRAP_ERROR that we found out it affected replication.

Thanks, TokenCelt, for the help you offered. Turns out it wasn't an IP issue at all.