Home > Backup Exec > Backup Exec 2010 R2 Error Connecting To The Remote Computer

Backup Exec 2010 R2 Error Connecting To The Remote Computer

Contents

Sorry, we couldn't post your feedback right now, please try again later. Join our community for more solutions or to ask questions. Your comments indicate that you have local adminpermissions on the media server, but not on some other servers. To be honest, I haven't had an issue updating my agents (on the servers I have migrated to R3 so far), but have seen the option to trust them (I haven't...haven't Source

Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? From the dcomcnfg Console Root select Component Services | Computers | My Computer | DCOM ConfigLocate the DCOM Object that matches the Value Data from the 'AppID' Registry Value Data noted No Yes Did this article save you the trouble of contacting technical support? No Yes How can we make this article more helpful?

Ensure That The Computer Is Available Has Wmi Enabled And Is Not Blocked By A Firewall 67

From the error, it looks like the account specified, does not have the necessary permissions to do so. The Backup Exec Install requires admin level privledges on the remote systems in order to successfully install or update agents. Promoted by Recorded Future Enhance your security with threat intelligence from the web.

  • 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.
  • Create/Manage Case QUESTIONS?
  • Get 1:1 Help Now Advertise Here Enjoyed your answer?
  • 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
  • I'll try to setup a test like you mention above and see what is happening.

Live Traffic Feed Feedjit Live Blog Stats Blog Archive ► 2016 (35) ► September (1) ► August (4) ► July (10) ► June (4) ► April (1) ► March (4) ► Even specifying the domain admin credentials through the wizard for the RAWS installation account I was receiving the remote registry error. Join Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Veritas.com Support Welcome to VOX An Thank you for your feedback!

Join Now For immediate help use Live now! How To Install Backup Exec Remote Agent Manually F. 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 Storage Software SBS Windows Server 2003 Windows Server 2008 Data Deduplication for VM Backups Article by: Anna VM backup deduplication is a method of reducing the amount of storage space needed

Showing results for  Search instead for  Do you mean  VOX Featured on VOX Viva Veritas! RAWS does not need a service account, as it runs as local system. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? To push the agents successfully i had to log into the media server as a domain admin, launch the BE console and push the remote agents.

How To Install Backup Exec Remote Agent Manually

Covered by US Patent. Great care should be taken when making changes to a Windows registry. Ensure That The Computer Is Available Has Wmi Enabled And Is Not Blocked By A Firewall 67 Right Click on the DCOM Object that matches and select 'Properties' and select the 'Security' tabFig 5 7. Backup Exec Cannot Connect To The Remote Computer Ensure That The Remote Computer Is Available 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

A Windows Security Alert pop-up will appear, click Unblock. 5. this contact form Lewan Technology is a business technology and managed service provider serving Colorado, Wyoming, New Mexico and beyond. http://www.symantec.com/business/support/index?page=content&id=TECH180429 will it work? It's related to the RAWS32 http://www.symantec.com/connect/forums/be-2014-remote-agent-install-failing 0 Message Accepted Solution by:Seshadrim2014-12-24 The issue is now fixed. 0xe00086ce

To select the remote computer from a Microsoft Windows Network domain, expandMicrosoft Windows Network, and then expand the domain where the remote computer resides. 5.Do one of the following:To establish the PCSTATS Loading... I Also tried uninstalling the previous version of the Agent from the Server and tried a Manual install by transferring the "RAWS32" folder from the media Server, But it Still fails http://gatoisland.com/backup-exec/backup-exec-2010-r3-error-connecting-to-the-remote-computer.php During this check i believe it is using the logged in user account and not the specified one.

However, the install requires an admin level account to do the necessary changes to the remote system to run the install, etc. Join the community of 500,000 technology professionals and ask your questions. 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

Article:000081930 Publish: Article URL:http://www.veritas.com/docs/000081930 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

Solution The trust relationship between the media server and a remote computer can be established manually in a number of ways: A. 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. Learn about the Veritas Technology Partner Program. 267 Posts 31 Solutions Trusted Advisors mikebounds Partner Trusted Advisor Accredited 51 Kudos 2297 Posts 672 Solutions Marianne Partner Trusted Advisor Accredited Certified 348 Agent has been installed very good on the other server.

Comment Submit Your Comment By clicking you are agreeing to Experts Exchange's Terms of Use. 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 Create/Manage Case QUESTIONS? Check This Out The trust relationship between the remote computer and the media server is automatically established during installation. (See related articles for How to push install Backup Exec RAWS)2.

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 No Yes Did this article save you the trouble of contacting technical support? No Yes Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Veritas.com Support Communities Push-install the remote agent to one or more remote computers from the media server.

© Copyright 2017 gatoisland.com. All rights reserved.