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

Backup Exec Error Connecting To The Remote Computer Ensure

Contents

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. 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. 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 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 Source

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 No Yes How can we make this article more helpful? Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Error connecting to the remote computer. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue?

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

Thanks! 0 Kudos Reply Enterprise Admins is more CraigV Moderator Partner Trusted Advisor Accredited ‎11-18-2012 10:08 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to Sorry, we couldn't post your feedback right now, please try again later. Otherwise, register and sign in. Sorry, we couldn't post your feedback right now, please try again later.

Does this make a difference? 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). Now i have the access to Server 2008 R2 Exchange for backup. How To Install Backup Exec Remote Agent Manually AndEvent ID 4672 for my "backup-user": SeCreateTokenPrivilege SeSecurityPrivilege SeBackupPrivilege SeRestorePrivilege SeTakeOwnershipPrivilege SeDebugPrivilege SeSystemEnvironmentPrivilege SeLoadDriverPrivilege SeImpersonatePrivilege 0 Kudos Reply I installedRAWS64(Local).

No Yes Home | Site Map | Cisco How To | Net How To | Wireless |Search| Forums | Services | Donations | Careers | About Us | Contact Us| Backup Exec Cannot Connect To Remote Computer Why? Promoted by Experts Exchange Engage with tech pros in our community with native advertising, as a Vendor Expert, and more. Enter: cd c:\ netsh firewall set service type=remoteadmin mode=enable This will return the following: "IMPORTANT: Command executed 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 0xe00086ce Make sure... If you've already registered, sign in. Serves run with local system account.

  1. But, the Exec show me the size0 Kb ofmy DB!
  2. 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.
  3. 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.
  4. Ensure the server is available, has WMI enabled, and is not blocked by a firewall. 1603."   Error Message Error connecting to the remote server.
  5. No Yes How can we make this article more helpful?

Backup Exec Cannot Connect To Remote Computer

No Yes Did this article save you the trouble of contacting technical support? for eg. 14,24,1603 ?? Backup Exec Error Connecting To The Remote Computer Ensure That The Computer Is Available Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Backup Exec (BE) 2010 push install of the Backup Exec Remote Agent The Backup Exec Server Could Not Connect To The Remote Computer No Yes How can we make this article more helpful?

Covered by US Patent. this contact form 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 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. Check the following. Ensure That The Computer Is Available Has Wmi Enabled And Is Not Blocked By A Firewall 67

Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : Error connecting to the remote computer. Join the community of 500,000 technology professionals and ask your questions. Backup Exec 2010 push install of the Remote Agent fails with error: Error connecting to the remote computer. have a peek here Get 1:1 Help Now Advertise Here Enjoyed your answer?

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 Ensure that the computer is available, has WMI enabled 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 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

Comment Submit Your Comment By clicking you are agreeing to Experts Exchange's Terms of Use.

As a Xerox company, you can depend on our 40 years of providing local solutions, service and support, backed by the trusted Xerox name. 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 Thank you very much! But Exec is very terribly slow.

My DB have size 50Gb 0 Kudos Reply ...check this CraigV Moderator Partner Trusted Advisor Accredited ‎04-30-2013 01:06 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Examples: 1. Learned this many,many years ago. Check This Out 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

Thank You! Everytime I try to push the agent out to it it gives the following error: "Error connecting to the remote computer. I can also ping the sbs box in the reverse direction.

© Copyright 2017 gatoisland.com. All rights reserved.