Why is my HP printer not showing up on the network? — Complete troubleshooting guide

When your HP printer doesn’t appear on the network it’s maddening: machines can’t print, phones can’t scan, and productivity grinds to a halt. The good news is that the problem almost always falls into a handful of network, configuration, or hardware categories — and most of those are fixable with methodical checks. This guide walks you from quick fixes to deep diagnostics, covering wired and wireless setups, routers, firewalls, OS-specific tips (Windows, macOS, Linux, Chromebooks, Android/iOS), enterprise issues (VLANs, print servers), and preventive measures.

Quick checklist

Before launching into advanced diagnostics, run this short list — it solves many “not showing up” cases:

1. Is the printer powered on and showing Ready?

2. Is the printer connected to the correct network (same SSID/subnet) — not a guest network or hotspot?

3. Can you print a network configuration page from the printer (shows IP, SSID, MAC)?

4. Is the printer wired (Ethernet) cable firmly seated and link light on the router/switch active?

5. Restart the printer, router, and the client device you're using to search for the printer.

6. Check that Wi-Fi Direct isn’t active (that can make the printer temporarily invisible to the Wi-Fi network).

7. If the printer is connected to the router, open a browser and try to reach the printer’s Embedded Web Server (type its IP).

If any of the above reveals the printer is on a different network, offline, or has a bad cable, fix that and recheck discovery.

Why printers disappear — the common root causes

1. Different network/subnet — device and printer aren’t on the same broadcast domain (common with guest networks, VPNs, or multi-AP setups).

2. Printer lost its DHCP lease / IP changed — the printer got a new IP and clients are still looking for the old one.

3. AP/client isolation / guest network — router blocks device-to-device discovery.

4. mDNS/Bonjour or SSDP is blocked — discovery protocols used by AirPrint, Mopria, and many HP features are filtered at the router or by a firewall.

5. Firewall on PC or network device — inbound discovery packets (UDP 5353, etc.) blocked.

6. Wrong Wi-Fi band or band steering — printer on 2.4 GHz, device on 5 GHz separated by AP isolation or different SSIDs.

7. Cable or port failures (Ethernet) — link light off or flakey.

8. Printer sleep or power-save mode — some printers sleep deeply and don’t respond to discovery until woken.

9. Firmware bugs or corrupted network stack — printers occasionally need firmware updates or network resets.

10. Printer set to Wi-Fi Direct or offline mode — internal settings can disable normal network discovery.

Step-by-step troubleshooting (start here, proceed until fixed)

Step 1 — Confirm physical and power state

• Is the printer powered on and showing “Ready,” not an error?

• For Ethernet: check the RJ45 cable, swap cable and router port, look for link/activity LEDs.

• For Wi-Fi: verify the printer’s wireless icon is lit and not showing an error. Print a Network Configuration Page (printer menu → Reports/Network) — note SSID, IP, subnet mask, and gateway.

Step 2 — Verify network membership and IP

• On the network report, confirm the IP address and the SSID. If no IP or 0.0.0.0, the printer didn’t get DHCP — try reconnecting it to Wi-Fi or using a static IP in your LAN range.

• On a PC in the same room, open a Command Prompt/Terminal and ping the printer IP:
  ping 192.168.1.45
  If pings succeed, basic connectivity exists. If ping fails, note “Request timed out” (no response) or “Destination host unreachable” (routing issue).

Step 3 — Check for AP isolation / guest network

• Many routers have a Guest SSID with client isolation that prevents devices from seeing each other. Ensure both printer and client are on the same primary SSID.

• If using a dual-band router with band steering, temporarily split SSIDs (e.g., MyWiFi-2G and MyWiFi-5G) and force both printer and your device onto the same band to test.

Step 4 — Check multicast and discovery protocols

• Home routers sometimes block mDNS/Bonjour (UDP 5353) or SSDP — those are used by AirPrint and many HP discovery tools. On your router, ensure multicast or mDNS/Bonjour forwarding is enabled or at least not filtered.

• Small business networks with managed switches may block multicast by default — ask your network admin to allow mDNS through or enable Bonjour Gateway.

Step 5 — Verify DNS, DHCP reservation, and static IP

• If the printer has a dynamic IP that changes, clients may still search for an old address. Reserve the printer’s MAC address in the router DHCP table to give it a static/dhcp-reserved IP.

• Alternatively, set the printer to a static IP within your LAN range (outside DHCP pool or reserved) via the printer’s network settings.

Step 6 — Check firewall/antivirus on client machines

• On Windows, ensure File and Printer Sharing, Function Discovery Provider Host, and Function Discovery Resource Publication services are running for network discovery.

• Temporarily disable the PC firewall to test whether the printer appears. If it appears with the firewall off, add exceptions for discovery protocols or the HP software.

• For macOS, ensure Block all incoming connections is not enabled in Security & Privacy → Firewall Options; also enable mDNSResponder/Bonjour-related services.

