🌐 Connection cluster

Printer not found on network

🔍

Specific issue? Can't connect printer to Wi-Fi · Printer keeps disconnecting · Blocked by firewall or antivirus · Router compatibility issue. If the printer shows as offline rather than not found, see the offline guide.

Quick answer

When a printer is not found during setup or disappears from the network, it almost always has a different IP address than expected. Print a network configuration page from the printer's own control panel — it shows the current IP address. Add the printer manually using that IP address instead of relying on auto-discovery. Then assign the printer a static IP in your router's DHCP reservation settings so it never changes again.

⚡ Quick checks

Print a network configuration page from the printer's control panel — this shows the printer's current IP, SSID, and connection status
Confirm the printer shows "Connected" and the correct SSID on that page — not guest network, not wrong band
On the computer: Settings → Printers & Scanners → Add device → wait for auto-discovery. If not found, click "Add manually" → add by IP address using the IP from the config page
Confirm the computer and printer are on the same network — VPN on the computer routes traffic away from local devices
Power cycle router, printer, and computer in that order with 30-second pauses between each

Why printers disappear from the network

IP address changed — router restarted and DHCP assigned a new IP; auto-discovery uses the old address. This is the cause in roughly 70% of cases.
Printer connected to wrong network — after a router replacement or ISP change, the printer still has the old Wi-Fi credentials and can't connect
Network isolation / AP isolation enabled — many routers and mesh networks have a setting that prevents devices on the same Wi-Fi from communicating with each other. The printer is on the network but the computer can't reach it
Guest network — printer connected to the guest SSID, computer on the main SSID; guest networks are isolated by design
2.4 GHz vs 5 GHz band split — some routers broadcast separate SSIDs per band; printer and computer on different bands may be on different subnets
mDNS / Bonjour blocked — auto-discovery uses multicast DNS (mDNS) packets; some firewalls and routers block these, making discovery fail even when the printer is reachable by IP

Add the printer manually by IP address

Auto-discovery is unreliable on complex networks. Adding by IP is faster and more stable.

Find the printer's IP: print a network configuration page from Setup → Reports → Network Configuration Page (or similar depending on brand)
Windows: Settings → Bluetooth & devices → Printers & scanners → Add device → scroll down → "Add manually" → "Add a printer using an IP address or hostname" → enter the IP
macOS: System Settings → Printers & Scanners → + → IP tab → enter the printer's IP → select the correct driver
After adding: print a test page from Printer properties to confirm communication
Prevent recurrence: log into your router admin panel → DHCP Reservations → reserve the printer's IP for its MAC address

Check for AP isolation and network isolation

Access Point (AP) isolation — also called client isolation, wireless isolation, or SSID isolation — is a router security feature that prevents Wi-Fi devices from communicating with each other directly. It's designed to protect users on guest networks and public hotspots, but if accidentally enabled on the main network, it breaks printer discovery entirely.

To check: log into your router admin panel (usually 192.168.1.1 or 192.168.0.1) → Wi-Fi settings → look for "AP Isolation," "Client Isolation," or "Wireless Isolation." It must be disabled on the network your printer and computer both use.

💡

Mesh networks: Google Nest, Eero, Orbi, and similar mesh systems sometimes place wired and wireless devices on different subnets. If the printer is on Ethernet and the computer is on Wi-Fi (or vice versa), check whether your mesh system has "bridge mode" or "unified network" enabled. All devices should be on the same subnet for printing to work.

Check using ping and browser test

# Windows Command Prompt or PowerShell
ping 192.168.1.X # Replace with printer's IP from its network page

# If ping responds, open browser and navigate to:
# http://192.168.1.X — printer's web interface should load

# If ping fails entirely: network path issue (wrong network, AP isolation, firewall)
# If ping works but discovery fails: mDNS/Bonjour blocked — add by IP manually

Official support

HP

Canon

Canon support

Epson

Brother

Brother support

📶 Wi-Fi connection

Cannot connect printer to Wi-Fi

🔍

