Sysvol Not Shared on Second 2003 Server

Fortrak
Fortrak used Ask the Experts™
on
Promoted a second server (Server2) to be a domain controller on a network with only one other DC (Server1). Both are running 2003R2 OS. DCPROMO completed. After which I installed DNS on Server2 - AD integrated and it populated the zones fine. Problem is that replication is not happening from Server1 (original server) to Server2 (secondary). In Sites and Services NTDS shows that Server1 has a connection to Server2 but Server2 NTDS dosn't show any connections. Also Sysvol is not shared. Should DNS have been installed on Server2 before promoting it to a DC? Would demoting and promoting Server2 now that DNS is installed possibly fix this issue?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®

Commented:
Did you restart your server2 after promoting it to DC?
Top Expert 2012

Commented:
You can use the burflag method to get replication to take place.

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

Also, when you promote a server to a DC it should point to existing DC for DNS until full replication of the AD has taken place including the SYSVOL and Netlogon server.

Author

Commented:
Yes I've restarted Server2 since the promotion but no change.

I did have it pointing to Server1 for DNS prior to the promotion but once I had installed DNS I changed it to only point to itself. Before looking at the burflag method I wanted to makes sure there wasn't something I missed here.
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Top Expert 2012

Commented:
A common mistake is that once you get DNS running on the new server you should change the IP address to point to itself which can cause issues with replication if it isn't fully finished.

Top Expert 2012

Commented:

Author

Commented:
I've changed it to point to Server1 and rebooted. Will wait a bit and report back with results.

Author

Commented:
No luck on changing the DNS after the reboot. Still no Sysvol share.

Using the burflag registry key would not the Sysvol need to be shared out prior or will it do that automatically when doing the non-authoritative  restore?
Top Expert 2012

Commented:
When you do the authoritative restore the sysvol should come up.
Commented:
Turns out the Windows Firewall was enabled on Server2!  I didn't think the firewall was enabled on a DC but in this case it was. This was the root of all the problems. After turning off the firewall and rebooting, the Sysvol and Netlogon shares came up. Lesson learned. Thanks for the input.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial