Fix Network Printer Not Connecting in Windows 11 (2026 Guide)

Introduction

Network printers are essential in both home and office environments, but Windows 11 changed how printer communication works and broke many existing setups. Starting with Windows 11 22H2, Microsoft tightened RPC (Remote Procedure Call) security for printing, and a large number of network and shared printers stopped responding. If the printer shows as offline, cannot be found, or refuses to print, you are hitting one of the most common Windows 11 printer faults.

The failure appears in several forms: the printer is not detected during installation, it shows as offline while powered on and connected, print jobs sit in the queue indefinitely, or Windows reports "Windows cannot connect to the printer" or "Operation failed with error 0x00000709". Both USB printers shared over a network and direct network printers with their own IP address can be affected.

This guide works through fourteen fixes in diagnostic order, from a cable check to registry and Group Policy changes. It includes copy-ready commands, expected output, a root-cause table and a before-and-after check.

Problem Description

Windows 11 network printer failures occur when the operating system cannot establish or maintain communication with a printer over the network. The printer may be connected by Ethernet or Wi-Fi, or shared from another computer on the same network segment.

Since Windows 11 22H2, Microsoft changed the default RPC protocol for print communication from RPC over TCP to RPC over named pipes. The change improves security but breaks connectivity with printers and print servers configured for the older protocol. Windows 11 security updates also changed how the Print Spooler service operates, which affects network printer connections in ways that are not always obvious.

Symptoms

  • The network printer shows as Offline in Devices and Printers.
  • "Windows cannot connect to the printer" is displayed.
  • Print jobs stay in the queue with an Error status.
  • The printer is not detected by the Add Printer wizard.
  • "Operation could not be completed (error 0x00000709)" appears when connecting.
  • The printer worked before a Windows update and stopped afterwards.
  • Double-clicking the printer shows "Printer is offline".
  • The printer is visible in the network but cannot print.
  • The Print Spooler service stops repeatedly.
  • Printer driver installation fails over the network.

Root Causes

Root causeTypical clueFirst fix
RPC protocol mismatch (22H2 and later)Started after a Windows updateStep 7
RpcAuthnLevelPrivacyEnabled enforcedError 0x00000709 on connectStep 6
Print Spooler stopped or hungQueue frozen, service not runningStep 2
Printer IP address changed by DHCPPrinter answers to ping, Windows shows offlineStep 10
Corrupted or incompatible driverDriver install fails or printer hangsStep 5
Firewall blocking RPC or SMBWorks on one PC, not anotherStep 9
Network discovery disabledPrinter not visible in the networkStep 9
Wrong subnet or VLANPing to the printer failsStep 3
Stale printer entry after an updateOld queue with error statusStep 13
Printer firmware bugDrops off the network after idleStep 11

Before You Start

Collect three facts before changing anything: the printer's IP address, the PC's IP address, and whether the printer responds to ping. These three checks separate a network problem from a Windows problem.

  1. Print a network configuration page from the printer's control panel, or read the IP from Settings > Network on the printer.
  2. Open Terminal and note the PC's IPv4 address and subnet mask.
PowerShell
Get-NetIPConfiguration | Select-Object InterfaceAlias, IPv4Address, IPv4DefaultGateway
Test-NetConnection 192.168.1.50 -Port 9100

Expected output when the printer is reachable:

Output
ComputerName     : 192.168.1.50
RemotePort       : 9100
TcpTestSucceeded : True

Step 1: Run the Printer Troubleshooter

Windows 11 includes a built-in printer troubleshooter that detects and resolves common issues.

  1. Press Windows key + I and open System > Troubleshoot > Other troubleshooters.
  2. Click Run next to Printer and follow the prompts.
  3. Note any problem the troubleshooter reports, even if it cannot fix it, because the message usually identifies the layer that failed.

Step 2: Restart the Print Spooler Service

A stopped or hung Print Spooler is the most common cause of printer connection failures.

  1. Press Windows key + R, type services.msc and press Enter.
  2. Right-click Print Spooler and select Stop.
  3. Open File Explorer and navigate to C:\Windows\System32\spool\PRINTERS.
  4. Delete all files in the PRINTERS folder to clear stuck print jobs.
  5. Return to services.msc, right-click Print Spooler and select Start.
  6. Confirm that Startup type is Automatic.
  7. Restart the computer and test the printer.
PowerShell
Stop-Service Spooler -Force
Remove-Item C:\Windows\System32\spool\PRINTERS\* -Force -ErrorAction SilentlyContinue
Set-Service Spooler -StartupType Automatic
Start-Service Spooler
Get-Service Spooler | Select-Object Name, Status, StartType

Step 3: Verify the Printer Is on the Same Network