This covers initial Wi-Fi setup failures and reconnecting after a router/password change. For a printer that was working and disappeared, see printer not found on network. For repeated disconnections, see keeps disconnecting.

Quick answer

Most Wi-Fi connection failures during setup are caused by the printer trying to connect to the wrong SSID, a 5 GHz-only SSID the printer doesn't support, or an incorrect Wi-Fi password entry. Most home printers only support 2.4 GHz Wi-Fi — they will not appear in the device list on a 5 GHz-only network. If your router broadcasts separate SSIDs per band, connect the printer to the 2.4 GHz SSID specifically.

⚡ Quick checks

Confirm the target SSID is 2.4 GHz — most printers do not support 5 GHz. If your router uses a single SSID for both bands, move the printer closer to force 2.4 GHz association
Re-enter the Wi-Fi password on the printer's control panel — passwords are case-sensitive and special characters can be tricky to enter on small keypads
Temporarily disable WPA3 security in your router if your printer only supports WPA2 — reconnect, then re-enable WPA3
Use WPS setup if your router has a WPS button — press WPS on router, then start WPS setup on printer within 2 minutes
If nothing works: connect via USB first, use the brand's setup software (HP Smart, Canon PRINT, Epson Connect) to complete Wi-Fi configuration

2.4 GHz vs 5 GHz — the most common cause

Most consumer inkjet and laser printers only have 2.4 GHz Wi-Fi radios. Modern routers often broadcast both 2.4 GHz and 5 GHz as either separate SSIDs (e.g., "HomeNetwork" and "HomeNetwork_5G") or a single merged SSID that automatically assigns devices to the fastest available band.

When using a merged SSID, a phone or laptop close to the router will connect to 5 GHz — but the printer will either fail to connect or connect intermittently because the router keeps trying to negotiate 5 GHz first. The solution is either to use the separate 2.4 GHz SSID for the printer, or to temporarily connect the printer during setup while it's in the same room as the router (which forces 2.4 GHz due to signal characteristics).

WPA3 and security protocol mismatches

Many routers purchased after 2020 default to WPA3 security or WPA2/WPA3 transition mode. Older printers (and some current budget models) only support WPA2 or WPA/WPA2 mixed mode. If the printer fails to connect to a network that works fine for all other devices, the security protocol mismatch is likely. The fix: log into your router admin panel → Wi-Fi security settings → change from WPA3-only to WPA2/WPA3 mixed mode. This allows the printer to connect using WPA2 while other devices continue using WPA3.

USB-first setup method (most reliable)

When wireless setup fails repeatedly, all major brands support a USB-first setup path that is more reliable than the printer's own wireless setup wizard:

Connect the printer to the computer via USB cable — standard USB-A to USB-B or USB-A to USB-C depending on model
Download and run the brand's full setup software: HP Smart · Canon PRINT · Epson Connect · Brother setup
The software detects the printer via USB and offers to configure the wireless settings — it transfers your Wi-Fi credentials to the printer automatically
Once Wi-Fi configuration completes, disconnect the USB — the printer now appears on the network

→

Back to cluster

Printer not found on network — all causes

→

⚡ Repeated disconnections

Printer keeps disconnecting from Wi-Fi

🔍

This covers printers that connect successfully but drop the connection repeatedly. For initial setup failure, see can't connect to Wi-Fi. For offline status after disconnection, see the offline guide.

Quick answer

Printers that repeatedly disconnect usually have one of three root causes: the printer's Wi-Fi sleep mode cuts the radio during idle periods (fix: disable Wi-Fi sleep in the printer's power management settings), the DHCP lease expires and the new IP isn't handled by the computer (fix: assign a static IP), or the router's band steering keeps trying to move the printer to 5 GHz (fix: use the 2.4 GHz-only SSID or assign a fixed channel in the router). Assign a static IP regardless — it eliminates the IP-change component of any disconnection.

⚡ Quick checks

