Backup Exec Error Connecting To The Remote Computer 24
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal
Backup Exec Error Connecting To The Remote Computer Ensure That The Computer Is Available
Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA backup exec cannot connect to remote computer Site: Veritas Veritas PartnerNet A push install of the remote agent fails with: "Error connecting to the remote computer. Ensure
The Backup Exec Server Could Not Connect To The Remote Computer
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 Veritas Account? backup exec cannot connect to the remote computer because a trust was not established Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Push install of the Backup Exec Remote Agent to a Remote Windows Server fails with error: "Error connecting to the remote computer. Ensure that the computer is available, error connecting to the remote registry backup exec has WMI enabled and is not blocked by a firewall" Error Message Error connecting to the remote computer. Ensure that the computer is available, has WMI enabled, and is not blocked by a firewall. 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 the remote server, run setup.exe from the RAWS32/RAWS64 folder and complete the install.Make sure to enable "Publishing" on the remote agent. For that launch Remote Agent Utility from Programs list or double click on the Remote Agent icon in the system tray. 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 server has NDMP running on any port other than 10000, then this can also cause the failure.To check which port NDMP is using, follow the article: www.symantec.com/docs/TECH24256If there is no entry in the services file (located at C:\Windows\System32\Drivers\etc) for NDMP, means its using the default port 10000.If the ports are different on both, the media server and remote server, then make the
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs
Error Connecting To The Remote Registry Backup Exec 2010
Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research ensure that the computer is available has wmi enabled and is not blocked by a firewall 67 Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português
How To Install Backup Exec Remote Agent Manually
Español USA Site: Veritas Veritas PartnerNet Push install of the Backup Exec 2010 Remote Agent and/or Desktop Laptop Agent (DLO) to a remote Windows server https://www.veritas.com/support/en_US/article.TECH177317 fails with "Error connecting to the remote server. Ensure the server is available, has WMI enabled, and is not blocked by a firewall. 1603" Article:000006395 Publish: Article URL:http://www.veritas.com/docs/000006395 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile https://www.veritas.com/support/en_US/article.TECH128062 Logout Sign in to Subscribe Please sign in to set up your subscription. 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 and/or Desktop Laptop Agent (DLO) to a Remote Windows Server fails with error: "Error connecting to the remote 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. 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 push log
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest https://vox.veritas.com/t5/Backup-Exec/2010-remote-agent-installation-error/td-p/296726 helps you quickly narrow down your search results by suggesting possible matches as you http://www.chicagotech.net/netforums/viewtopic.php?f=3&t=15781 type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : Backup Exec : 2010 remote agent installation error VOX : Backup and Recovery : Backup Exec : 2010 remote agent installation error Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer backup exec Friendly Page Solved! Go to Solution 2010 remote agent installation error Mooser N/A 03-18-2010 11:56 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content I get the following when trying to push out a remote agent with Backup Exec 2010 "Error connecting to the remote server. Ensure that the server is available, has WMI enabled, and is not blocked by a firewall.24" I to the remote have verified that WMI is working, there is no firewall blocking traffic and I can ping and remote into the server from the main box where the Backup Exec software is installed. This is one of many virtualized servers on the network. I could get the agent pushed out on other servers except for this one. It had a previous remote agent installed on all the servers. I was able to successfully detect and upgrade the others, however; I keep getting this error even after un-installing, rebooting, and trying to re-install the agent again. Any ideas? Solved! Go to Solution. Labels: 2010 Backup and Recovery Backup Exec Troubleshooting 2 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! Solution Works - Nr. 2 s_hasslinger N/A Partner Accredited 08-02-2010 01:35 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi, i ajusted the policies -Adjust Memory Quotas for Process Properties -Replace a process level token in a new group policy rolled out to the Backup Servers. On German Server called: -Anpassen von Speicherkontingenten für einen Prozess -Ersetzen eines Tokens auf Prozessebene -> make a gpudate /force It Works fine since the changes, Thank You! View solution in original post 0 Kudos Reply 7 Replies I am having the same issue. Mike_Se