Backup Exec Error Connecting To The Remote Computer 1603
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 backup exec error 1603 when installing a remote agent Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange
Backup Exec Error Connecting To The Remote Computer Ensure That The Computer Is Available
Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español backup exec error connecting to the remote registry 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 fails with
Error Connecting To The Remote Registry Backup Exec 2010
"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 Logout Sign in backup exec error code 1603 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
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
Ensure That The Computer Is Available Has Wmi Enabled And Is Not Blocked By A Firewall 67
Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español
0xe00086ce
USA Site: Veritas Veritas PartnerNet Error 1603 when installing or updating the Remote Agent for Windows Systems via the push install method. Article:000013971 Publish: Article URL:http://www.veritas.com/docs/000013971 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 https://www.veritas.com/support/en_US/article.TECH128062 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 Manual installation of the Remote Agent for Windows Systems (RAWS) works fine, but when attempting to install or upgrade it via the push install method fails at the beginning of the procedure. Error Message "Error connecting to the remote https://www.veritas.com/support/en_US/article.000013971 server. Ensure the server is available, has WMI enabled, and is not blocked by a firewall. 1603." Cause The "remote registry" service in the destination server is disabled. Solution 1) Log on to the target server where RAWS is to be installed. 2) Open Windows Services applet (services.msc) 3) Locate "Remote registry" service. 4) If the service is disabled, enable it. 5) Retry the operation from the Media Server. Check the related technical articles for more information. Terms of use for this information are found in Legal Notices.
Related Articles Article Languages x Translated Content Please note that this document is a translation from English, and may have been machine-translated. It is possible that updates have been made to the original version after this document was translated and published. Veritas does not guarantee the accuracy regarding the completeness of the translation. You may also refer to the English Version of this knowledge base article for up-to-date information. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? No Yes Did this article save you the trouble of contacting technical support? No Yes How can we make this article more helpful? EManaged IT Services Managed Infrastructure Managed Cloud Hosting Managed Print Managed Data Protection Managed Network Security Managed Technology Spend Blog Contact Us Customer Support Lewan Technology Blog The latest insights, industry news, tips and topics from our team of http://www.lewan.com/blog/2010/09/28/backup-exec-2010-r2-remote-agent-install-error-code-1603 experts. Backup Exec 2010 R2 - Remote Agent Install Error Code 1603 [fa icon="long-arrow-left"] https://www.experts-exchange.com/questions/28005478/Installing-symantec-agent-to-vmware-host.html Back to all posts [fa icon="pencil'] Posted by Lewan Solutions [fa icon="calendar"] September 28, 2010 Tweet While onsite trying to remotely push a Backup Exec 2010 R2 remote agent, we were getting a lot of the "error code 1603" messages, which stated: "Error connecting to the remote server. Ensure the server is available, has WMI enabled, and backup exec 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 Our workaround was to just install the client manually on each server that wouldn't connect, instead of going through all the steps mentioned in the above technote. Written by Lewan Solutions View & Submit Comments [fa icon="envelope"] Subscribe to Email Updates Search Blog Posts in Google [fa icon="comments-o"] Follow us backup exec error Get even more great content, photos, event info and industry news. [fa icon="tags"] Posts by Topic VMware (175) Citrix (130) Microsoft (115) Microsoft Windows (79) Citrix XenDesktop (69) Citrix XenApp (65) How To Guide (57) Virtualization (55) VMware vSphere (48) Managed Services (36) Cisco (33) Data Storage (31) Apple (25) Lewan Awards & Certifications (22) Lewan News & PR (18) Microsoft Exchange (18) Data Backup & Recovery (17) Microsoft Hyper-V (15) Cloud Computing (14) NetApp (13) Paper (12) Paperless Solutions (12) Data Security (10) Dell (10) Disk Performance (10) IT Solutions (10) Managed Infrastructure & Helpdesk (10) Citrix XenServer (9) Lewan Events (9) Printers & Copiers (9) Xerox (9) AppSense (8) HP (8) Networking (8) Sales Technique (8) Linux (7) Microsoft Office (7) PowerShell (6) Citrix Storefront (5) Unified Communication & Collaboration (5) VMware vCenter (5) Citrix XenMobile (4) Email Security (4) infographic (4) CommVault (3) CRN (3) Fortrust (3) Google (3) Microsoft Outlook (3) Nimble Storage (3) Unidesk (3) Barracuda (2) Microsoft Azure (2) Product Announcements (2) Fax Solutions (1) Microsoft System Center Configuration Manager (1) NetScaler (1) RES Software (1) see all [fa icon="calendar"] Recent Posts Citrix Provisioning Services (PVS) vs. Machine Creation Services (MCS) 3 Questions to Ask When Evaluating Managed Print Services companies Error fix: Microsoft SCCM 2
Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > Installing symantec agent to vmware host Want to Advertise Here? Solved Installing symantec agent to vmware host Posted on 2013-01-23 Storage Software 1 Verified Solution 6 Comments 982 Views Last Modified: 2013-02-12 Hi, Got an old server that currently backs up to a disk on another server using an old local copy of symantec. 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. Everytime I try to push the agent out to it it gives the following error: "Error connecting to the remote computer. Ensure that the computer is available, has WMI enabled, and is not currently blocked by a firewall" There is no active firewall and WMI is active and I can ping the machine I'm trying to push the agent to. I can also ping the sbs box in the reverse direction. 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? 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 install the agent is manually. Learned this many,many years ago. 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 error message ??? for eg. 14,24,1603 ?? Check the following. Backup Exec 2010 push install of the Remote Agent fails with error: Error connecting to the remote computer. Ensure that the computer is available, has WMI enabled, and is not blocked by a firewall.24 http://www.symantec.com/docs/TECH177320 How to enable firewall rules on windows server 2008 R2 to enable PUSH install of Remote agent for windows servers http://www.symantec.com/docs/TECH146818 0 LVL 23 Overall: Level 23 Storage Software 20 Message Active 3 days ago Expert Comment by:Iamthecreator2013-01-23 Edited the previous post to correct the second link. 0 Message Author Comment by:Paul-Brooks2013-01-23 I've followed up both your links and both had the correct settings already and no changes were needed. Apologies for the misquote in the OP,