Confirm that the PC and printer are on the same network segment. Compare the first three octets of both addresses: 192.168.1.x and 192.168.1.y are on the same subnet, while 192.168.1.x and 192.168.2.y are not.

PowerShell
ipconfig | Select-String -Pattern "IPv4"
Test-Connection 192.168.1.50 -Count 4

If ping fails, the problem is the network, not Windows. Check the cable, the Wi-Fi band, VLAN assignment and any guest-network isolation before continuing.

Step 4: Add the Printer by IP Address

If Windows does not detect the printer automatically, add it manually using the IP address. This bypasses discovery, which is often what is broken.

  1. Open Settings > Bluetooth & devices > Printers & scanners > Add device.
  2. Click Add manually when prompted.
  3. Select Add a printer using an IP address or hostname.
  4. Set Device type to TCP/IP Device.
  5. Enter the printer's IP address and clear the Query the printer checkbox.
  6. Click Next and follow the prompts.
Connection typePortUse when
TCP/IP (raw)9100Most modern network printers
IPP631Printers that advertise IPP or driverless printing
LPR515Older print servers and Unix-style queues
WSDDynamicDiscovery-based installs that keep failing

Step 5: Update or Reinstall the Printer Driver

Outdated or corrupted drivers are a frequent cause of connection problems.

  1. Download the latest Windows 11 driver from the printer manufacturer.
  2. Remove the printer from Printers & scanners.
  3. Restart the computer.
  4. Install the downloaded driver, then add the printer again.
PowerShell
Get-PrinterDriver | Select-Object Name, Manufacturer, DriverVersion
Get-Printer | Select-Object Name, DriverName, PortName, PrinterStatus

Step 6: Disable RpcAuthnLevelPrivacyEnabled

This registry setting is the primary cause of network printer connection failures on Windows 11 22H2 and later.

  1. Press Windows key + R, type regedit and press Enter.
  2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print.
  3. Right-click in the right pane, choose New > DWORD (32-bit) Value.
  4. Name it RpcAuthnLevelPrivacyEnabled and set the value to 0.
  5. Click OK, close Registry Editor and restart the computer.
PowerShell
New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Print" `
  -Name "RpcAuthnLevelPrivacyEnabled" -PropertyType DWord -Value 0 -Force
Get-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\Print" -Name "RpcAuthnLevelPrivacyEnabled"

Step 7: Configure RPC Connection Settings with Group Policy

On Windows 11 Pro, Enterprise or Education, Group Policy is the cleaner way to set the RPC transport.

  1. Press Windows key + R, type gpedit.msc and press Enter.
  2. Navigate to Computer Configuration > Administrative Templates > Printers.
  3. Double-click Configure RPC connection settings.
  4. Select Enabled and set the protocol to RPC over named pipes.
  5. Click Apply and OK, then restart.

Home editions do not include gpedit.msc. The equivalent registry values live under HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Printers\RPC.

Step 8: Configure RPC Listener Settings

Some network printers need the RPC listener to accept both named pipes and TCP connections.

  1. Open gpedit.msc.
  2. Navigate to Computer Configuration > Administrative Templates > Printers.
  3. Double-click Configure RPC listener settings.
  4. Select Enabled and set the protocols to RPC over named pipes and TCP.
  5. Apply the change and restart.

Use the narrowest setting that works. If named pipes alone fixes the printer, do not also enable TCP.

Step 9: Turn On Network Discovery and File and Printer Sharing

Windows needs these features to detect shared printers.

  1. Open Control Panel > Network and Sharing Center > Change advanced sharing settings.
  2. Under the Private profile, turn on network discovery and file and printer sharing.
  3. Save the changes.
PowerShell
Get-NetFirewallRule -DisplayGroup "File and Printer Sharing" |
  Where-Object { $_.Enabled -eq 'False' } |
  Select-Object DisplayName, Profile, Enabled

If the firewall rules are disabled, enable the group rather than creating ad-hoc rules:

PowerShell
Enable-NetFirewallRule -DisplayGroup "File and Printer Sharing"

Step 10: Reset the TCP/IP Port

If the printer's IP address changed, the Windows TCP/IP port still points at the old address. That produces the classic "printer answers to ping but Windows says offline" symptom.

  1. Open Control Panel > Devices and Printers.
  2. Right-click the printer and choose Printer properties.
  3. Open the Ports tab.
  4. Select the current TCP/IP port and click Configure Port.
  5. Update the IP address and click OK.
PowerShell
Get-PrinterPort | Where-Object { $_.Name -like "*IP*" } | Select-Object Name, PrinterHostAddress, PortNumber

Step 11: Run the Printer's Wireless Connectivity Test

