Home > Backup Exec > Backup Exec Error Connecting To The Remote Computer Ensure

Backup Exec Error Connecting To The Remote Computer Ensure

Contents

Thank you very much! Open your command prompt on the workstation. Join the community of 500,000 technology professionals and ask your questions. Ensure that BE is not installed on the target remote server.  Solution A trust relationship between the media server and the remote computer can be established in the following ways:1. Source

Under 'Launch and Activation Permissions' select the 'Customize' radio button and click EditFig 6 8. Solution 2: NDMP using different ports on media server and remote server NDMP by default runs on port 10000.If the media server is running on port 10000 and if the remote Join Now For immediate help use Live now! Learn More [fa icon="long-arrow-right"] More Links [fa icon="caret-right"] Home [fa icon="caret-right"] Blog [fa icon="caret-right"] Contact Us [fa icon="caret-right"] Job Opportunities Contact Us [fa icon="phone"] 303.759.5440 [fa icon="envelope"][email protected] [fa icon="home"] Our HQ:

Backup Exec Error Connecting To The Remote Computer Ensure That The Computer Is Available

if i install thebe5204R180429_x64bit.exe 0 Kudos Reply ...if that patch hasn't been CraigV Moderator Partner Trusted Advisor Accredited ‎04-30-2013 01:30 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed VOX : Backup and Recovery : Backup Exec : Error connecting to the remote computer. Exchange Office 365 Storage Software Software-Other Exclaimer Changing the Backup Exec Service Account and Password Video by: Rodney This tutorial will walk an individual through locating and launching the BEUtility application Ensure that the computer is available, has WMI enabled, and is not blocked by a firewall.24 http://www.symantec.com/docs/TECH177320 How to enable firewall rules on windows server 2008 R2 to enable PUSH install

Subscribe to our monthly newsletter for tech news and trends Membership How it Works Gigs Live Careers Plans and Pricing For Business Become an Expert Resource Center About Us Who We Connect with top rated Experts 9 Experts available now in Live! All rights reserved. How To Install Backup Exec Remote Agent Manually I have the DNS suffixes of each domain as search domains, but I also added the names into the hosts file on each machine as you suggested and I still get

And it didn't solve the problem. "Microsoft Exchange 2010 database backup fails with v-79-57344-913 database was not found" 0 Kudos Reply « Previous 1 2 Next » Contact Privacy Policy Terms Install the Remote Agent for Linux or UNIX Servers on a Linux or UNIX computer respectively and then add the computer to User-defined Selections.   Please refer to the Related Document Backup Exec 2010 R2 - Remote Agent Install Error Code 1603 [fa icon="long-arrow-left"] Back to all posts [fa icon="pencil'] Posted by Lewan Solutions [fa icon="calendar"] September 28, 2010 Tweet While onsite Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Push install of the Backup Exec Remote Agent to a Remote Windows

No Yes Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES 0xe00086ce Create/Manage Case QUESTIONS? 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. Otherwise, register and sign in.

Backup Exec Cannot Connect To Remote Computer

Thank You! A trust relationship for a remote Linux or UNIX computer must be established prior to a backup.  Note: This error also occurs if the Backup Exec Server is trying to backup another media Backup Exec Error Connecting To The Remote Computer Ensure That The Computer Is Available Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : Error connecting to the remote computer. The Backup Exec Server Could Not Connect 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.

If problem persist, install Remote Agent for Windows Servers (RAWS) using manual method following instructions listed here.   Terms of use for this information are found in Legal Notices.

Related Articles http://sovidi.com/backup-exec/backup-exec-error-connecting-to-the-remote-computer-14.php Not sure if this is related, but when I click 'Browse Remote Computers' in BE, only my local domain appears - not the remote one? You may also refer to the English Version of this knowledge base article for up-to-date information. But now: Microsoft DenisFrolov Level 3 ‎04-30-2013 01:28 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content ok. Ensure That The Computer Is Available Has Wmi Enabled And Is Not Blocked By A Firewall 67

Request a Free Review How To: Azure Resource Manager VM Level Backup & Restore Without Snapshots NetScaler Website Redirection - The Nice & Elegant Way Paper Weight & Printing - how No Yes Home | Site Map | Cisco How To | Net How To | Wireless |Search| Forums | Services | Donations | Careers | About Us | Contact Us| Why? have a peek here Solved Installing symantec agent to vmware host Posted on 2013-01-23 Storage Software 1 Verified Solution 6 Comments 982 Views Last Modified: 2013-02-12 Hi, Got an old server that currently backs up

Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES Services Overview Does this make a difference? It is possible that updates have been made to the original version after this document was translated and published.

Email Address (Optional) Your feedback has been submitted successfully!

It has worked on every workstation I have tried it on so far. 1 Kudo Share Back to Blog Newer Article Older Article 2 Comments Partner Accredited paja N/A ‎11-19-2013 10:42 I've been asked to change this so that we push the agent out to it from another newer symantec install (backup exec 2010 r3) on an sbs2008 box. Ensure that the computer is available, has WMI enabled, and is not blocked by a firewall. 24   Cause WMI Remote execution requires the following:   "Adjust Memory Quotas for Process The solution there is to install locally so in your case I guess you would have to install it locally http://www.symantec.com/docs/TECH198173 Thanks 0 Kudos Reply OK, so I assume you

Thanks. 0 Kudos You must be a registered user to add a comment. Our domain controller is SBS 2003 running exchange, it also runs the backup exec. 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 Check This Out Terms of use for this information are found in Legal Notices.

Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may

It is possible that updates have been made to the original version after this document was translated and published. As a Xerox company, you can depend on our 40 years of providing local solutions, service and support, backed by the trusted Xerox name. In system log is nothing. It was not listed under my firewall settings however (due to group policy).

Go to Solution 6 Comments LVL 23 Overall: Level 23 Storage Software 20 Message Active 3 days ago Expert Comment by:Iamthecreator2013-01-23 Is there a number at the end of the Sorry, we couldn't post your feedback right now, please try again later. Network access to server is have.