+ Post New Thread
Results 1 to 9 of 9
Windows Server 2008 R2 Thread, Sysvol Replication not working to 1 DC out of 3 in Technical; Hi all Have googled around but couldnt find anything to fix our issue. Have 3 DCs all running Windows 2008 ...
  1. #1
    mthomas08's Avatar
    Join Date
    Jun 2008
    Posts
    1,619
    Thank Post
    136
    Thanked 166 Times in 147 Posts
    Rep Power
    62

    Sysvol Replication not working to 1 DC out of 3

    Hi all

    Have googled around but couldnt find anything to fix our issue.

    Have 3 DCs all running Windows 2008 R2 Server, 2 of the DCs including the Master are working fine but number 3 being our exchange server is failing. Any chances to the Sysvol folders on the 2 working DCs are not replicating over. This issue DC has got exchange 2010 (been installed for a year now) issues must of occurred in the last 6 months which must have something do to with our server upgrades?

    Have tried the following:
    Reboots
    Manual replication
    Folder Permissions all match
    Servers can access each other name/ip no problem
    DCDiag looks fine minus an alert 20 (event log is Schannel alert 20 and 10 - quite a few of them).
    IP Config /all looks all right
    Repl all looks as well - all succeeded

    I have manually gone in and change the GPO settings on this DC temporarily which has resolved our basic issues.

    Looking at DNS I can't see no obvious issues, I have noticed that email is appearing in OurDomain-DomainDNSZones/TCP (and Sites TCP) and ForestDNSZOnes TCP (and Sites TCP) even though its not a DNS?

    Also: An old server which was demoted and now only a member server (till we can transfer the public drive data then its out) is appearing in the msdcs.OurDomain - Domains/TCP and DC/TCP folders. Even though its not a DC just a member server (this is windows 2003 server box which will be scrapped).

    Not sure what else to add but as you can guess I have tried a few bits and bobs. Any help will be great thank you.

  2. #2

    Join Date
    Dec 2008
    Location
    Essex
    Posts
    2,144
    Thank Post
    1
    Thanked 326 Times in 316 Posts
    Rep Power
    77
    1. First of all, check the even logs for any errors or warning.
    2. Use repadmin /showreps to see what replication issues it's reporting, chances are it will find something.
    3. I assume Exch is working as it should?

  3. #3
    mthomas08's Avatar
    Join Date
    Jun 2008
    Posts
    1,619
    Thank Post
    136
    Thanked 166 Times in 147 Posts
    Rep Power
    62
    repadmin /showreps

    Showing all successful

    Only errors Occuring are to do with our Certificate because our external domain has one but internally we dont so it asks users to click continue when the first load outlook. Also the alert 20/10 which I think has to do with the certificate.

    Other then that nope no other issues, Active Directory/Exchange are working perfectly fine. It really does seem to be just the Sysvol folder and all its contents not syncronizing - can be accessed from each other though using start-run.

    Cheers

  4. #4

    3s-gtech's Avatar
    Join Date
    Mar 2009
    Location
    Wales
    Posts
    2,813
    Thank Post
    146
    Thanked 571 Times in 515 Posts
    Rep Power
    154

  5. Thanks to 3s-gtech from:

    mthomas08 (29th June 2012)

  6. #5

    Ric_'s Avatar
    Join Date
    Jun 2005
    Location
    London
    Posts
    7,599
    Thank Post
    109
    Thanked 765 Times in 596 Posts
    Rep Power
    181
    Step 1 - Stop using your Exchange server as a DC... this is bad!
    Step 2 - Check that the previously mentioned server is no longer referenced anywhere as a DC.
    Step 3 - Hope that manually changing Sysvol stuff on that server hasn't further screwed replication... this is also bad!

    BTW - If you have schannel errors, you will almost certainly need to do an schannel reset on that server (from a DC run netdom reset screwedservername) and then reboot the screwed server.

  7. Thanks to Ric_ from:

    mthomas08 (29th June 2012)

  8. #6

    Join Date
    Jan 2006
    Location
    Surburbia
    Posts
    2,178
    Thank Post
    74
    Thanked 307 Times in 243 Posts
    Rep Power
    115
    Quote Originally Posted by Ric_ View Post
    Step 1 - Stop using your Exchange server as a DC... this is bad!
    Catch 22: Microsoft do not support changing that Exchange box from a DC to a member server. I don't know if that's because Bad Stuff[tm] will happen or not, but superficially at least "not recommended" seems like a better place to be than "not supported".

  9. Thanks to PiqueABoo from:

    mthomas08 (29th June 2012)

  10. #7
    mthomas08's Avatar
    Join Date
    Jun 2008
    Posts
    1,619
    Thank Post
    136
    Thanked 166 Times in 147 Posts
    Rep Power
    62
    Thanks for taking time to respond guys

    The DC on exchange was something it did and told me to do. I did read about the GC shouldnt really be on exchange though so dont know if your mixing them up?

    2nd: The replication issue is now fixed and this has solved two of our issues so great thank you on that. Profiles seem to be logging on MUCH better and faster. We have a 3rd issue which fingers crossed will resolve this but only time will tell.

    As for the Schannel errors thats not going to cause any other problems is it? the reset?

    I just did a bit of googling on the netdom reset and this does have something to do with the replication between DCs so perhaps the error will go away. I will give the servers a reboot and see how things go. I will drop back if the errors are still occurring if the netdom reset solves the issue or not.

    Will return, few days! thanks again.

  11. #8

    Join Date
    Jan 2006
    Location
    Surburbia
    Posts
    2,178
    Thank Post
    74
    Thanked 307 Times in 243 Posts
    Rep Power
    115
    Read this sometime: How We Solved Problems With Exchange Running on a Domain Controller in EBS. Bear in mind that's three years ago talking about Exchange 2007 and some aspects might have changed. The DR point snagged my attention in an "oh.. ughh" way, but I don't know whether that's still the case with E2K10 and likewise for them saying that if it is a DC it will benefit from being a GC.

    Update - MS Quote (from a context that does encompass E2K10): If Exchange Server is running on a domain controller, you must also make that domain controller a global catalog server.
    Last edited by PiqueABoo; 29th June 2012 at 11:54 PM.

  12. #9
    mthomas08's Avatar
    Join Date
    Jun 2008
    Posts
    1,619
    Thank Post
    136
    Thanked 166 Times in 147 Posts
    Rep Power
    62
    Typical microsoft that is, one page says one thing and another page says another.

    Anyway: the replication problem is 100% fixed and still no issues on that front. The Schannel error is still appearing though, I know we have an internal certificate issue (because it has the external link in its list and not internal). I will try and get that resolved but I dont think this will give the Schannel issue.

SHARE:
+ Post New Thread

Similar Threads

  1. Replies: 2
    Last Post: 10th November 2010, 11:50 AM
  2. PXE booting not working on one model of PC - any ideas?
    By sidewinder in forum Wireless Networks
    Replies: 10
    Last Post: 22nd July 2010, 10:08 AM
  3. Want To Get Out Of Your Orange Mobile Contract Early?
    By SYSMAN_MK in forum General Chat
    Replies: 46
    Last Post: 6th August 2009, 07:21 PM
  4. Tips to (not) get the most out of your IT department
    By sidewinder in forum General Chat
    Replies: 74
    Last Post: 14th January 2008, 01:04 PM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •