Solved

New domain controller, replication fails

Posted on 2014-03-20
5
1,587 Views
1 Endorsement
Last Modified: 2014-03-21
I added a new server to an already existing domain and made it a domain controller. Sysvol is on the new dc but without any information.  It is not replicating.  I do not see sysvol or netlogon when I run net share. This is what I get when I do a dcdiag. Thank you

PS C:\Windows\system32> dcdiag

Directory Server Diagnosis

Performing initial setup:
   Trying to find home server...
   Home Server = medmod-pdc
   * Identified AD Forest.
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\MEDMOD-PDC
      Starting test: Connectivity
         ......................... MEDMOD-PDC passed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\MEDMOD-PDC
      Starting test: Advertising
         Warning: DsGetDcName returned information for \\MEDMOD-DC.medmod.local, when we were trying to reach
         MEDMOD-PDC.
         SERVER IS NOT RESPONDING or IS NOT CONSIDERED SUITABLE.
         ......................... MEDMOD-PDC failed test Advertising
      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.
         ......................... MEDMOD-PDC passed test FrsEvent
      Starting test: DFSREvent
         ......................... MEDMOD-PDC passed test DFSREvent
      Starting test: SysVolCheck
         ......................... MEDMOD-PDC passed test SysVolCheck
      Starting test: KccEvent
         ......................... MEDMOD-PDC passed test KccEvent
      Starting test: KnowsOfRoleHolders
         ......................... MEDMOD-PDC passed test KnowsOfRoleHolders
      Starting test: MachineAccount
         ......................... MEDMOD-PDC passed test MachineAccount
      Starting test: NCSecDesc
         ......................... MEDMOD-PDC passed test NCSecDesc
      Starting test: NetLogons
         Unable to connect to the NETLOGON share! (\\MEDMOD-PDC\netlogon)
         [MEDMOD-PDC] An net use or LsaPolicy operation failed with error 67, The network name cannot be found..
         ......................... MEDMOD-PDC failed test NetLogons
      Starting test: ObjectsReplicated
         ......................... MEDMOD-PDC passed test ObjectsReplicated
      Starting test: Replications
         ......................... MEDMOD-PDC passed test Replications
      Starting test: RidManager
         ......................... MEDMOD-PDC passed test RidManager
      Starting test: Services
         ......................... MEDMOD-PDC passed test Services
      Starting test: SystemLog
         An error event occurred.  EventID: 0x0000272C
            Time Generated: 03/20/2014   22:15:34
            Event String:
            DCOM was unable to communicate with the computer 75.75.75.75 using any of the configured protocols; requeste
d by PID     1538 (C:\Windows\system32\dcdiag.exe).
         An error event occurred.  EventID: 0x0000272C
            Time Generated: 03/20/2014   22:15:56
            Event String:
            DCOM was unable to communicate with the computer 75.75.76.76 using any of the configured protocols; requeste
d by PID     1538 (C:\Windows\system32\dcdiag.exe).
         ......................... MEDMOD-PDC failed test SystemLog
      Starting test: VerifyReferences
         ......................... MEDMOD-PDC passed test VerifyReferences


   Running partition tests on : ForestDnsZones
      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation

   Running partition tests on : DomainDnsZones
      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation

   Running partition tests on : Schema
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation

   Running partition tests on : Configuration
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation

   Running partition tests on : medmod
      Starting test: CheckSDRefDom
         ......................... medmod passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... medmod passed test CrossRefValidation

   Running enterprise tests on : medmod.local
      Starting test: LocatorCheck
         ......................... medmod.local passed test LocatorCheck
      Starting test: Intersite
         ......................... medmod.local passed test Intersite
PS C:\Windows\system32>
1
Comment
Question by:dtw3
  • 3
  • 2
5 Comments
 
LVL 13

Expert Comment

by:Santosh Gupta
ID: 39944646
Hi,

Please go through the steps.

#1
Try to access the shares by using \\saporito.local and see if you are able to see the sysvol share. if not then follow the below url and enable the share.

Set the SysvolReady Flag registry value to "0" and then back to "1" in the registry.

 Click Start, click Run, type regedit, and then click OK.
 Locate the following subkey in Registry Editor:

 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters]

 In the details pane, right-click SysvolReady Flag, and then click Modify.
 In the Value data box, type 0 and then click OK.
 Again in the details pane, right-click SysvolReady Flag, and then click
 Modify.  In the Value data box, type 1, and then click OK.

 Then run NET SHARE and see if the SYSVOL and NETLOGON share is present.

http://support.microsoft.com/kb/315457

##2
if sysvol share is present then try the authoritative restore of server by playing with registry.

http://support.microsoft.com/kb/315457

###3
Enable Loose Replication Consistency


 To enable Loose Replication Consistency, follow these steps on the domain controller 2003 that reports the errors messages. Locate and click the following registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTDS\Parameters

2.Click Add Value on the Edit menu.
3.Add the following value:
Value Name: Strict Replication Consistency
 Data type: REG_DWORD
 Value data: If the value is 1, change it to 0.


Also share the Operating system version and number of DC. in your reply.
0
 

Author Comment

by:dtw3
ID: 39944936
Hello,

Thank you for helping me.  I went through your steps.  After step #1 I ran 'net share' and I see sysvol but not netlogon.  Here is the results from 'net share'


PS C:\Windows\system32> net share

Share name   Resource                        Remark

----------------------------------------------------------------------
C$           C:\                             Default share
D$           D:\                             Default share
IPC$                                         Remote IPC
ADMIN$       C:\Windows                      Remote Admin
SYSVOL       C:\Windows\SYSVOL\sysvol        Logon server share
The command completed successfully.

I tried following the directions in step #2 but get the error 'The term 'linkd' is not recognized as the name of a cmdlet'

I did complete step # 3. I have 2 servers the original DC is running windows server 2008 R2 and the new DC that is giving me issues is windows server 2012 r2.  Here is what dcdiag looks like now.


Directory Server Diagnosis

Performing initial setup:
   Trying to find home server...
   Home Server = medmod-pdc
   * Identified AD Forest.
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\MEDMOD-PDC
      Starting test: Connectivity
         ......................... MEDMOD-PDC passed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\MEDMOD-PDC
      Starting test: Advertising
         ......................... MEDMOD-PDC passed test Advertising
      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.
         ......................... MEDMOD-PDC passed test FrsEvent
      Starting test: DFSREvent
         ......................... MEDMOD-PDC passed test DFSREvent
      Starting test: SysVolCheck
         ......................... MEDMOD-PDC passed test SysVolCheck
      Starting test: KccEvent
         ......................... MEDMOD-PDC passed test KccEvent
      Starting test: KnowsOfRoleHolders
         ......................... MEDMOD-PDC passed test KnowsOfRoleHolders
      Starting test: MachineAccount
         ......................... MEDMOD-PDC passed test MachineAccount
      Starting test: NCSecDesc
         ......................... MEDMOD-PDC passed test NCSecDesc
      Starting test: NetLogons
         Unable to connect to the NETLOGON share! (\\MEDMOD-PDC\netlogon)
         [MEDMOD-PDC] An net use or LsaPolicy operation failed with error 67, The network name cannot be found..
         ......................... MEDMOD-PDC failed test NetLogons
      Starting test: ObjectsReplicated
         ......................... MEDMOD-PDC passed test ObjectsReplicated
      Starting test: Replications
         ......................... MEDMOD-PDC passed test Replications
      Starting test: RidManager
         ......................... MEDMOD-PDC passed test RidManager
      Starting test: Services
         ......................... MEDMOD-PDC passed test Services
      Starting test: SystemLog
         An error event occurred.  EventID: 0x0000164A
            Time Generated: 03/21/2014   04:46:36
            Event String:
            The Netlogon service could not create server share C:\Windows\SYSVOL\sysvol\medmod.local\SCRIPTS.  The follo
wing error occurred:
         An error event occurred.  EventID: 0x0000164A
            Time Generated: 03/21/2014   05:03:13
            Event String:
            The Netlogon service could not create server share C:\Windows\SYSVOL\sysvol\medmod.local\SCRIPTS.  The follo
wing error occurred:
         ......................... MEDMOD-PDC failed test SystemLog
      Starting test: VerifyReferences
         ......................... MEDMOD-PDC passed test VerifyReferences


   Running partition tests on : ForestDnsZones
      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation

   Running partition tests on : DomainDnsZones
      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation

   Running partition tests on : Schema
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation

   Running partition tests on : Configuration
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation

   Running partition tests on : medmod
      Starting test: CheckSDRefDom
         ......................... medmod passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... medmod passed test CrossRefValidation

   Running enterprise tests on : medmod.local
      Starting test: LocatorCheck
         ......................... medmod.local passed test LocatorCheck
      Starting test: Intersite
         ......................... medmod.local passed test Intersite
0
 

Author Comment

by:dtw3
ID: 39944959
I also now see this in the event log on the 2012 DC.


The File Replication Service is no longer preventing the computer MEDMOD-PDC from becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL.
 
Type "net share" to check for the SYSVOL share.
0
 
LVL 13

Accepted Solution

by:
Santosh Gupta earned 500 total points
ID: 39944993
Hi,

1. follow the step #1, in earlier post.
2. check the FRS event log.
3. check if fsmo roles are ok, "NETDOM QUERY FSMO"
4. RUN DCDIAG /TEST:DNS
5. Check the LAN property of ADC and make sure the your primary DC IP is configured as first DNS.
0
 

Author Closing Comment

by:dtw3
ID: 39945012
Thank you so much! This site and you ROCK!


Share name   Resource                        Remark

-------------------------------------------------------------------------------
C$           C:\                             Default share
D$           D:\                             Default share
IPC$                                         Remote IPC
ADMIN$       C:\Windows                      Remote Admin
NETLOGON     C:\Windows\SYSVOL\sysvol\medmod.local\SCRIPTS
                                             Logon server share
SYSVOL       C:\Windows\SYSVOL\sysvol        Logon server share
0

Featured Post

Enabling OSINT in Activity Based Intelligence

Activity based intelligence (ABI) requires access to all available sources of data. Recorded Future allows analysts to observe structured data on the open, deep, and dark web.

Join & Write a Comment

The password reset disk is often mentioned as the best solution to deal with the lost Windows password problem. In Windows 2008, 7, Vista and XP, a password reset disk can be easily created. But besides Windows 7/Vista/XP, Windows Server 2008 and ot…
Are you one of those front-line IT Service Desk staff fielding calls, replying to emails, all-the-while working to resolve end-user technological nightmares? I am! That's why I have put together this brief overview of tools and techniques I use in o…
Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

762 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

20 Experts available now in Live!

Get 1:1 Help Now