Error 0x00000035: The network path was not found
Error 0x00000035 means Windows can't reach the computer or path you typed for a shared printer. Check the name, sharing settings and try the IP.
What this error means
0x00000035 is Windows error 53, "The network path was not found". Your PC couldn't find the computer named in the printer path, or reached it but couldn't open the share. It usually comes down to a typo in the name, network discovery or sharing being turned off, a firewall blocking file and printer sharing, or your PC being unable to turn the computer's name into a network address.
Common causes
- A typo in the computer name or share name
- Network discovery or file and printer sharing is off, or the network is set to Public
- Your PC can't resolve the host's name to an IP address
- A firewall blocking file and printer sharing on the host
- The two PCs are on different networks, such as guest Wi-Fi or a VPN
How to fix it
Start with the first fix. They’re ordered from safest and quickest to most involved.
Fixes for Windows
0 of 7 steps tried
-
Check the computer and share names
A shared printer path looks like
\\COMPUTERNAME\ShareName. On the host, find the exact computer name in Settings > System > About (shown as Device name). Find the share name in Printers & scanners > your printer > Printer properties > Sharing. Re-type the path carefully on your PC; a single wrong character produces this error. -
Turn on network discovery and file and printer sharing
On both PCs, open Settings > Network & internet > Advanced network settings > Advanced sharing settings and turn on Network discovery and File and printer sharing for private networks. Then open your Wi-Fi or Ethernet connection's properties and set the network profile to Private. On Windows 10, use Control Panel > Network and Sharing Center > Change advanced sharing settings.
-
Connect using the IP address
On the host, open Command Prompt, run the command below and note the IPv4 Address. On your PC, press Win + R, type two backslashes followed by that address (for example
\\192.168.1.20) and press Enter, then right-click the printer and choose Connect. If this works when the name didn't, name resolution is the problem; keep using the IP path and reserve that address for the host in your router so it doesn't change.ipconfig -
Test whether the host answers
On your PC, run
ping HOSTPCand thenpingfollowed by the host's IP address. Replies to the IP but not the name confirm a name problem. No reply to either means the PCs can't reach each other at all, though a timeout can also mean Windows Firewall is blocking ping because file and printer sharing isn't allowed on the host. -
Allow file and printer sharing through the firewall
On the host, open Windows Security > Firewall & network protection > Allow an app through firewall. Click Change settings and tick File and Printer Sharing in the Private column. If third-party security software manages the firewall, allow file and printer sharing on your home network in its settings instead.
-
Check the sharing services on the host
On the host, press Win + R, type
services.mscand press Enter. Make sure Server is running with startup type Automatic; without it the PC can't share anything. Function Discovery Resource Publication helps the PC appear in other computers' Network folder, so set it to Automatic if the host doesn't show up there. On your PC, the Workstation service should be running. -
Put both devices on the same network, or connect directly
Guest Wi-Fi networks, some mesh systems and VPNs keep devices apart, so check both PCs are on the same main network with any VPN disconnected. If the printer has its own network connection, adding it on each PC by IP address avoids PC-to-PC paths entirely.
Did this fix it?
Good. To confirm everything is healthy, print a test page. It takes a minute and shows any quality problems early.
Still stuck? Our printer assistant can walk you through it by live chat, free. . Or the The troubleshooter asks a few questions and narrows it down. If your printer is under warranty, the manufacturer can repair or replace it at no cost. Find their official support site on our brand pages.
Common questions
The host appears in Network but I still get 0x00000035. Why?
Discovery works, but the share itself can't be opened. Check the share name, that the Server service is running on the host and that the firewall allows file and printer sharing.
Is 0x00000035 a printer fault?
No. It means Windows couldn't find the network path to the computer sharing the printer. The printer itself isn't involved yet at that stage.