- Verify that RPC Remote procedure call service is running on NetCrunch server
- Verify that "Workstation" service is started on NetCrunch server
- Verify that "Client for Microsoft Services" are installed and enabled on the active network card on the NetCrunch server
- Verify that "Server" service is started on the target host. If not, you need to start it.
- Verify that "File and print services" are installed and enabled on the active network card on the target host
- Make sure that TCP 139, 445 and UDP 137, 138 ports are not blocked on local or enterprise firewall
- You may consult Microsoft Documentation
This article is kept for reference and is no longer maintained. It describes a version of NetCrunch that is out of support, and the product has changed since.
Connection error (35) or Connection Error (Invalid network path) or WinPerfMon - The remote procedure call failed (#06BE)
When trying to connect to a Windows node I get the error "Invalid network path" in the last error column.
