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

Backup Exec 2010 R3 Error Connecting To The Remote Computer


But Exec is very DenisFrolov Level 3 ‎04-30-2013 05:48 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Instaled. Join the community of 500,000 technology professionals and ask your questions. Problem Backup Exec 2010 R3 job fails with the error: 0xe0009b86 - Backup Exec cannot connect to the remote agent because a trust relationship was not established between the remote agent When you are performing a push install, you are being prompted for credentials to the remote machine. Source

This is the perfect course to leap into this lucrative career, learning how to use ethical hacking to reveal ... No Yes Did this article save you the trouble of contacting technical support? Thank you for your feedback! However, 2 of them give the message "Error connecting to the remote registry".

Symantec Backup Exec 2010 R3 Remote Agent Download

E. This is my theory anyway. 0 Kudos Reply Thanks for your input... Agent has been installed very good on the other server.

The two offices are connected via a VPN tunnel with SonicWall NSA appliances on either end. Storage Software Storage Backup Exec 2014 – Overview and Differences from 2012 Video by: Rodney This tutorial will give a short introduction and overview of Backup Exec 2014 and the additional Interestingly,itispossibleto updatetheagentswhenI logintotheBackupExecmediaserverwith this accountthat islocaladminonallserversandrunningthe services. Backup Exec 2010 R3 Deduplication Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?

A Windows Security Alert pop-up will appear, click Unblock. 5. Backup Exec 2010 R3 Sp2 I have a few comments/questions about your scenario. It is recommended that a complete backup of the registry and workstation be made prior tomaking any registry changes.Goto the following registry key: HKEY_CLASSES_ROOT\CLSID\ Locate the 'AppID' String Value key and Connect with top rated Experts 9 Experts available now in Live!

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 Symantec Backup Exec 2010 R3 Server Suite I tried instal with local administrator account and gave all sorts of rights, but to no avail. Solved "Error connecting to the remote registry" when pushing remote agent for Backup Exec Posted on 2008-06-01 Storage Software Windows Server 2003 1 Verified Solution 6 Comments 8,432 Views Last Modified: 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

Backup Exec 2010 R3 Sp2

Take note of the exact 'CLSID' and 'user' noted within the description of the Windows DCOM System Event. (See Figure 2)Fig 2 In this example, we see the CLSID to be {555F3418-D99E-4E51-800A-6E89CFD8B1D7}2. It is possible that updates have been made to the original version after this document was translated and published. Symantec Backup Exec 2010 R3 Remote Agent Download So you can use the window remote computer credentials successful? Backup Exec 2010 R3 Admin Guide OnlyEvent ID 4634: An account was successfully logged off.

No Yes How can we make this article more helpful? this contact form You can also make sure that the RAWS agent is actually running on those servers giving you hassles. Privacy Policy Site Map Support Terms of Use Home Issues with installing Symantec Backup Exec Remote Agent by jhansen_fl on Sep 15, 2015 at 1:59 UTC | Data Backup 0Spice Down No Yes How can we make this article more helpful? Upgrade Backup Exec 2010 R3 To 2012

You may get a better answer to your question by starting a new discussion. not so much. Thanks! 0 Kudos Reply Update Agents/Install Agents via push Nick_Elmer Level 6 Employee ‎07-18-2011 08:21 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a have a peek here Your comments indicate that you have local adminpermissions on the media server, but not on some other servers.

Thanks for your help, 0 Message Author Comment by:davidrobertbristow2008-06-02 Sorry, "act as part of the Operating System" user rights assignment is also the same for both success and failed (lists Backup Exec 2010 R3 Download Iso Go to the Agent directory under the BE installation directory and then copy either the RAWS32/RAWS64 directory over to the remote machine and then do the agent installation from the copied This is required to launch the install, and make the necessary changes to the system during the install/update.

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:

Why? My new house... I am able to log on through TS as an Administrator on failed. Backup Exec 2010 R3 Sp1 Download In system log is nothing.

Ensure the server is available, has WMI enabled, and is not blocked by a firewall. 1603." It seems like this is the likely problem, mentioned in the below Symantec technote: http://www.symantec.com/business/support/index?page=content&id=TECH128062 I'm pushing this out from the Symantec BE software and it keeps giving me the following error when it goes to validate the install; Error connecting to the remote computer. No Yes About Us Our Team Vendor Partners Careers Locations Upcoming Events Technology Solutions VoIP & Video Conferencing Networking & Security Application Delivery & Mobility Virtualization & Cloud Printers & Copiers Check This Out Check this microsoft article http://support.microsoft.com/kb/314837 additionally Check if this user has the log on locally, act as part of OS and long interactively permissions on these two servers.

No Yes How can we make this article more helpful? Office locations in Denver, Boulder, Colorado Springs, Fort Collins, Glenwood Springs, Pueblo, Silverthorne, Albuquerque, Santa Fe and Cheyenne. Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : Error connecting to the remote computer. Powered by Blogger.

Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Reply Subscribe RELATED TOPICS: Slow backup using Symantec Backup Exec Symantec Backup Exec is at it again. Click Start | Run | RegeditWarning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. 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

As with Backup Exec 2012, the Backup Exec button in the upper left corner. Add the User 'LOCAL SERVICE' to the Group or user names list and give Allow access for these permissions:   Local Launch Remote Launch Local Activation Remote Activation   Fig 7 Click You may also refer to the English Version of this knowledge base article for up-to-date information. Join the community Back I agree Powerful tools you need, all for free.

Posted by IT's Amazing at 8:34 AM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Labels: Symantec Backup Exec 2010 No comments: Post a Comment Newer Post Older Post Home Subscribe Sorry, we couldn't post your feedback right now, please try again later. Examples: 1.If the Backup Exec 2010 R3 or aboveRemote agent for Windows (RAWS) is installed manually,the Trust must be established before selecting the remote computer for backup or an existing selection IN THIS DISCUSSION Join the Community!

I have verified that the remote registry service is running.

© Copyright 2017 gatoisland.com. All rights reserved.