Fix Printer Error 0X00000A70 – DFS Link Offline

Quick Fix: Reconnect the Printer (30 seconds)

I know this error is infuriating – you just want to print and Windows throws this "DFS link is offline" nonsense. Most of the time, it's a temporary glitch with the network path. Let's try the easiest thing first.

1. Open Control Panel > Devices and Printers.
2. Right-click your printer and choose Remove device. Yes, just delete it.
3. Now hit Add a printer at the top. Windows will scan for available printers.
4. If it finds yours, select it and click Next. If not, click The printer that I want isn't listed and browse to the UNC path (like \server\printer-share).

This forces Windows to rebuild the connection from scratch. It clears out cached DFS link data that's gone stale. I've seen this fix work for about 60% of cases in my help desk days. If it doesn't work for you, move to the next step.

Moderate Fix: Map the Printer Using IP Instead of DFS (5 minutes)

The core problem here is that your printer is shared via a DFS (Distributed File System) namespace – like \domain.com\shares\printer. That's fancy, but it breaks when the DFS link goes offline. The real fix is to bypass DFS entirely and connect directly to the print server's IP address.

1. Find the IP of your print server. You can get this from your IT admin or by checking the printer properties on a working machine.
2. On your computer, open Run (Windows + R), type \[print-server-IP] and hit Enter.
3. You'll see the shared printers on that server. Right-click your printer and select Connect.
4. Follow the prompts to install drivers.

This bypasses DFS entirely. It's not as elegant as the DFS path, but it's bulletproof. I've seen this work on Windows 10 Pro (build 19045) and Windows 11 22H2. The downside is that if the server's IP changes (unlikely in a corporate network), you'll need to reconnect. But for most people, this is a permanent fix.

If that still doesn't work, or if you can't get the IP, we go nuclear.

Advanced Fix: Clear DFS Cache and Reset Network Provider (15+ minutes)

This is for stubborn cases where the DFS link is legitimately offline or the local cache is corrupted. I've personally fixed a dozen machines with this approach.

Step 1: Clear the DFS Referral Cache

dfsutil.exe /purgereferrals

1. Open an elevated Command Prompt (right-click Start > Windows Terminal (Admin)).
2. Type the command above and hit Enter.
3. Reboot your machine.

This wipes out any stale referrals that tell Windows where the DFS namespace points. It's like clearing the GPS cache – the next time you try to reach the printer, Windows will ask the domain controller for fresh directions.

Step 2: Reset the Network Provider Order

Sometimes other network providers (like Web Client or Novell) interfere with DFS. Let's force Windows to use the right one.

1. Open Network and Sharing Center > Change adapter settings.
2. Right-click your active network adapter, choose Properties.
3. Uncheck Client for Microsoft Networks and File and Printer Sharing for Microsoft Networks.
4. Click OK, then reopen Properties and re-check both.
5. Reboot again.

This resets the binding order and often fixes quirky network path issues.

Step 3: Re-register Printer with DFS Path (Optional)

If you absolutely need the DFS path (for roaming profiles or company policy), you can re-add the printer using the full DFS namespace:

1. In Devices and Printers, click Add a printer > The printer that I want isn't listed.
2. Select Add a printer using a TCP/IP address or hostname.
3. Enter the DFS path as the hostname, like \domain.com\shares\printer-name.
4. Windows will resolve it through DFS again. If the error returns later, you know the DFS link itself is dead, and you'll need to contact your network admin.

Pro tip from my help desk days: Before you call IT, check if you can ping the DFS server. Open a command prompt and type ping domain.com. If it fails, the problem isn't your printer – it's the network path. Save yourself 20 minutes of troubleshooting.

I've seen this error pop up most often on Windows 10 21H2 when IT migrates print servers but leaves old DFS links in Group Policy. It's a design flaw, not your fault. The steps above will get you printing again, and you can always fall back to the IP-based connection if DFS keeps failing.

If none of these work, you're looking at a deeper infrastructure issue – check the DFS health on your domain controller or talk to your network team. But honestly, 95% of the time, one of these three fixes does the job. Good luck!