waspsoft.com


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

Backup Exec Error Connecting To The Remote Computer Ensure

Contents

Veritas does not guarantee the accuracy regarding the completeness of the translation. A Windows Security Alert pop-up will appear, click Unblock. 5. 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 Ensure that the computer is available, has WMI enabled, and is not blocked by a firewall. 14". have a peek here

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 No Yes How can we make this article more helpful? No Yes Did this article save you the trouble of contacting technical support? You may also refer to the English Version of this knowledge base article for up-to-date information.

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

Create/Manage Case QUESTIONS? Everytime I try to push the agent out to it it gives the following error: "Error connecting to the remote computer. Network access to server is have. Promoted by Experts Exchange Engage with tech pros in our community with native advertising, as a Vendor Expert, and more.

http://www.symantec.com/business/support/index?page=content&id=TECH180429 will it work? 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 Covered by US Patent. How To Install Backup Exec Remote Agent Manually To open the File History control panel swipe from the right side to get the search menu or position the cursor in the… PCs Windows 8 Storage Software Advertise Here 845

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 Backup Exec Cannot Connect To Remote Computer Great care should be taken when making changes to a Windows registry. Its 14. Lewan Technology is a business technology and managed service provider serving Colorado, Wyoming, New Mexico and beyond.

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 0xe00086ce 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 Any other suggestions would be awesome... If you've already registered, sign in.

  1. Thanks! 0 Kudos Reply Instaled.
  2. Bug FIx: View Templates Folder in Azure Resource Manager Premium Storage Error Fix: "The App-V server addresses must be valid URLs" in XenApp/XenDesktop 7.9 About Us We manage your printing and
  3. I've done it this way before but we had a trust between the company's 2 domains (1 in Africa/South Africa and 1 in Asia).
  4. Apologies for the misquote in the OP, the full error is "Error connecting to the remote computer.
  5. Serves run with local system account.
  6. 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
  7. We also have Server 2008 acting as a fileserver.

Backup Exec Cannot Connect To Remote Computer

Enter: cd c:\ netsh firewall set service type=remoteadmin mode=enable This will return the following: "IMPORTANT: Command executed successfully. 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 Backup Exec Error Connecting To The Remote Computer Ensure That The Computer Is Available Ensure that the computer is available, has WMI enabled, and is not blocked by a firewall. 1603". The Backup Exec Server Could Not Connect To The Remote Computer 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

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. http://waspsoft.com/backup-exec/backup-exec-error-connecting-remote-computer.html Open your command prompt on the workstation. Thanks. 0 Kudos You must be a registered user to add a comment. 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: Ensure That The Computer Is Available Has Wmi Enabled And Is Not Blocked By A Firewall 67

It will prompt to authorize the server or not. Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : Error connecting to the remote computer. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Check This Out After working with the problem for some time I found that remote administration needed to be let through the firewall as well.

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 Agent has been installed very good on the other server. Ensure the server is available, has WMI enabled, and is not blocked by a firewall. 1603."   Error Message Error connecting to the remote server.

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

All rights reserved. Join our community for more solutions or to ask questions. 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 AndEvent ID 4672 for my "backup-user": SeCreateTokenPrivilege SeSecurityPrivilege SeBackupPrivilege SeRestorePrivilege SeTakeOwnershipPrivilege SeDebugPrivilege SeSystemEnvironmentPrivilege SeLoadDriverPrivilege SeImpersonatePrivilege 0 Kudos Reply I installedRAWS64(Local).

Showing results for  Search instead for  Do you mean  VOX : Blogs : Backup & Recovery Community Blog : Fix for Error 1603 When trying to push install age... 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 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 this contact form No Yes Home | Site Map | Cisco How To | Net How To | Wireless |Search| Forums | Services | Donations | Careers | About Us | Contact Us|

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. 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 Thank You! 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

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.