Sysvol and Netlog does not share on new DC

Hi,

I have installed a new Windows 2003 SP1 Domain Controller into and existing domain on the same LAN. I have two DC's already operating fine in this domain. Both these DC have DNS configured. I set the new new server to point to one of tge DC's. The DCPROMO went fine with no errors. After rebooting the new DC does not share the SYSVOL and NETLOG and I get this error in NETDIAG.

Domain membership test . . . . . . : Failed
    [WARNING] Ths system volume has not been completely replicated to the local machine. This machine is not working properly as a DC.

This is the Output from DCDIAG


 Domain Controller Diagnosis

Performing initial setup:
   Done gathering initial info.

Doing initial required tests
   
   Testing server: EMN-Randburg\EMN-DC10
      Starting test: Connectivity
         ......................... EMN-DC10 passed test Connectivity

Doing primary tests
   
   Testing server: EMN-Randburg\EMN-DC10
      Starting test: Replications
                ......................... EMN-DC10 passed test Replications
      Starting test: NCSecDesc
         ......................... EMN-DC10 passed test NCSecDesc
      Starting test: NetLogons
         Unable to connect to the NETLOGON share! (\\EMN-DC10\netlogon)
         [EMN-DC10] An net use or LsaPolicy operation failed with error 1203, No network provider accepted the given network path..
         ......................... EMN-DC10 failed test NetLogons
      Starting test: Advertising
         Warning: DsGetDcName returned information for \\emn-dc02.xxxx.com when we were trying to reach EMN-DC10.
         Server is not responding or is not considered suitable.
         ......................... EMN-DC10 failed test Advertising
      Starting test: KnowsOfRoleHolders
         ......................... EMN-DC10 passed test KnowsOfRoleHolders
      Starting test: RidManager
         ......................... EMN-DC10 passed test RidManager
      Starting test: MachineAccount
         ......................... EMN-DC10 passed test MachineAccount
      Starting test: Services
         ......................... EMN-DC10 passed test Services
      Starting test: ObjectsReplicated
         ......................... EMN-DC10 passed test ObjectsReplicated
      Starting test: frssysvol
         ......................... EMN-DC10 passed test frssysvol
      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.
         ......................... EMN-DC10 failed test frsevent
      Starting test: kccevent
         ......................... EMN-DC10 passed test kccevent
      Starting test: systemlog
         An Error Event occured.  EventID: 0xC0002719
            Time Generated: 04/07/2006   19:02:22
            (Event String could not be retrieved)
         ......................... EMN-DC10 failed test systemlog
      Starting test: VerifyReferences
         ......................... EMN-DC10 passed test VerifyReferences
   
   Running partition tests on : DomainDnsZones
      Starting test: CrossRefValidation
         ......................... DomainDnsZones passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... DomainDnsZones passed test CheckSDRefDom
   
   Running partition tests on : ForestDnsZones
      Starting test: CrossRefValidation
         ......................... ForestDnsZones passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... ForestDnsZones passed test CheckSDRefDom
   
   Running partition tests on : emn
      Starting test: CrossRefValidation
         ......................... emn passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... emn passed test CheckSDRefDom
   
   Running partition tests on : Schema
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom
   
   Running partition tests on : Configuration
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom
   
   Running enterprise tests on : naspers.dom
      Starting test: Intersite
         ......................... naspers.dom passed test Intersite
      Starting test: FsmoCheck
         ......................... naspers.dom passed test FsmoCheck


The server has been running for 3 hours already and the volumnes are still not shared.
All DNS diags work fine.
MarkWThorneAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jay_Jay70Commented:
Hi MarkWThorne,

save yourself the time - demote the server if you can and repromote it  - semething gone crazy on the promotion

OR

the share permissions should look like this

ACL should be for the following accounts:

Administrators --- Full Control
System Account --- Full Control
Creator Owner --- Full Control
Read --- Server Operators and Authenticated Users

read this its old but still valid
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q257338

Cheers!
0
Netman66Commented:
Please check and ensure the following before try what I post below.

