Submit a ticketCall us

AnnouncementsSystem Monitoring for Dummies

Tired of monitoring failures disrupting the system, application, and service? Learn the key monitoring concepts needed to help you create sophisticated monitoring and alerting strategies that can help you save time and money. Read the eBook.

Get your free eBook.

Home > Success Center > Server & Application Monitor (SAM) > SAM - Knowledgebase Articles > Access Denied or network path was not found errors when deploying an agent

Access Denied or network path was not found errors when deploying an agent

Updated: 3-29-2017


The following errors appear when attempting to deploy remote agents to nodes for monitoring:

  • Access Denied
  • The network path was not found

The errors can occur for Orion agent for Windows and Orion agent for Linux. You need to verify and test your credentials and take additional steps to complete the deployment. The issue can occur due to credentials or configurations on remote nodes blocking Windows access.


  • Orion Platform 2014.1.1 and later
  • Orion agent for Windows
  • Orion agent for Linux


This can occur because of the following:

  • Credentials from the primary SolarWinds server are not accepted on a remote node.
  • When User Account Control (UAC) is enabled on remote nodes using Windows Vista and newer operating systems, specific settings on the remote node may prevent access to local administrators and, sometimes, even built-in administrator accounts. This access is required to deploy remote Orion agents for Windows.


Review the following options for resolving credentials for Orion agent for Windows and Linux.

General troubleshooting

Verify the following:

  • In case of push deployment, the firewall must not block in the direction from the Orion server to the agent. Networks may commonly block the direction from the agent to the Orion server, for example from DMZ.
  • Provided credentials are correct.

Windows troubleshooting

Verify the following for agents installed on Windows-based computers:

  • File-sharing between the primary server and the remote node(s) is not blocked.
  • The server service is started on the remote host.
  • User Account Control (UAC) is disabled on the remote node.
  • The account used for remote deployment must have access to the administrative share on the target computer: \\<hostname_or_ip>\admin$\temp.
Note: You may need to restart the “Server” service on the remote host.


Linux troubleshooting

Agents installed on Linux-based computers may use two (one set to connect via SSH and one set to install the software) different credential sets to install and configure the agent. During this process, a service account is also created to run the agent service.

You need the following privileges to install and configure the agent:

  • SSH connectivity

  • SFTP or SCP (for the push method)

  • HTTPS connection from the linux box to the Orion poller (for the pull method of install)

  • root or SUDO level access to the server

Credentials are used to install and configure the agent and are not used at any other time.  During the process of install, the Linux agent will create a least privileged account to use for the everyday operation (the swiagent user and group).

For more information, see the Credentials and privileges used on Linux-based computers.

UAC on remote nodes

Disable UAC remote restrictions by editing the LocalAccountTokenFilterPolicy entry in the registry of your remote node, as indicated in the Microsoft Support article, Description of User Account Control and remote restrictions in Windows Vista.


Last modified