A push install of the remote agent fails with: "Error connecting to the remote computer. Ensure that the computer is available, has WMI enabled and is not blocked by a firewall"
Push install of the Backup Exec Remote Agent to a Remote Windows Server fails with error: "Error connecting to the remote computer. Ensure that the computer is available, has WMI enabled and is not blocked by a firewall"
Error connecting to the remote computer. Ensure that the computer is available, has WMI enabled, and is not blocked by a firewall.
Please refer "C:\ProgramData\Veritas\Backup Exec\Logs\RAWSINSTXX.HTM" on the remote server and
"C:\ProgramData\Veritas\Backup Exec\PushLogs\Remoteserver_name_Push.log" in the Backup Exec server for more detailed error codes or messages.
Related UMI v-79-57344-34510
Solution 1: NDMP using different ports on media server and remote server (Applicable when remote agent is already installed on remote server and push update fails)
NDMP (Network Data Management Protocol) is the protocol used by Backup Exec Remote Agent.
- NDMP by default runs on port 10000.
- If the media server is running on port 10000 and if the remote server has NDMP running on any port other than 10000, then this can also cause the failure.
- To check which port NDMP is using, follow the article: How to change the default port used by the Backup Exec Remote Agent for Windows Servers (RAWS).
- If there is no entry in the services file (located at C:\Windows\System32\Drivers\etc) for NDMP, means its using the default port 10000.
- If the ports are different on both, the media server and remote server, then make them use the same port and then try the push installation again.
Note: Avoid changing NDMP port on media server, if media server have many other working Remote Agents on port 10000 then all will drop the connection immediately after the NDMP port on media server changed.
Solution 2: Remote Registry Service
On the remote server, check the Windows Services and verify the Remote Registry Service is running.
If detailed error codes or messages are seen in the install logs mentioned above, please use those to search here for accurate solution.
Workaround : Manually install the remote agent
- Copy the RAWS32/RAWS64 (from X:\Program Files\Symantec\Backup Exec\Agents) and the MSXML folders on the particular remote server where you want to install Remote Agent.
- On the remote server, run setup.exe from the RAWS32/RAWS64 folder and complete the install.
- Make sure to enable "Publishing" on the remote agent. For that launch Remote Agent Utility from Programs list or double click on the Remote Agent icon in the system tray.
Related Knowledge Base Articles
Was this content helpful?
Rating submitted. Please provide additional feedback (optional):