Error Connecting To The Remote Computer Backup Exec 24
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process how to install backup exec remote agent manually ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor backup exec cannot connect to the remote computer Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA 0xe00086ce Site: Veritas Veritas PartnerNet 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" Article:000015581 Publish: Article URL:http://www.veritas.com/docs/000015581 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem 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 Message Error connecting to the remote computer. Ensure that the computer is available, has WMI enabled, and is not blocked by a firewall. Solution Solution 1: 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. Solution 2: NDMP using different ports on media server and remote server
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Push install of the Backup Exec 2010 Remote Agent and/or Desktop Laptop Agent (DLO) to a remote Windows server fails https://www.veritas.com/support/en_US/article.TECH177317 with "Error connecting to the remote server. Ensure the server is available, has WMI enabled, and is not blocked by a firewall. 1603" Article:000006395 Publish: Article URL:http://www.veritas.com/docs/000006395 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout https://www.veritas.com/support/en_US/article.TECH128062 Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Backup Exec (BE) 2010 push install of the Backup Exec Remote Agent and/or Desktop Laptop Agent (DLO) to a Remote Windows Server fails with error: "Error connecting to the remote server. Ensure the server is available, has WMI enabled, and is not blocked by a firewall. 1603." Error Message Error connecting to the remote server. Ensure the server is available, has WMI enabled, and is not blocked by a firewall. 1603 Windows System Event log on the remote Windows Workstation or Server shows below:Fig 1 Remote Agent push log
October (10) September (7) August (10) July (1) June (2) May (2) April (3) March (3) February (3) January (4) December (3) http://dbastas.blogspot.com/2012/03/symantec-backup-exec-remote-agent.html November (4) October (4) September (19) August (3) July (14) June (8) May (5) April (6) March (13) February (18) January (7) December (3) November (15) October (9) September (1) August (6) July (21) June (21) May (82) Labels ADSL (1) Antispam (2) Antivirus (1) asterisk (1) Avaya (2) Boot Disks (2) Cisco (13) Core (7) Dell (1) Excel (1) Exchange Server backup exec (34) Firefox (1) Hyper-V (19) Hyper-V R2 (22) IIS (1) IPv6 (1) ISA Server (3) Linux (22) Microsoft Office (3) mysql (1) Networking (20) ntfrs (2) OpenVPN (1) Oracle (3) Outlook (6) PFSense (2) Powershell (7) Procurve (5) Remote Control (1) Routers (2) SharePoint Server (1) SmoothWall (1) SQL Server (6) squid (1) Symantec BackupExec (1) Synology (1) Teamviewer (1) Terminal Services to the remote (1) Thecus (1) TMG 2010 (1) UPS (1) VBA (1) VMware (92) VMware View (3) VMware Workstation (1) WDS (1) wget (1) Windows 2000 (6) Windows 7 (41) Windows 8 (3) Windows Live Mesh (1) Windows Server 2003 (50) Windows Server 2008 (49) Windows Server 2008 R2 (49) Windows Server 2012 (5) Windows Vista (32) Windows XP (17) Zyxel (2) Followers About Me Dimitris Bastas A boy and his dog View my complete profile Visitors Sunday, March 18, 2012 Symantec Backup Exec remote agent installation error When you try to install Symantec Backup Exec Agent to a remote computer you receive the following error: "Error connecting to the remote server. Ensure that the server is available, has WMI enabled, and is not blocked by a firewall.24" To fix this problem try the following on the remote computer: Run Group Policy Editor or the local group policy editor (gpedit.msc) and from the Local Computer Policy/Computer Configuration/Windows Settings/Security Settings/Local Policies/User Rights Assignments allow Administrators, Local Service, and Network Service accounts to "Adjust Memory Quotas for Process Properties" and Local Service, and Network Service to "Replace a pr