1)  Point the new server to the main DNS server in your domain.  Make sure you do not point it anywhere else.
2)  Restart the Netlogon service on this DC.  Check DNS to be sure it has registered in the same containers as another DC (for comparison).

If the above is true then proceed with this:

1)  Stop the FRS service on this DC only.  Set the startup type to manual just for the duration of this process so it doesn't restart in the middle of it.
2)  Open regedit and navigate to this key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup

3)  In the right pane double click the BurFlags entry.
4)  Change the value to D2.

Restart the FRS service and set the startup back to Automatic.

Let us know if SYSVOL now comes back to life.

0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
MarkWThorneAuthor Commented:
SYSVOL and NETLOGON Still not shared.

got these events and information:

Event Type:      Information
Event Source:      NtFrs
Event Category:      None
Event ID:      13553
Date:            4/9/2006
Time:            11:47:21 AM
User:            N/A
Computer:      EMN-DC11
Description:
The File Replication Service successfully added this computer to the following replica set:
    "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
 
Information related to this event is shown below:
Computer DNS name is "emn-dc11.domainname.com"
Replica set member name is "EMN-DC11"
Replica set root path is "d:\windows\sysvol\domain"
Replica staging directory path is "d:\windows\sysvol\staging\domain"
Replica working directory path is "c:\windows\ntfrs\jet"

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:      Information
Event Source:      NtFrs
Event Category:      None
Event ID:      13554
Date:            4/9/2006
Time:            11:47:21 AM
User:            N/A
Computer:      EMN-DC11
Description:
The File Replication Service successfully added the connections shown below to the replica set:
    "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
 
      "emn-dc01.domainname.com"
      "EMN-DC10.domainname.com"
      "EMN-DC10.domainname.com"
      "emn-dc01.domainname.com"
     
           
      More information may appear in subsequent event log messages.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:      Information
Event Source:      NtFrs
Event Category:      None
Event ID:      13553
Date:            4/9/2006
Time:            11:47:21 AM
User:            N/A
Computer:      EMN-DC11
Description:
The File Replication Service successfully added this computer to the following replica set:
    "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
 
Information related to this event is shown below:
Computer DNS name is "emn-dc11.domainname.com"
Replica set member name is "EMN-DC11"
Replica set root path is "d:\windows\sysvol\domain"
Replica staging directory path is "d:\windows\sysvol\staging\domain"
Replica working directory path is "c:\windows\ntfrs\jet"

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.





0
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

MarkWThorneAuthor Commented:
Jay Jay,

Checked the permissions, they look okay. Tried introducing another DC. Same problem.
0
Jay_Jay70Commented:
>>>>
>>>>>>>
Replica set root path is "d:\windows\sysvol\domain"
Replica staging directory path is "d:\windows\sysvol\staging\domain"
Replica working directory path is "c:\windows\ntfrs\jet"


>>>>>>

what is that! im not sure that thats the way it supposed to be  note the c: and d:    whats the deal with your partitioning and drive layout   do you have a c:\windows\sysvol and a d:\windows\sysvol??

I may be wrong but i have never seen this happen before - hopefully netman can shed some more light as he has seen a lot more that i have....
0
Netman66Commented:
This would be normal if you selected D: as the ntds.dit and log file drive.  Did you accept the defaults when you DCPROMO'd this server or did you change the directory paths?

0
MarkWThorneAuthor Commented:
No I changed the default to D: for the NTDS and the SYSVOL. We do this on all our DCs.
0
Netman66Commented:
Well, the logs indicate that the new server is participating in the domain and SYSVOL should be shared.

If you run:

net share

..from the CMD prompt on the new server, is SYSVOL listed?

0
MarkWThorneAuthor Commented:
No, its not.
0
Netman66Commented:
OK, please go through the logfiles (Event Logs) on this server and post anything related (copy to clipboard and paste the actual error here).  I suspect there will be a Journal Wrap error on this server or one of the other DCs.

