waspsoft.com


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

Backup Exec Error Connecting To The Remote Computer

Contents

The servers that already had remote agent on them from BE 2010 had no problem ungrading. Ok." Then enter: NETSH advfirewall firewall SET rule group="remote administration" new enable=yes This will return the following: "Updated 3 rule(s).
 Ok." You can then close the command prompt and retry 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 A Windows Security Alert pop-up will appear, click Unblock. 5. have a peek here

I suspect there is a bug when the remote hosts are verifying the installation to check if you haves RAWS installed and what version you are running. 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 You may also refer to the English Version of this knowledge base article for up-to-date information. Thank you for your feedback!

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

Labels: 2010 Agents Backup and Recovery Backup Exec Best Practice Configuring Installing Tip-How to Upgrade 0 Kudos Reply 8 Replies Hi St3phan, Might have CraigV Moderator Partner Trusted Advisor Accredited I have a few comments/questions about your scenario. 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

I had the problem with the R2, too. Join our community for more solutions or to ask questions. Enter: cd c:\ netsh firewall set service type=remoteadmin mode=enable This will return the following: "IMPORTANT: Command executed successfully. Backup Exec Cannot Connect To The Remote Computer Because A Trust Was Not Established This will allow each of the backups to be kept separate preventing the previous day’s backup from being overwritten.

I tried instal with local administrator account and gave all sorts of rights, but to no avail. Error Connecting To The Remote Registry Thanks. 0 Kudos You must be a registered user to add a comment. No Yes Did this article save you the trouble of contacting technical support? Join & Ask a Question Need Help in Real-Time?

Hope this helps, Nick 0 Kudos Reply I've just experienced the BMcGinnis Level 2 ‎07-28-2011 09:54 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to Error Connecting To The Remote Registry Backup Exec 2010 Make sure that the computer is available, WMI is enabled and not blocked Windows Firewall.14 DenisFrolov Level 3 ‎04-29-2013 06:57 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed I can't find it anywhere. We also have Server 2008 acting as a fileserver.

  • 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
  • No Yes Did this article save you the trouble of contacting technical support?
  • 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
  • Its DenisFrolov Level 3 ‎04-29-2013 11:58 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content No, i have another id.
  • Even specifying the domain admin credentials through the wizard for the RAWS installation account I was receiving the remote registry error.
  • Thank You!
  • It is possible that updates have been made to the original version after this document was translated and published.
  • If you do, this becomes easy...you put your BESA account into the Domain Admins Group in the remote domain, and use that account for the BE services on the remote media
  • CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical
  • RAWS does not need a service account, as it runs as local system.

Error Connecting To The Remote Registry

Try adding that domain in and see if it makes any difference. 0 Kudos Reply Hey CraigV, How do I add IPG Level 4 ‎11-19-2012 12:23 PM Options Mark as New Re-attempt the push installSystem account could be blocking the setup.   If a push/local install of RAWS fails with the error 1603 still and is accompanied by the below event log Backup Exec Error Connecting To The Remote Computer Ensure That The Computer Is Available Add this into your CASO and when you push-install (or even locally install) you'd use this account. Backup Exec Cannot Connect To Remote Computer Nick_Elmer Level 6 Employee ‎09-15-2011 10:35 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content BMcGinnis, A co-worker happened to

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 http://waspsoft.com/backup-exec/backup-exec-error-connecting-to-the-remote-computer-24.html Backup Exec requires administrative credentials to the remote machine to do the push. Ensure that the computer is available, has WMI enabled and is not blocked by a firewall" Error Message Error connecting to the remote computer. During theupdateof theagents(includingtheinstallationof agents), Inoticedthe following: I logged ontheBackupExecmediaserver with my personal accountthatisno member of thedomainadminsandalso has no access to someservers. The Backup Exec Server Could Not Connect To The Remote Computer

After this phase when you start the installation then it uses the specified credentials. Microsoft .Net 3.5 is required. Thanks! 0 Kudos Reply Hey CraigV, I do have a trust IPG Level 4 ‎11-18-2012 01:41 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to http://waspsoft.com/backup-exec/backup-exec-error-connecting-remote-computer.html You might also need to edit the hosts file on both servers so that they can resolve each other manually!

If you've already registered, sign in. Backup Exec Error 1603 When Installing A Remote Agent Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : Push-Install Backup Exec Server Failing VOX : Backup and Recovery : Backup Exec 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.

DenisFrolov Level 3 ‎04-30-2013 01:04 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content I installedRAWS64(Local).

Nick_Elmer Level 6 Employee ‎09-14-2011 07:32 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Thank you for your feedback Ensure that the computer is available, has WMI enabled, and is not blocked by a firewall. And if so how do I open them? 0 Question by:Paul-Brooks Facebook Twitter LinkedIn Google LVL 29 Active today Best Solution bypgm554 FYI,Symantec tech support unofficially sez the best way to Ensure That The Computer Is Available Has Wmi Enabled And Is Not Blocked By A Firewall 67 Comment Submit Your Comment By clicking you are agreeing to Experts Exchange's Terms of Use.

Lewan Technology is a business technology and managed service provider serving Colorado, Wyoming, New Mexico and beyond. No Yes How can we make this article more helpful? 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. this contact form But now: Microsoft Exchange 2010 database backup fails with V-79-57344-913 database was not found error.

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 Create/Manage Case QUESTIONS? I'll try to setup a test like you mention above and see what is happening. Right Click on the DCOM Object that matches and select 'Properties' and select the 'Security' tabFig 5 7.

I have tried: Turning off the firewall on the remote server Checking WMI is enabled (I can connect to the WMI from the CAS server via WMI Management MMC) Push-Installing as http://www.symantec.com/business/support/index?page=content&id=TECH180429 will it work? 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 Its 14.

Only thing of note on the old box is a copy of vmware 2 hosting an accounts application Is there any way vmware will be blocking the ports I need? Veritas does not guarantee the accuracy regarding the completeness of the translation. VOX : Backup and Recovery : Backup Exec : Error connecting to the remote computer. 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

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. Featured Post Top 6 Sources for Identifying Threat Actor TTPs Promoted by Recorded Future Understanding your enemy is essential.