Agent Installation - Knowledge Base

No Network Provider accepted the given Network Path

Problem

Desktop Central Agent installation, Patch Scanning fails with the error message - "No Network Provider accepted the given Network Path"

Cause

This error will be shown due to one or more of the following reasons:

1. When you do not have access to admin$ of the client computer.
2. You are unable to ping the client computer by FQDN.
3. When File and Print Sharing For Microsoft Networks is not enabled.
4. If File and Printer Sharing is disabled in the Windows Firewall of the client computers.
5. If Security Policy is not configured.
6. If the "Workstation Service" is not running in the Client Computers.
7. If the "TCP/IP NetBIOS Helper" service is not running in the Client Computers.

Resolution

You can resolve this issue as follows:

1. Check your access to admin$ of the client computer

From the computer where Desktop Central Server is installed, select Start --> Run and type \\<client Computer Name>\admin$. If you get the same error, enable Remote Administration Exception in the client computers as below:

1. From the client computer, select Start --> Run and type gpedit.msc and hit enter
2. Expand the Administrative Templates -> Network -> Network Connections -> Windows Firewall
3. Click the Domain Profile and double click the Windows Firewall : Allow remote administration exception
4. Select Enabled and click OK.


2. Ping the client computer by FQDN

Ensure that you are able to ping the client computers from the computer where Desktop Central Server is installed using the Fully Qualified Domain Name (eg. hostname.domainname.com)



3. Enable File and Print Sharing For Microsoft Networks

Enable File and Print Sharing For Microsoft Networks in the client computers as 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.


4. Enable File and Printer Sharing in the Windows Firewall of the client computers

Enable File and Printer Sharing the in client computers as below:

1. Open the Windows Firewall and select the Exceptions tab
2. Select the File and Printer Sharing check box and click OK.

If you still get the same error, verify that you are configuring File and Printer Sharing in the same profile that the Desktop Central Server computer is using. If you enable File and Printer Sharing in the domain profile, but the Desktop Central Server computer is using the standard profile, then File and Printer Sharing might not be enabled. You can use the Netsh tool to determine which profile the Desktop Central Server computer is currently using and which profile has File and Printer Sharing enabled. To enable File and Printer Sharing for all profiles, use the following command:

From the command prompt, type netsh firewall set service type = FILEANDPRINT mode = ENABLE scope = ALL profile = ALL and press enter.



5. Configure Security Policy
1. Select Start --> Settings --> Control Panel --> Administrative Tools --> Local Security Policies
2. In Security Options  -> local policies -> Security Options -> Change the Network security: LAN Manager authentication level: Send LM & NTLM responses


6. Make "Workstation Service" run in the Client Computers
1. Select Start --> Settings --> Control Panel --> Administrative Tools --> Services.msc
2. Right-click Workstation service and then click start


7. Make "TCP/IP NetBIOS Helper" service run in the Client Computers
1. Select Start --> Settings --> Control Panel --> Administrative Tools --> Services.msc
2. Right-clickTCP/IP NetBIOS Helper service and then click start

More Information

If you still could not get it resolved, you can try installing the agents manually using the script or using Windows GPO. Click here for more details.

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

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

	Did this resolve your issue?  Seek assistance from our Experts.

Agent Installation - Knowledge Base