Fix FRS_ERR_PARENT_TO_CHILD_COMM (0X00001F4C) on Server 2019

This error stops your domain controllers from syncing SYSVOL. It's frustrating. But we can get you back up in about 20 minutes.

The quick fix: Restart FRS and reset the partner

1. Open Command Prompt as Administrator. Press Windows Key + R, type cmd, then right-click it and pick Run as administrator.
2. Stop FRS with this command:
   net stop ntfrs
   You should see: "The File Replication service was stopped successfully."
3. Now reset the parent-child relationship. Run:
   nltest /dsregdns:yourdomain.local
   Replace yourdomain.local with your actual domain. Wait 10–15 seconds. You should see "Netlogon successfully registered DNS records."
4. Start FRS again:
   net start ntfrs
   You should see: "The File Replication service started successfully."
5. Check the event log. Open Event Viewer > Windows Logs > Application. Look for Event ID 13562. That means FRS found its parent.

Why this works

The error 0X00001F4C happens when FRS can't talk to its parent domain controller. Usually this is because DNS records are stale or the parent DC changed its IP. By stopping FRS, reregistering DNS, and starting FRS, you force a fresh connection. The nltest /dsregdns command updates the SRV records that FRS uses to find its parent. It's a clean reset without touching AD.

If the quick fix doesn't work

Sometimes the issue is deeper. Here are three less common causes and their fixes.

1. Firewall blocking RPC ports

FRS uses RPC (port 135) and a dynamic high port range (49152–65535 on newer servers). If a firewall between DCs blocks these, you get this error.

1. Open Windows Defender Firewall with Advanced Security on both DCs.
2. Go to Inbound Rules. Look for "File and Printer Sharing (SMB-In)". It should be enabled for Domain profile. If it's off, right-click and Enable.
3. Also check for rules named "Remote Service Management (RPC)". Enable those too.
4. Test with telnet from the child DC to the parent on port 135:
   telnet parentdc.yourdomain.local 135
   If it connects (blank screen with blinking cursor), RPC is fine. If it fails, you've got a firewall problem.

2. Corrupted FRS database

If DNS and firewall are fine, the FRS database might be corrupted. You can rebuild it.

1. Stop FRS: net stop ntfrs
2. Rename the FRS database folder (keeps a backup):
   ren C:\Windows\NTFRS\jet\ntfrs.jdb ntfrs.jdb.old
3. Start FRS: net start ntfrs
4. Check the event log for Event ID 13565. That means FRS is building a fresh database. This can take 5–10 minutes.

3. Time sync issue

FRS is strict about time. If the clocks on your DCs are more than 5 minutes off, it throws this error.

1. On each DC, run w32tm /query /status. Note the "Source" and "Last Successful Sync Time".
2. If they're not syncing, run:
   w32tm /resync /nowait
3. Make sure the PDC emulator role holder syncs with an external source (like time.windows.com). On that DC, run:
   w32tm /config /manualpeerlist:time.windows.com /syncfromflags:manual /reliable:yes /update
   Then restart the service: net stop w32time && net start w32time

Prevention tips

You don't want to fix this again. Here's what I tell my guys:

• Keep DNS clean. Set scavenging on all zones. Do it once a week. Stale records cause more FRS errors than anything else.
• Migrate to DFSR. FRS is old. Windows Server 2008 R2 and later support DFSR for SYSVOL. It's more stable. Run dfsrmig /getglobalstate to check your state. If it's not at "Eliminated", plan to migrate. I've done this on dozens of domains—takes a few hours but saves headaches.
• Monitor event logs. Set alerts for Event IDs 13562 and 13572. Catching these early means a 5-minute fix instead of a 2-hour disaster.
• Use static IPs on DCs. DHCP changes break DNS registration. Give each DC a static IP.

That's it. If you still get the error after trying these steps, check the Application event log for a parent DC that's offline. FRS can't talk to a dead server. Sometimes the fix is just bringing the parent back up.