Disable the printer's Wi-Fi sleep / power save mode — this is the fix for the majority of "drops during idle" disconnections
Assign a static IP via router DHCP reservation — prevents the reconnection-after-IP-change failure pattern
Move the printer closer to the router or access point — weak signal causes reconnection attempts that often pick up the wrong band
Assign a fixed Wi-Fi channel in your router (channels 1, 6, or 11 for 2.4 GHz) — channel congestion causes intermittent drops
Check for router firmware updates — some models have known Wi-Fi stability bugs fixed in firmware updates

Diagnosing the pattern — which type of disconnect is it?

Pattern	Primary cause	Fix
Drops after idle for 30+ minutes	Wi-Fi sleep mode	Disable Wi-Fi sleep in printer power settings
Drops then re-shows at a different IP	DHCP lease expiry / reassignment	DHCP reservation (static IP) in router
Drops during active print jobs	Weak signal or channel congestion	Move printer closer; fix router channel
Drops when other devices join the network	Band steering pushing to 5 GHz	Use 2.4 GHz-only SSID; disable band steering
Drops daily at specific time	Router scheduled restart or DHCP renewal	Disable scheduled router restart; static IP

Disable band steering on your router

Band steering is a router feature that automatically moves capable devices to the 5 GHz band for better performance. It works well for phones and laptops but causes problems for printers: the printer doesn't support 5 GHz, so when the router tries to steer it, the connection drops. The router keeps retrying, causing a loop of drops and reconnections.

To fix: either disable band steering entirely in the router admin panel, or create a separate 2.4 GHz-only SSID for the printer. The printer connects to that SSID permanently; band steering only affects the main merged SSID that phones and laptops use.

→

After disconnection

Printer shows offline — remove, re-add, and set static IP

→

🔒 Firewall / antivirus

Printer blocked by firewall or antivirus

🔍

This covers printers blocked by Windows Firewall, third-party firewalls, or antivirus network protection. For a printer not found at all (before firewall is a factor), see not found on network.

Quick answer

Firewalls and antivirus software block printer communication by filtering the specific ports and protocols printers use: port 9100 (raw printing), port 631 (IPP/CUPS), UDP port 5353 (mDNS/Bonjour discovery), and TCP port 515 (LPD/LPR). The diagnostic test: temporarily disable the firewall or antivirus entirely, then try printing. If it works immediately, the security software is the cause. Add the printer's IP or the printer-related ports as exceptions rather than leaving the firewall disabled.

⚡ Quick checks

Temporarily disable Windows Firewall: Control Panel → Windows Defender Firewall → Turn off (test, then re-enable)
Temporarily disable any third-party antivirus network shield (Norton, McAfee, Kaspersky, Bitdefender) — test printing while disabled
If printing works while firewall is off: add the printer's IP as a trusted address in the firewall settings rather than leaving it disabled
Check if a VPN is running — VPNs reroute all traffic away from the local network, making the printer unreachable regardless of firewall settings

Ports printers use — what to allow

Port / Protocol	Used for	Direction
TCP 9100	Raw printing (most common path)	Computer → Printer
UDP 5353	mDNS / Bonjour (auto-discovery)	Both
TCP 631	IPP (Internet Printing Protocol) / CUPS	Computer → Printer
TCP 515	LPD / LPR (older protocol)	Computer → Printer
TCP 80 / 443	Printer's embedded web server (EWS)	Computer → Printer
UDP 161	SNMP (status monitoring)	Both

The most important ports to allow are TCP 9100 (printing) and UDP 5353 (discovery). If you can print after enabling just these two, the others are optional.

Adding a Windows Firewall exception

Control Panel → Windows Defender Firewall → Advanced Settings
Inbound Rules → New Rule → Port → TCP → specific local ports: 9100, 631, 515
Allow the connection → apply to Private and Domain profiles (not Public) → name it "Printer communication"
Repeat for UDP rule with port 5353 for mDNS discovery
Alternatively: add the printer's IP as a trusted IP range under Inbound Rules → New Rule → Custom → All programs → IP Addresses → enter the printer's IP

Third-party antivirus network shield

Norton, McAfee, Kaspersky, Bitdefender, and similar products have a "network threat protection" or "firewall" component separate from Windows Firewall. Both can be running simultaneously, and the antivirus firewall may be the blocker even after adding Windows Firewall exceptions. Look in the antivirus console for a "Network" or "Firewall" section → add the printer's IP to the trusted devices list.

💡

VPN note: If a VPN is running when you try to print, traffic goes through the VPN tunnel to the remote server rather than to the local network. The printer is on the local network. Disconnect the VPN before printing, or check whether your VPN supports "split tunneling" — which allows local network traffic to bypass the VPN.

Back to cluster

Printer not found on network — all causes

→

📡 Router compatibility

Printer router compatibility issues — mesh, band steering, WPS

🔍

This covers router-specific issues that cause printers to fail even when other devices work fine. For firewall blocking, see firewall guide. For Wi-Fi password or initial setup, see can't connect to Wi-Fi.

Quick answer

Modern routers have features designed for smartphones and laptops that actively break printer connectivity: band steering (pushes 2.4 GHz-only printers to 5 GHz and drops them), AP isolation (blocks device-to-device communication), WPA3-only security (incompatible with older printer firmware), and mesh backhaul routing that places wired and wireless devices on different subnets. Each of these requires a specific router setting change, not anything on the printer.

⚡ Quick checks

Check if your router has AP isolation / client isolation enabled — this blocks all device-to-device communication on Wi-Fi
If your router is a mesh system (Eero, Google Nest, Orbi, Velop): ensure the printer and computer are on the same "node" or that the mesh is in bridge mode
Create a dedicated 2.4 GHz-only SSID for the printer if your router allows it — removes all band-steering interference
Check security protocol: WPA3-only breaks older printers. Use WPA2/WPA3 mixed mode instead
Disable "Smart Connect" or "Band Steering" in the router admin panel if the printer drops repeatedly

Compatibility issues by router feature

Router feature	Effect on printer	Setting to change
AP / Client Isolation	Computer can't reach printer — appears offline or not found	Disable on main SSID; OK to keep on guest SSID
Band Steering / Smart Connect	Printer dropped repeatedly; can't hold 2.4 GHz connection	Disable, or create separate 2.4 GHz SSID
WPA3-only security	Printer can't authenticate; fails at password step	Change to WPA2/WPA3 mixed mode
Mesh — separate subnets	Printer on different subnet from computer; unreachable	Enable bridge mode; ensure unified subnet
DHCP lease too short	IP changes frequently; printer appears and disappears	Extend DHCP lease to 24h or use reservation
mDNS isolation	Auto-discovery fails; printer not visible in Add Printer	Enable mDNS proxy or mDNS forwarding
WPS disabled	WPS button setup method unavailable	Enable WPS temporarily for setup, disable after

Mesh network printer setup

Mesh Wi-Fi systems (Eero, Google Nest WiFi, Orbi, Velop, Deco) are designed to seamlessly move devices between nodes. This works well for mobile devices but causes issues for printers because the printer's IP may be associated with one node while the computer connects through a different node — depending on the mesh system's implementation, these may be treated as different network segments.

The most reliable approach with mesh systems: connect the printer via Ethernet to one of the mesh nodes if possible. This gives the printer a stable, wired connection that doesn't change with mesh node reassignment. If Wi-Fi only: ensure the printer is positioned close to the main router node (not a satellite node), and assign a static IP via the mesh system's DHCP reservation feature.

Back to cluster

Printer not found on network — add by IP, static IP

→

Printer not found on network

Why printers disappear from the network

Add the printer manually by IP address

Check for AP isolation and network isolation

Check using ping and browser test

Official support

Cannot connect printer to Wi-Fi

2.4 GHz vs 5 GHz — the most common cause

WPA3 and security protocol mismatches

USB-first setup method (most reliable)

Printer keeps disconnecting from Wi-Fi

Diagnosing the pattern — which type of disconnect is it?

Disable band steering on your router

Printer blocked by firewall or antivirus

Ports printers use — what to allow

Adding a Windows Firewall exception

Third-party antivirus network shield

Printer router compatibility issues — mesh, band steering, WPS

Compatibility issues by router feature

Mesh network printer setup

Related problems