Why your printer, NAS, or camera is not reachable

This page is for the moment when the network mostly works, but one device path does not. The goal is to separate addressing, gateway, VLAN, discovery, and target-device trouble before the network gets flattened or the wrong device gets blamed.

Pillar: Home & Office Networking Type: Guide / troubleshooting hybrid Single-device path diagnosis

Reachability is not the same as internet access

A printer or NAS can fail on the local path even while web browsing still works normally.

Addressing comes before discovery

Client IP, target IP, subnet, and gateway usually matter before app-level discovery or convenience features.

One device path can be broken while the rest of the network feels fine

That is why it helps to keep the problem narrow instead of treating the whole Wi-Fi network as guilty.

Keep the path readable

  • Record the client and target IP, subnet, and gateway before you change anything.
  • Notice whether the device is on wired Ethernet, Wi-Fi, a different SSID, or a different network segment.
  • Check whether the problem affects every client or only one app, one computer, or one room.
  • Review recent reservation, static-IP, VLAN, or SSID changes if the device used to work.

Open the next page that matches the network shape

Start with the IoT-network guide if segmentation changed recently. Start with modem and router basics if device roles are still fuzzy.

Use the closest live repair branch

Keep the network path calm