Most network printers include a self-diagnostic for wireless connectivity. On the printer's control panel, open Settings > Network or Wi-Fi and look for a connectivity or network test option. The report usually includes signal strength, IP address, gateway and DNS, which is enough to prove whether the printer or Windows is at fault.

Step 12: Reset the Print System with PowerShell

For administrators, the whole spooler reset can be scripted.

PowerShell
$ErrorActionPreference = 'Continue'
Stop-Service Spooler -Force
Remove-Item C:\Windows\System32\spool\PRINTERS\* -Force -ErrorAction SilentlyContinue
Set-Service Spooler -StartupType Automatic
Start-Service Spooler

# Optional: clear the per-user printer connection cache
Remove-Item "HKCU:\Printers\Connections\*" -Recurse -Force -ErrorAction SilentlyContinue

Log the result with Start-Transcript when you need an audit trail for a support ticket.

Step 13: Remove and Re-add the Network Printer

A stale printer entry can keep failing even after the underlying problem is fixed.

  1. Open Settings > Bluetooth & devices > Printers & scanners.
  2. Select the problem printer and click Remove device.
  3. Restart the computer.
  4. Add the printer again, by IP address if discovery still fails.

Step 14: Install the Latest Windows 11 Cumulative Update

Microsoft regularly ships printer fixes in cumulative updates. Open Settings > Windows Update > Check for updates and install everything pending, then restart.

PowerShell
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5 HotFixID, InstalledOn

Verify the Fix

CheckBefore (broken)After (fixed)
Test-NetConnection <printer-ip> -Port 9100TcpTestSucceeded : FalseTcpTestSucceeded : True
Printers & scanners statusOfflineReady
Print a test pageJob stays in queuePage prints
Get-Service SpoolerStoppedRunning, Automatic
Printer Properties > PortsOld IP addressCurrent IP address
Event Viewer > SystemSpooler crash eventsNo new spooler errors

Frequently Asked Questions

Why did my network printer stop working after a Windows 11 update?

Windows 11 22H2 and later introduced RPC security changes that break legacy network printer connections. The RpcAuthnLevelPrivacyEnabled registry fix or the equivalent Group Policy setting restores compatibility.

What is RpcAuthnLevelPrivacyEnabled?

It is a registry value that enforces authentication privacy for print RPC calls. Setting it to 0 disables that enforcement and restores compatibility with older printers and print servers.

My printer shows as offline but I can ping it. Why?

The Windows TCP/IP port probably points at an old IP address. Update the port configuration under Printer Properties > Ports > Configure Port.

How do I find my printer's IP address?

On most printers, open the control panel and go to Settings > Network or Wi-Fi. You can also print a network configuration page from the printer menu.

Do I need to edit the registry to fix printer problems?

Only for the 22H2 RPC issue. For other faults, start with the spooler restart, the IP port check and a driver update, and leave the registry alone.

Can firewall settings block network printers?

Yes. Windows Defender Firewall must allow File and Printer Sharing, and RPC needs port 135 plus the dynamic RPC range. Check inbound rules for blocked printer traffic.

Why does the Print Spooler keep stopping?

Corrupted print jobs, incompatible drivers or a recent Windows update can crash the spooler. Clear the queue, update the driver, and check Event Viewer for the faulting module.

How do I add a network printer without automatic detection?

Use the manual method: Settings > Bluetooth & devices > Printers & scanners > Add device > Add manually > Add a printer using an IP address.

Which ports are required for network printing?

RPC Endpoint Mapper (TCP 135), the dynamic RPC range (TCP 49152-65535), raw printing (TCP 9100) and SMB (TCP 445) for shared printers.

Will System Restore fix printer problems?

It can revert printer-related settings to an earlier working state, but it does not repair a bad driver or a changed IP address.

Can I use USB instead of network printing?

Yes. If the printer has a USB port, a direct connection bypasses the network faults entirely, which is a useful way to prove the printer itself is healthy.

Do I need admin rights to install a network printer?

Installing drivers and changing print settings requires administrative rights. Adding a printer to an existing, already-installed queue sometimes does not.

Conclusion

Network printer failures in Windows 11 usually come from the RPC security changes introduced in 22H2, combined with driver incompatibility, a changed IP address and spooler faults. Work in order: restart the spooler, confirm the printer's address, update the TCP/IP port, then apply the RPC fix if the printer still refuses to connect.

For most users, the spooler restart, the IP check and the port update resolve the problem in a few minutes. For persistent legacy hardware, Group Policy or the registry change provides a durable fix. Administrators should script the spooler reset, set DHCP reservations for printers, and standardise drivers to prevent the problem from recurring.

We Value Your Privacy

We use cookies to improve your browsing experience, analyze traffic, and display relevant advertisements.