Multiple customers of mine have had issues with the error message “Network path is not found”. Windows can throw this error message for a number of reasons. This often becomes a problem when you’re trying to remotely monitor event logs, services, disk space, etc. using network monitoring software such as Overseer Network Monitor.

If you’re having this issue, try these things:

Make sure both Windows PCs(your computer and the remote computer) are running on the same network/LAN.

Disable the Windows firewall. If this works, you know it’s the firewall blocking traffic, and you can find what rule to add to the firewall to make things work.

Disable UAC!. Note that you may have to disable remote UAC in addition to the GUI disabling of user account control

Check the clocks on both computers. If the times are not within 15 minutes of each other, this problem may occur. Be sure to check the date and the time, as it’s easy to miss a different year when looking at just the time or day.

Check the status of these services and make sure they’re running on both ends:

Remote Registry Service

Server

Workstation

Computer Browser

Remote Procedure Call

TCP/IP NetBIOS Helper Service

Check your network card(s) properties, and check these options:

Client for Microsoft Networks

File and Printer Sharing for Microsoft Networks

Also make sure “Enable NetBIOS over TCP/IP” is enabled

Make sure “802.1x” authentication is disabled(potentially buried under ‘configure’ tab for network adapter

If using local accounts, be sure you’re referring to them as MACHINE\username, and **not** .\username. If you use .\username, you will get “network path was not found”, which is a very unhelpful in resolving this problem.