If a USB-C Ethernet adapter is involved and your local printer suddenly stopped being reachable, the issue is usually discovery, the printer’s IP path, or a host setting such as VPN, firewall, or an IPv4/IPv6 mismatch. The safest first move is to check what stopped working by IP and by name before you change anything on the computer, adapter, printer, or switch.
What stopped working: discovery, printing, or scanning?
Start by sorting the failure into one of three cases: you can’t find the printer in the print dialog, you can find it but jobs fail, or printing works but scanning does not.
That split matters because each case points to a different layer. If the printer disappears from discovery but still works by IP, the network path is probably fine and the issue is name resolution or discovery. If neither name nor IP works, check the adapter, subnet, or printer path first. If printing works and scanning fails, the scanner path is often the issue, not the Ethernet link.
If the failure changes depending on whether you use the printer’s name, its IP address, or a specific app, write that down before you change settings. That clue is usually more useful than the first error message.
Before you start
Use the simplest checks first, and stop if they show a wider outage.
- Leave the computer’s current network settings unchanged for now.
- Keep the printer’s front panel, Ethernet cable, and the switch or router port nearby.
- If the printer can also connect by Wi-Fi, note whether it is on a guest network or another isolated segment.
- If you can, have one other device on the same network ready for a quick test.
If the printer shows a local error, a paper jam, or no network light at all, fix that side first. It is safer to stop here than to keep changing adapter settings on the laptop when the printer itself is down.
First checks that are safe to make right now
- Check the printer’s own status lights or screen. Make sure it is on, awake, and not reporting a paper jam, offline state, or network warning.
- Check the Ethernet link light on the printer port and on the switch or router port it uses. If there is no link light, the issue is usually cable, port, or power, not printer discovery on the computer.
- Reseat the Ethernet cable at both ends. If you have a known-good spare cable, swap it in.
- Test the printer from another device on the same network, if you have one. If another computer can print or open the printer, the printer and network path are probably alive, and the break is more likely on the machine with the USB-C Ethernet adapter.
- If the printer is on Wi-Fi, check whether it was moved to a guest network, isolated wireless segment, or a different VLAN. A printer can look online and still be unreachable from your computer if the network path blocks local traffic.
If the printer is clearly down for everyone, stop trying to fix the adapter first. That usually wastes time and can hide the real problem.
Check the printer by IP instead of by name
Find the printer’s IP address from the printer screen, its network report, or its web admin page if you already know how to reach it. The exact menu names vary by model.
Then compare it with your computer’s address. If your computer is on 192.168.1.x, a printer on 192.168.50.x is probably on a different subnet, which means the two devices may be connected but not on the same local path.
Test the printer directly by IP address instead of by its name. That separates discovery from connectivity. If the printer works by IP but not by name, the network path is probably fine and the break is in name resolution, discovery, or the print queue entry.
If the printer does not have a valid IP address, or its address is on a different subnet than the computer, fix the printer network path first. A cable can be fine and the printer can still be unreachable if it is on the wrong segment or using the wrong network.
If IP works, the problem is discovery or host settings
When the printer opens or prints by IP but not by name, the issue is usually discovery, a stale printer entry, or a host-side block.
On the computer, check these before you touch the printer again:
- A VPN that sends local traffic into the wrong tunnel.
- A firewall or security app that blocks local printer discovery.
- A network profile that treats the wired link as public instead of private.
- An IPv4/IPv6 mismatch, where the printer and the computer are not using the same protocol path.
If you are on Windows and the USB-C Ethernet adapter stopped being recognized after a restart or upgrade, reconnecting it can sometimes make Windows notice it again. One Microsoft Q&A user reported success by turning USB connection notifications off and back on, then unplugging and replugging the adapter while Windows was running; another user in the same thread said that did not help, so it is not a universal fix. Treat that as a reversible check, not as the main solution.
If the printer’s web interface or admin page is exposed only by name and not by IP, do not assume the adapter is the cause. Discovery can fail while the actual wired path still works.
How to tell whether the adapter is the real problem
A USB-C Ethernet adapter is less likely to be the root cause if the computer still gets a normal wired connection, can reach other local devices, and can print to the printer by IP. In that case, the adapter is probably passing traffic, and the break is elsewhere in the printer path or host setup.
The adapter becomes more suspect if the computer has no usable wired connection at all, if the adapter keeps disconnecting, or if the link light on the adapter never comes on while the cable and switch port are known good. If other devices on the same switch can still reach the printer, I would stop blaming the adapter first.
If the printer has its own network settings, check for isolation features on the router or switch. Guest Wi-Fi, client isolation, and VLAN separation can block local printer access even when the cable and adapter are fine. That is especially likely if the printer was recently moved to another network or the office network was reconfigured.
On some printers, especially older HP models, web-based setup or management was possible through USB during initial setup, but that is not typical across manufacturers. If you are trying to manage the printer’s web interface and you do not have an IP address yet, the model-specific setup path matters more than the adapter itself.
Verify the fix
Use a real print job from the same computer that had the problem. A successful ping or a visible device list is not enough.
- Print a small test page from the printer queue or system print dialog.
- Send the same kind of job from the app you actually use.
- If printing works but scanning still fails, test the scanner path separately.
If the test page prints but your app still cannot find the printer, the remaining issue is usually the queue entry, driver, or app-specific printer selection. If the printer still fails by IP, go back to the subnet, isolation, and host-side checks rather than changing discovery settings again.
Frequently Asked Questions
If I can ping the printer, why won’t it print?
Because ping only proves the printer answers network requests, not that the print queue, driver, or print protocol is working. A printer can reply to ping and still fail in the driver path, the queue, or a name-based discovery path.
Should I add the printer by IP address?
Yes, if the printer works by IP but not by name. That is the cleanest way to tell whether discovery is broken while the actual network path is still fine.
Why does the printer show on my Mac but not on Windows, or the other way around?
The same root cause can look different on each OS because Windows and macOS use different discovery methods and network defaults. One system may hide a Bonjour, WSD, firewall, or profile problem that the other surfaces differently.