Let me know.
0
MarkWThorneAuthor Commented:
Hello Netman66,

The NTFRS log only gives two warnings before the two events I have posted after that nothing is logged in the event log.
Event Type:      Warning
Event Source:      NtFrs
Event Category:      None
Event ID:      13520
Date:            4/9/2006
Time:            11:47:21 AM
User:            N/A
Computer:      EMN-DC11
Description:
The File Replication Service moved the preexisting files in d:\windows\sysvol\domain to d:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog.
 
The File Replication Service may delete the files in d:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog at any time. Files can be saved from deletion by copying them out of d:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog. Copying the files into d:\windows\sysvol\domain may lead to name conflicts if the files already exist on some other replicating partner.
 
In some cases, the File Replication Service may copy a file from d:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog into d:\windows\sysvol\domain instead of replicating the file from some other replicating partner.
 
Space can be recovered at any time by deleting the files in d:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:      Warning
Event Source:      NtFrs
Event Category:      None
Event ID:      13565
Date:            4/9/2006
Time:            11:47:15 AM
User:            N/A
Computer:      EMN-DC11
Description:
File Replication Service is initializing the system volume with data from another domain controller. Computer EMN-DC11 cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.
 
To check for the SYSVOL share, at the command prompt, type:
net share
 
When File Replication Service completes the initialization process, the SYSVOL share will appear.
 
The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume, the availability of other domain controllers, and the replication interval between domain controllers.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

The ealier events are a repeat on the on above and NTFRS stopping and starting.

One thing I did not mention and I am not sure that this is of help.

The DC is a VM server using VM Server 2005. I have created DCs before using VMs for our DR site but never experienced this problem.
0
Netman66Commented:
These really are not errors, but are what I would expect to see given the process I asked you to perform.  So far nothing you have posted for Events are a problem.

Being in a VM should not matter.  Is the D: drive within the VM also?  or is it mapped to the host's drive?



0
Jay_Jay70Commented:
i take it by the fact that you are able to promote the DC's that there is still good contact between them - you can complete full name resolution

thorwing in shots now as i have never seen this not fixed by the above solutions - at least not without more specific event logs
0
MarkWThorneAuthor Commented:
Lanman the D drive is part of the VM. a 16GB drive partitioned into 2 x 8GB at the time of he installation.

Jay Jay. The DC is still fully operational and has fully connectivity. Name resolution is not a problem.

When running ADUC and connect to this DC it works fine. same with other tools.
0
Netman66Commented:
Is the Firewall turned off on the VM guest?

0
MarkWThorneAuthor Commented:
FW in turned off on both the guest and the host.
0
dragepCommented:
I've got more or less the same problem, I've tried to recreate the sysvol structure manually on the new BDC using the dcpromo /adv switch (I'm thinking maybe it's getting stuck copying some rogue data from the PDC) but it didn't work.

I've also tried cleaning up the old AD metadata but I can't find any reference to any old servers in there. (we forced a demotion of a PDC last year)

Is there a way to read the NTFrs logs? They look a bit of a jumble if you read them as straight text - Any help gratefully received! - Paul.
0
MarkWThorneAuthor Commented:
Hi,

Just an update on this. First my apologies for the late response, I off site for a week or so.

Since I did the DCPROMO on the 8/4 the SYSVOL and Netlogon finally mounted itself on the 13/4 at 03:00 am.
There are no errors in the eventlogs prior to this only the warning events already posted.

I have no idea why this took so long.

So if this is okay by you I would like the split the points 400 to Netman an 100 to Jay for the effort in trying to resolve it.
But it still a mystery as to why it took so long.

Best regards

Mark
0
Netman66Commented:
Hi Mark,

Thanks for the update.  It's strange it took so long - absolutely.  As long as it's up and running I guess it's one for the books.

Do what you feel is right with the points.

Cheers,
NM
0
Jay_Jay70Commented:
as long its working thats great!

i dont feel i helped you all that much but the choice is yours with the points - main thing is your working again :)

cheers mate
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.