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

Backup Exec 2012 Agent Error Connecting To The Remote Computer

Contents

Now i have the access to Server 2008 R2 Exchange for backup. 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. Ensure that the computer is available, has WMI enabled, and is not blocked by a firewall. 1603". All rights reserved. Source

Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Covered by US Patent. Domain account with full administrator rights. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application.

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" Error Message Error connecting to the remote computer. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? Email Address (Optional) Your feedback has been submitted successfully! Ensure the server is available, has WMI enabled, and is not blocked by a firewall. 1603."   Error Message Error connecting to the remote server.

  • In system log is nothing.
  • 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 Home | Site Map | Cisco How To | Net How To | Wireless |Search| Forums | Services | Donations | Careers | About Us | Contact Us|
  • 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
  • Great care should be taken when making changes to a Windows registry.
  • Our domain controller is SBS 2003 running exchange, it also runs the backup exec.
  • 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
  • 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
  • Everytime I try to push the agent out to it it gives the following error: "Error connecting to the remote computer.

Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : Backup Exec : Error connecting to the remote computer. Under 'Launch and Activation Permissions' select the 'Customize' radio button and click EditFig 6 8. Join Now For immediate help use Live now! Backup Exec Cannot Connect To The Remote Computer 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

I tried instal with local administrator account and gave all sorts of rights, but to no avail. The Backup Exec Server Could Not Connect To The Remote Computer Click Start | Run | RegeditWarning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Sorry, we couldn't post your feedback right now, please try again later. 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

Join & Ask a Question Need Help in Real-Time? 0xe00086ce It is possible that updates have been made to the original version after this document was translated and published. Comodo Backup is another solution for backing up your computer. 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.

The Backup Exec Server Could Not Connect To The Remote Computer

Check It Out Suggested Solutions Title # Comments Views Activity Commvault (I think) Icons 4 53 81d Dell Powervault 3220i... OnlyEvent ID 4634: An account was successfully logged off. Backup Exec Error Connecting To The Remote Computer Ensure That The Computer Is Available Email Address (Optional) Your feedback has been submitted successfully! Backup Exec Remote Agent Error 1603 No Yes How can we make this article more helpful?

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... this contact form 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 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 Followed the above procedure and afterwards, the push install worked. How To Install Backup Exec Remote Agent Manually

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 It is possible that updates have been made to the original version after this document was translated and published. 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 have a peek here Ensure that the computer is available, has WMI enabled, and is not currently blocked by a firewall.14" I've tried turning off the firewall as per http://www.symantec.com/business/support/index?page=content&id=TECH148594 in all 3 modes, still

Update the password in Backup Exec Tools > Backup Exec Services > Services Credentials.Update the password in Network > Logon Accounts.Edit the System Logon Account > Change Password > OKRestart Backup Thank You! It is possible that updates have been made to the original version after this document was translated and published.

Machine Creation Services (MCS) 3 Questions to Ask When Evaluating Managed Print Services companies Error fix: Microsoft SCCM 2012 Error Code Ox87D00668 (.NET Patching Issue) Controlling Printing Costs with Print Governance

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 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. Sorry, we couldn't post your feedback right now, please try again later. 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

Thank you very much! V-79-57344-3844   Cause Media Server's FQDN (Fully Qualified Domain Name) or IP address is not entered in the Publishing tab of Backup Exec Remote Agent Utility on the remote server.Password for The weird thing is, because we use SEPM the Windows Firewall is not running on the target server, the firewall service is not even running and it still worked. http://gatoisland.com/backup-exec/backup-exec-2012-agent-error-connecting-to-the-remote-registry.php Reboot the Workstation or Server wherein this DCOM change occurred.10.

Create/Manage Case QUESTIONS? Every workstation that I have done this to has worked perfectly since. I can also ping the sbs box in the reverse direction. Join our community for more solutions or to ask questions.

The servers that already had remote agent on them from BE 2010 had no problem ungrading. Ensure that the computer is available, has WMI enabled, and is not blocked by a firewall. 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 Retain evidence of this with email archiving to protect your employees.

© Copyright 2017 gatoisland.com. All rights reserved.