Fix RPC_S_INVALID_NAF_ID (0X000006E3) Network Error

You're staring at RPC_S_INVALID_NAF_ID (0X000006E3) – the network address family is invalid. This usually happens when you try to connect to a shared printer, map a network drive, or run a remote management tool. The error means the Windows Remote Procedure Call (RPC) service can't use the network protocol it needs.

I've seen this error on Windows 10 and 11, especially after a Windows update, a network adapter driver change, or when someone disabled IPv6 thinking it would speed things up. Let's fix it in order of likelihood – the most common cause first.

Cause 1: IPv6 is Disabled (Most Common)

Windows RPC relies on IPv6 for certain internal operations, even on IPv4-only networks. If you or a group policy disabled IPv6 on your network adapter, you'll get this exact error.

How to check if IPv6 is disabled

1. Press Win + R, type ncpa.cpl, and hit Enter.
2. Right-click your active network adapter (Ethernet or Wi-Fi), select Properties.
3. Look for Internet Protocol Version 6 (TCP/IPv6) in the list.
4. If the checkbox is unchecked, that's your problem.

The fix: Re-enable IPv6

1. Check the box next to Internet Protocol Version 6 (TCP/IPv6).
2. Click OK and then Close.
3. Restart your computer. After rebooting, the error should be gone.

If you're on a domain network, check Group Policy – a policy might have disabled IPv6. Run gpedit.msc and go to Computer Configuration > Administrative Templates > Network > TCPIP Settings > IPv6 Transition Technologies. Look for any policy that says “Disable IPv6” – set it to Not Configured.

Don't skip the reboot. I've seen techs re-enable IPv6 and test immediately, get the same error, and then give up. The RPC service needs a fresh start to pick up the new protocol stack.

Cause 2: Winsock Catalog Corruption

Winsock is the Windows implementation of the sockets API – it's what programs use to send and receive data over the network. When the Winsock catalog gets corrupted – often by a bad VPN client, antivirus filter driver, or a botched uninstall – RPC can't find the right address family, throwing 0X000006E3.

How to reset Winsock

1. Open Command Prompt as administrator. Press Win + X and select Terminal (Admin) or Command Prompt (Admin).
2. Type the following and press Enter after each:

netsh winsock reset
netsh int ip reset

3. You'll see a message saying you need to restart the computer. Do it.

After the restart, test your network connection again. If you're still getting the error, the Winsock reset didn't completely clear the problem – sometimes you need to uninstall the offending software first. I've seen a particular VPN client (I won't name it, but it rhymes with “Norton”) that keeps corrupting Winsock until you completely uninstall it, reset Winsock, and then reinstall a clean version.

Cause 3: RPC Service Configuration Issues

Less common, but I've hit this on machines where the RPC service itself was misconfigured – either the service is set to manual when it should be automatic, or the Remote Procedure Call (RPC) Locator service is disabled when it shouldn't be.

Check the RPC service status

1. Press Win + R, type services.msc, and press Enter.
2. Scroll down to Remote Procedure Call (RPC). Right-click it and select Properties.
3. Make sure Startup type is Automatic and the service status is Running.
4. If it's not running, click Start.

Also check Remote Procedure Call (RPC) Locator – it's not critical for most operations, but if it's disabled, some network features fail. Set its startup type to Manual (not Disabled) and start it if it's stopped.

If the service won't start

If the RPC service won't start or keeps stopping, you may have a deeper issue – like a corrupted system file. Run the System File Checker:

sfc /scannow

Then run DISM to repair the Windows image:

DISM /Online /Cleanup-Image /RestoreHealth

Both commands need an admin command prompt. They take a while – the DISM one especially. Let them finish. Don't close the window.

I've seen this happen after a failed Windows update. The RPC service gets in a weird state, and only a full system file repair fixes it.

Quick-reference summary

Start with the IPv6 fix – it's the most common and the quickest. If that doesn't work, move to the Winsock reset. And if you're still stuck, the RPC service check is your last stop before calling in more advanced help.

One more thing: if you're getting this error on a server, make sure the server's network adapter is set to allow IPv6 as well. Sometimes a group policy applies to servers differently. And if you're using a legacy application that requires IPv4 only, you might need to set the RPC service to use IPv4 specifically – but that's rare and usually involves editing the registry. Skip that unless you're really sure that's your situation.