Network Path Not Found

Problem

Desktop Central Agent installation, Patch Scan , Asset Scan and Remote Control fail with error message - "Network Path was not found."

Cause

This error will be shown if,

1. The Client computer is down or not accessible
2. "File and Printer Sharing for Microsoft Networks" is not enabled in the network adapter of the client computers.
3. Microsoft Firewall blocks the process.
4. Third-party Firewall blocks the process.
5. Administrative Share (Admin$) on the client computer might have been disabled.

Resolution

You can resolve this issue as follows:

1. Ensure the client computer is accessible

   Check the client computer is switched on and connected in the network properly to install agent and carry operations like Patch Scan/Remote Control/Asset Scan. Also, ensure that you have specified the computer name correctly. The following steps will help you confirm the client machine's accessibility:

   Goto Start > Run > Type computer name prefixed by "\\" and hit the Enter key

2. Enable "File and Printer Sharing for Microsoft Networks"

   Enable this in all the client computers as below to carry out remote operations like Agent Installation/ Patch Scan/ Inventory Scan/ Remote Control in the client machines.
   For computers using Operating System released before Windows 7, follow the steps mentioned below;

   1. Select Start --> Settings --> Network Connections.
   2. Right-click on Network Connection and select Properties.
   3. In the connection properties dialog, select the General tab.
   4. Select the "File and Printer Sharing for Microsoft Networks" and click OK.
   5. If you do not find this option, click Install button.
   6. In the network component type, select Service and click Add.
   7. Select File and Printer Sharing for Microsoft Networks and click OK.
   8. Click Close to exit the properties dialog

   For computers using Windows 7 as Operating System, follow the steps mentioned below;

   1. Select Start -->Control Panel.
   2. Choose Network and Internet
   3. Select Network and Sharing Center and choose Change Advanced Sharing Settings
   4. Under File and Printer Sharing enable Turn on File and Printer Sharing
   5. Save changes
3. Configure Windows Firewall:

   Firewall has to be configured for a problem-free agent-server communication. Enable the Microsoft Firewall settings in the Desktop Central application as follows and try doing the desired opeartion.

   Goto Admin tab > Agent Settings > General Settings > Select Enable Firewall Settings

   The settings will get applied during the subsequent refresh cycle. To apply the steps immediately, follow the steps mentioned below:

   1. Download the script enableFirewallSettings.txt.
   2. Rename it to enableFirewallSettings.vbs
   3. Run the script in all the client computers from the command prompt: CSCRIPT enableFirewallSettings.vbs

   Note: You will still have problems related to Windows firewall in case, the Group Policy is configured to not allow exceptions. To overcome this, you will need to modify the GPO accordingly to allow the Desktop Central Server to communicate the Desktop Central Agents via the 135 and 445 ports.

4. Configure third-party Firewall:

   Run the script as explained below in all the client machines to configure the Firewall to carry out remote operations like Agent Installation/ Patch Scan/ Inventory Scan in the client machines:

   1. Download the DesktopCentralAgent.msi by clicking the Download Agent link in the Scope of Management page of the Desktop Central client. Save the msi file in the network share, for example, \\MyServer\MyShare\DesktopCentralAgent.msi.
   2. Download the script WMIPortSetup.txt.
   3. Rename it to WMIPortSetup.vbs
   4. Run the script in all the client computers from the command prompt: CSCRIPT WMIPortSetup.vbs \\MyServer\MyShare\DesktopCentralAgent.msi

   Running the above script will open the following ports in the client computers and installs the Desktop Central Agent:

   • TCP port 5000
   • TCP port 5001
   • TCP port 5002

   To run the script in multiple computers, you can either use the PsExec utility or add this script as a startup script in the GPO of Active Directory.

5. Enable the Administrative Share (Admin$) on the Client Machine

   Desktop Central aplication copies the Agent binaries to the Admin$ of the client machine prior to triggering Agent Installation. Therefore it is essential to have the Admin$ enabled in the client machines for smooth Agent Installation. You will need to edit the registry to enable the default administrative share.

   For Servers:

   1. Click Start and select Run.
   2. Type regedit in the Run prompt and click OK.
   3. Navigate the following in the Registry Hive and edit the REG_DWORD Value as '1'
      Hive: HKEY_LOCAL_MACHINE Key: SYSTEM\CurrentControlSet\Services\LanManServer\Parameters Name: AutoShareServer Data Type: REG_DWORD Value: 1
      Note: 1. If you cannot find the value in the registry under the exact location (i.e. it does not exist) - No need to add new value. A reboot is necessary for this to take effect.

   For Windows Server 2008 R2: In case you have a Windows Server 2008 R2 based domain environment you can enable the Admin$ in your client machine using a Start-Up script. Please refer to this document for details.

   For Workstations:

   1. Click Start and select| Run.
   2. Type regedit in the Run prompt and click OK.
   3. Navigate the following in the Registry Hive and edit the REG_DWORD Value as '0'
      Hive: HKEY_LOCAL_MACHINE Key: SYSTEM\CurrentControlSet\Services\LanManServer\Parameters Name: AutoShareWks Data Type: REG_DWORD Value: 0
      Note: If you cannot find the value in the registry under the exact location (i.e. it does not exist) - No need to add new value. A reboot is necessary for this to take effect.

Applies to: Agent Installation Failure, Desktop Central Agent Installation, Patch Scan Failure, Asset Scan Failure

Keywords: Agent Installation, Desktop Central Agent Installation Failure, Patch Scan Fails, Asset Scan Fails, Installation Failure