Error Connecting To Remote Registry Backup Exec 2010
Contents |
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 backup exec 2010 error connecting to the remote server suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches backup exec error connecting to the remote computer as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : Backup Exec : Problem backup exec error connecting to the remote computer ensure that the computer is available installing Remote Agent for Windows Server... VOX : Backup and Recovery : Backup Exec : Problem installing Remote Agent for Windows Server... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this
Ensure That The Computer Is Available Has Wmi Enabled And Is Not Blocked By A Firewall 67
Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution Problem installing Remote Agent for Windows Server on Backup Exec 2010 seguridadallus Level 2 ‎04-11-2013 12:41 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi I have a problem with Backup Exec 2010 attempting install Remote Agent on a Windows Server 2008 Enterprise with Microsoft Exchange. backup exec cannot connect to the remote computer The issue appears when I try to install through Backup Server the agent on the other server, and say: "Error connecting to the remote registry of server. Ensure that the current logged in account is not blocked from accessing the remote registry and that the remote registry is available before try again." So the account is not blocked, password is OK and got administrator privileges, but the error keep appearing and is not allowing install Remote Agent. How I solve this issue? Thanks in advance. Lucas. Solved! Go to Solution. Labels: 2010 Agents Backup and Recovery Backup Exec Configuring Error messages Installing Troubleshooting Windows Server (2003-2008) 1 Kudo Reply 1 Solution Accepted Solutions Accepted Solution! Yep, I finally get solve the seguridadallus Level 2 ‎04-16-2013 07:30 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Yep, I finally get solve the issue mannually and I can validate credentials between BE10 and RAWS, but remote installation keep failing. What I made was modify X:\WINDOWS\SYSTEM32\DRIVERS\ETC\services and add this value ndmp 10000/tcp #BE10 I'll try repair BE10 for the moment Thanks a lot! View solution in original post 0 Kudos Reply 7 Replies Hi, Any firewall/AV CraigV Moderator Partner Trusted Advisor Accredite
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 Contact Us English ä¸æ–‡(简体) English Français Deutsch Italiano 日本語 í•œêµì–´ Português Español USA Site: Veritas Veritas PartnerNet A push install of the remote agent fails with: "Error connecting to the remote computer. 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 https://vox.veritas.com/t5/Backup-Exec/Problem-installing-Remote-Agent-for-Windows-Server-on-Backup/td-p/583798 have a Veritas Account? 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. https://www.veritas.com/support/en_US/article.TECH177317 Ensure that the computer is available, 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
for 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 https://www.experts-exchange.com/questions/23448709/Error-connecting-to-the-remote-registry-when-pushing-remote-agent-for-Backup-Exec.html 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 > "Error connecting to the remote registry" http://www.tremka.com/showthread.php?8155-Agent-Update-Error-connecting-to-the-remote-registry-of-Server when pushing remote agent for Backup Exec Want to Advertise Here? Solved "Error connecting to the remote registry" when pushing remote agent for Backup Exec Posted on 2008-06-01 Storage Software Windows Server 2003 1 backup exec Verified Solution 6 Comments 8,444 Views Last Modified: 2013-12-01 Question: I have Backup Exec installed on a Win2003 server. I am pushing remote agents to my other servers. 6 servers have installed the remote agent successfully. However, 2 of them give the message "Error connecting to the remote registry". I have verified that the remote registry service is running. I have also checked that mydomain\administrators have full permissions to error connecting to the registry entry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\ SecurePipeServers\winreg as outlined in the Veritas article http://seer.entsupport.symantec.com/docs/240179.htm Thanks in advance, 0 Question by:davidrobertbristow Facebook Twitter LinkedIn Google Best Solution bydavidrobertbristow I have decided to do a local install of the remote agent and it worked great on my 2 problem servers. Thanks again for your responses. Go to Solution 6 Comments LVL 23 Overall: Level 23 Storage Software 12 Windows Server 2003 8 Message Active today Expert Comment by:bhanukir72008-06-01 Hi i think there might some restrictions for the user a/c you are using to deploy the software. Check this microsoft article http://support.microsoft.com/kb/314837 additionally Check if this user has the log on locally, act as part of OS and long interactively permissions on these two servers. bhanu 0 Message Author Comment by:davidrobertbristow2008-06-02 Thanks. I'll try your solution over the next hour and let you know how it works out. 0 Message Author Comment by:davidrobertbristow2008-06-02 Okay, regarding http://support.microsoft.com/kb/314837 mydomain\administrators have full control to the winreg key. I am comparing two servers, sames OS win2003, one of which allowed me to write to the registry (let's call it "success") and the other which didn't (let's call it "failed"). The difference that I see is that "failed" has a k
the remote registry of Server Sehr geehrte Kunden und Forum-Besucher, ab sofort können Sie unsere neuen Workshop´s zu den Themen Endpoint Protection und Backup Exec buchen. Ergebnis 1 bis 1 von 1 Thema: Agent Update: Error connecting to the remote registry of Server Themen-Optionen Druckbare Version zeigen Thema weiterempfehlen… Thema abonnieren… Anzeige Linear-Darstellung Zur Hybrid-Darstellung wechseln Zur Baum-Darstellung wechseln 24.05.2011,14:33 #1 news_catcher Profil Beiträge anzeigen Private Nachricht Blog anzeigen Homepage besuchen Artikel anzeigen Erfahrener Benutzer Registriert seit 09.08.2010 Beiträge 63.166 Agent Update: Error connecting to the remote registry of Server I have a problem with the Agent Update of Backup Exec from 2010 R2 to R3. During the update of the agents (including the installation of agents), I noticed the following: I logged on the Backup Exec media server with my personal account that is no member of the domain admins and also has no access to some servers. On the media servers this account has local admin priviledges and is also listed as user in Backup Exec If I want to update the agents on the servers, I get the error: Error connecting to the remote registry of servers. Ensure that the current logged in accountis not blocked from accessing the remote registry and that the remote registry is available before trying again. This would also seem logical as far as when I will not have a window to set the user credentials for the remote computer. I entered the correct remote computer credentials in this window: The account that I use is definitely a localadmin on all servers. With this account, the Backup Exec services run, too. Interestingly, it is possible to update the agents when I login to the Backup Exec mediaserver with this account that is local admin on all servers and running the services. I read this TechNote: http://www.symantec.com/docs/HOWTO22459, but why could I enter a valid Logon Account in this upper window that we no used? Did anybody knows this behavoir and could tell me how I can fix this? Weiterlesen... Zitieren Gehe zu: Aktuelle Themen aus dem Symantec Connect Forum Nach oben Bereiche Benutzerkontrollzentrum Private Nachrichten Abonnements Wer ist online Foren durchsuchen Forum-Startseite Foren Allgemeines Welcome Dit un Dat News aus dem Netz Clips Symantec Aktuelle Risiken Aktuelle Themen aus dem Symantec Connect Forum Ba