• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 431
  • Last Modified:

Sysvol and net logon net being shared and replication not starting on new DC

Here's the situation, The sysvol and netlogon shares are not being created, and no files ever get replicated to the sysvol from the other DC's.  We've followed KB's that have us set the D4(the good DC) and D2 on the bad one and still no dice.  FRSDiag doesn't report errors and ping by FQDN work just fine as well as reverse lookup.

We get the 13508 event and then it just does nothing.

Any idea's from here?
1 Solution
Try to Force the replication from the problem DC, have you try this.....!
johnstraitAuthor Commented:
Also ran on ntfrsutl on all dcs and it does return the information.

NTFRSUTL VERSION  host.domain.name
NtFrsApi Version Information
   NtFrsApi Major      : 0
   NtFrsApi Minor      : 0
   NtFrsApi Compiled on: Feb 16 2007 20:10:33
NtFrs Version Information
   NtFrs Major        : 0
   NtFrs Minor        : 0
   NtFrs Compiled on  : Feb 16 2007 20:10:45
   Latest changes:
   Install Override fix
OS Version 5.2 (3790) -
SP (2.0) SM: 0x0112  PT: 0x02
Processor:  AMD64 Level: 0x0006  Revision: 0x0f06  Processor num/mask: 4/0000000
johnstraitAuthor Commented:
ya tried that, spent all day yesterday with PSS and still no luck, read almost every artical on here and tried about half of them, EVERYTHING looka like it should be working but it just isn't.

13508 everytime we restart ntfrs but never 13509.

The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

check the registry entries


there are two parameters that close the administrative shares...
        AutoShareServer   REG_DWORD       (0)
        AutoShareWks      REG_DWORD       (0)

if the parameters and exists and their values are 0 that set tem to one and restart your machine... that may solve your problem..
Jason WatkinsIT Project LeaderCommented:
Is the server's firewall on, or is there any firewall between D4, D2?  If so, open the port exceptions for Core Networking.

johnstraitAuthor Commented:
Well after 21 hours on the phone with microsoft it looks like we have found our issue.

While not public yet, there is a internally known issue with NTFRS and Cisco's IPS / VPN.  While MS would not say anything directly, once they had me removed all packet inspection from ALL of our Cisco devices, install a patch they will be released in SP3, it started working.

Not sure why, the MS network support guy didn't see a single lost packet and we could see the ACK's to the FRS requests.

Now it's on to Cisco to get their side of the story, and get IPS back inspecting.

Thanks for everyone's comments.

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now