Step 7 — Try direct access to Embedded Web Server (EWS)

• If the network page showed an IP, open a browser and go to that IP (e.g., http://192.168.1.45). If EWS loads, the printer is reachable — discovery may be the issue, not printing itself. Use EWS to confirm settings, name, and to update firmware.

Step 8 — Restart network equipment and printer

• Power cycle the printer, the switch/AP the printer is connected to, and the router. This clears ARP caches, DHCP assignments, and transient multicast blocks.

Step 9 — Check printer network mode and Wi-Fi Direct

• Some HP printers prioritize Wi-Fi Direct and will not appear on the normal network while Direct is active. In the printer Wireless settings, disable Wi-Fi Direct or set it to “available” (not always-on) and rejoin the normal SSID.

Step 10 — Update firmware and reset network settings

• In the Embedded Web Server or HP Smart app, check for a firmware update and apply it (do not interrupt). Firmware fixes resolve known network stack bugs.

• If problems persist, perform a network settings reset (usually in Setup → Network Settings → Restore Network Defaults) and reconfigure Wi-Fi/Ethernet from scratch.

OS-specific troubleshooting

Windows (10/11)

• Control Panel → Network and Sharing Center → Advanced sharing settings: enable Network discovery and File and printer sharing.

• Services: ensure Function Discovery Provider Host and Function Discovery Resource Publication are set to Automatic and running.

• Add the printer manually: Settings → Devices → Printers & scanners → Add a printer or scanner → If not found, choose “The printer that I want isn’t listed” → Add a printer using a TCP/IP address or hostname and enter the IP. Choose a suitable driver or IPP model.

macOS

• System Settings → Printers & Scanners → + to add: look under Default or IP tab; use ipp://printer-ip/ipp/print or socket://printer-ip for JetDirect.

• macOS relies heavily on Bonjour: if discovery fails, ensure your router doesn’t block multicast and the Mac is on the same subnet. For AirPrint, printers must advertise via Bonjour.

Linux (CUPS)

• Visit http://localhost:631 (CUPS web UI). Add printer via IPP (ipp://printer-ip/ipp/print) or socket:// and provide a PPD or use IPP Everywhere.

• Confirm avahi-daemon (mDNS) is running for discovery.

Chromebook / ChromeOS

• Settings → Printers → Add printer. If not auto-discovered, add manually using IPP/IPPS and the printer IP. Chromebooks depend on IPP/IPP Everywhere; ensure the printer supports it or use AppSocket if necessary.

Android / iOS (mobile)

• Mobile devices use AirPrint (iOS) or Mopria/HP Smart (Android). Ensure the phone/tablet is connected to the same Wi-Fi SSID and that mDNS/Bonjour is not blocked. On some routers, client isolation prevents mobile discovery.

Router and network configuration details (what to look for)

• Guest Network / Client Isolation: Disable isolation or move printer and clients to the same trusted SSID.

• Multicast & IGMP Snooping: IGMP snooping can block multicast if misconfigured on managed switches — temporarily disable or enable IGMP querier on the network.

• Bonjour / mDNS Repeater / Bonjour Gateway: Many enterprise routers support Bonjour gatewaying across VLANs — use it if printers and users are on different VLANs but need discovery.

• UPnP and SSDP: Some routers block UPnP; enable if you rely on SSDP-based discovery.

• Firewall rules: Allow UDP ports 5353 (mDNS), TCP/UDP 9100 (JetDirect), 631 (IPP), and LPD ports 515 where needed.

• VLANs/Subnets: If printers are on a print VLAN, ensure routing and mDNS reflectors or DNS records are in place for clients to reach them.

Advanced diagnostics (for network-savvy users)

1. Ping the printer IP — basic test.

2. ARP table: arp -a to see if the printer MAC appears.

3. nmap port scan: nmap -sV -p 1-65535 192.168.1.45 to see which services are open (IPP, JetDirect).

4. Packet capture (Wireshark): capture on the client subnet to watch for mDNS announcements (UDP 5353) from the printer. If the printer speaks mDNS but clients don’t see it, router is dropping multicast.

5. Telnet to port 9100: telnet 192.168.1.45 9100 — if connects (blank screen), JetDirect is listening and you have basic TCP connectivity.

6. SNMP check: snmpget -v1 -c public 192.168.1.45 .1.3.6.1.2.1.1.1.0 to query device sysDescr (requires SNMP enabled and community string).

Special cases & fixes

Printer shows IP but not discoverable (EWS accessible)

• If you can load EWS by IP but discovery tools don’t show it, the printer advertises less info or mDNS is blocked. Use manual add by IP on clients or enable mDNS support on network gear.

Printer visible on some clients but not others

• Check client firewall and OS settings (Windows network profile set to Public blocks discovery). Compare network settings and services (Function Discovery, Bonjour).

Ethernet printer blinking link intermittently

• Try different switch port, different cable, turn off energy-saving (EEE) on switch if supported — Energy Efficient Ethernet can cause compatibility issues with some printers.

Printer connected to router but internet-only (no local access)

• Rare: router has isolated the printer to a captive portal or isolated VLAN for IoT. Place printer in the trusted LAN segment or change router settings.

Office with multiple APs — printer disappears when clients roam

• Ensure AP controllers or mesh handle mDNS correctly. Consider moving the printer to a wired connection to avoid roaming issues.

Preventive best practices

1. Reserve DHCP IP for each networked printer — gives predictable addresses.

2. Name printers clearly in EWS (location and function).

3. Keep firmware updated on the printer and major network devices to benefit from bug fixes.

4. Avoid guest networks for printers; use separate VLANs only if Bonjour gatewaying is configured.

5. Document printer IPs, MACs, model, and admin credentials somewhere secure for future troubleshooting.

6. Set conservative sleep settings so printers are discoverable (but balance with energy saving).

7. Use wired connections for critical shared printers to maximize reliability.

When to reset or factory default

Use a network settings reset if the printer’s network configuration is corrupt or you moved it to a different network. Always print a Network Configuration Page first and note settings. After reset, reconnect to Wi-Fi and re-run updates.

When to contact HP support or your IT admin

• If the printer’s Embedded Web Server is unreachable despite correct IP and pings fail even after cable swaps — suspect hardware NIC failure.

• Firmware updates fail or the printer’s network stack repeatedly crashes.

• You’re on a managed corporate network with VLANs and you need mDNS/Bonjour gatewaying or firewall changes — involve IT.

• Warranty-covered printers with network hardware faults — contact HP for service.

Summary: a quick rescue flow

1. Print network report → note IP and SSID.

2. Ping the IP from a client. If ping fails, check cable, switch port, or Wi-Fi join.

3. If IP responds but discovery fails, try manual add by IP (IPP/JetDirect).

4. Check router for guest network / AP isolation / multicast blocking.

5. Reserve IP in DHCP or set static IP.

6. Update firmware and reset network if needed.

7. Use advanced packet capture or contact IT/HP if unresolved.

10 Frequently Asked Questions (FAQs)

1. My HP printer is powered on and connected to Wi-Fi but not showing up — what’s the first thing I should check?
Print the printer’s Network Configuration Page from its control panel. That page shows the exact SSID, IP address, and network status. If the SSID is wrong or the IP is 0.0.0.0, reconfigure Wi-Fi; if IP exists, try pinging it.

2. The printer has an IP address but my computer can’t find it — why?
Possible causes: client and printer are on different subnets/VLANs, firewall blocking discovery, or mDNS/Bonjour blocked by the router. Try pinging the IP, disabling firewall temporarily, and adding the printer manually by IP (IPP/JetDirect).

3. Why does the printer show up on my laptop but not on my phone?
Mobile devices rely on mDNS/Bonjour (iOS) or Mopria (Android) for discovery. If your router implements client isolation for Wi-Fi or blocks multicast, phones won’t see the printer. Ensure both phone and printer are on the same SSID and that AP/client isolation is off.

4. After a power outage my HP printer stopped appearing — what should I do?
Power cycle the router and printer. The printer may have lost its DHCP lease or the router’s DHCP server might be assigning a new IP. Reserve the printer’s IP in the router or set a static IP on the printer.

5. My office uses VLANs — how do I make the printer discoverable to other VLANs?
VLANs isolate broadcast and multicast traffic. Use a Bonjour/mDNS gateway or configure service discovery proxying on your network equipment. Alternatively, set up a print server accessible from each VLAN.

6. How do I add the printer manually if discovery fails?
Find the printer IP from its network report or router DHCP list. On Windows/Mac/Linux/Chromebook, add a printer by IP using IPP (ipp://printer-ip/ipp/print) or AppSocket (socket://printer-ip) or LPD as needed.

7. Could my router be blocking the printer?
Yes. Features like Guest Network, AP Isolation, or some security firmware can prevent device-to-device discovery. Temporarily disable those features or move printer and client to the same trusted SSID.

8. Why does the printer appear sporadically and then disappear?
Intermittent network issues (weak Wi-Fi signal, failing switch port, DHCP conflicts), aggressive power-saving on the printer, or firmware bugs can cause flakey visibility. Use wired Ethernet for reliability and update firmware.

9. What ports/protocols need to be allowed for discovery and printing?
Common ones: UDP 5353 (mDNS/Bonjour), TCP/UDP 9100 (JetDirect), TCP 631 (IPP), TCP 515 (LPD). For Windows sharing, SMB ports may be needed. Allow these between clients and the printer as needed.

10. I can reach the printer’s EWS page via IP but AirPrint/Mopria discovery still fails — what now?
If EWS is reachable, the printer’s core network is fine; the issue is discovery (mDNS) being blocked or filtered. Enable multicast/mDNS on the network, or configure a Bonjour gateway if users and printers are on different subnets.