Backup Exec 2012 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 error connecting to the remote computer ensure that the computer is available ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations
Backup Exec Cannot Connect To Remote Computer
Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site:
The Backup Exec Server Could Not Connect To The 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
Backup Exec Error Connecting To The Remote Registry
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 ensure that the computer is available has wmi enabled and is not blocked by a firewall 67 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 NDMP by def
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 Sign In how to install backup exec remote agent manually CommunityCategoryBlogResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your 0xe00086ce search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Blogs : Backup & Recovery Community Blog : Fix for Error 1603 When trying to push install age... Subscribe to RSS Feed Mark as New Mark as Read Bookmark Subscribe Email to a https://www.veritas.com/support/en_US/article.TECH177317 Friend Printer Friendly Page Report Inappropriate Content Fix for Error 1603 When trying to push install agent for windows in Backup Exec 2012 Jeff Hoins (Joins05) Joins05 N/A 07-18-2012 04:31 PM Subscribe to RSS Feed Mark as New Mark as Read Bookmark Subscribe Email to a Friend Printer Friendly Page Report Inappropriate Content 07-18-2012 04:31 PM After upgrading to BE 2012,I wanted to set up backups https://vox.veritas.com/t5/Backup-Recovery-Community-Blog/Fix-for-Error-1603-When-trying-to-push-install-agent-for-windows/ba-p/780507 for all of our workstations. I had previously only backed up our servers and workstations needed for our daily production at our sign shop. The decision to backup all workstations was due to a new need for better safetyguards for our workstations going down due to me moving too far away to be onsite on a daily basis for any hardware/software failure. Our domain controller is SBS 2003 running exchange, it also runs the backup exec. We also have Server 2008 acting as a fileserver. The servers that already had remote agent on them from BE 2010 had no problem ungrading. However, when I tried to push install Agent for Windows to our other workstations (XP or 7), I recieved the status "Error connecting to the remote computer. Ensure that the computer is available, has WMI enabled, and is not blocked by a firewall. 1603". I checked the workstations and their firewall settings all had WMI and File and Printer Sharing on. After working with the problem for some time I found that remote administration needed to be let through the firewall as well. It was not listed under my firewall settings however (due to group policy). Rather