Backup Exec 2010 Error Connecting To The Remote Computer
Contents |
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 backup exec 2010 r2 ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations backup exec error connecting to the remote computer ensure that the computer is available Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site:
Backup Exec Cannot Connect To Remote Computer
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
The Backup Exec Server Could Not Connect To The Remote Computer
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 backup exec error connecting to the remote registry 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 NDMP by default runs
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016
Backup Exec 2010 Remote Agent
Sign In CommunityCategoryBoardResourcesUsers backup exec 2010 remote agent utility turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as backup exec 2010 remote agent not detected you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : Backup Exec : Error connecting to the remote computer. Make sure... VOX https://www.veritas.com/support/en_US/article.TECH177317 : Backup and Recovery : Backup Exec : Error connecting to the remote computer. Make sure... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Error connecting to the remote computer. Make sure that the computer is available, WMI is enabled and not blocked https://vox.veritas.com/t5/Backup-Exec/Error-connecting-to-the-remote-computer-Make-sure-that-the/td-p/626777 Windows Firewall.14 DenisFrolov Level 3 04-29-2013 06:57 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hello, I can not install the Remote Agent Backup Exec 2010 R3 on Win Server 2008 R2 to backup Exchange 2010. Domain account with full administrator rights. The error is: Error connecting to the remote computer. Make sure that the computer is available, WMI is enabled and not blocked Windows Firewall.14 Firewall is turned off, antivirus is empty, the WMI service is enabled. Network access to server is have. I tried instal with local administrator account and gave all sorts of rights, but to no avail. Agent has been installed very good on the other server. Labels: 10.x and Earlier Agent for Microsoft Exchange Server Agents Backup and Recovery Backup Exec Troubleshooting Windows Server (2003-2008) 1 Kudo Reply 10 Replies Hi, Check out the TN CraigV Moderator Partner Trusted Advisor Accredited 04-29-2013 07:06 AM Options Mark as New Bookmark Subscr
October (10) September (7) August (10) July (1) June (2) May (2) April (3) March (3) February (3) January (4) December (3) 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 (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 (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 process level token". Remote user must also be a member of Local Administrators group and Remote Registry service must be running. Reboot the remote server to apply changes. Try to install Backup Exec agent again after rebooting the remote server. Posted by Dimitris Bastas at 10:23 AM Labels: Symantec BackupExec No comments: Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom)