Error Connecting To The Remote Registry
Contents |
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery error connecting to the remote registry backup exec 2010 Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs error connecting to the remote registry backup exec Groups Vision 2016 Sign In CommunityCategoryBoardResourcesUsers
Backup Exec Error Reading Remote Registry
turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for
Error Connecting Network Registry
Search instead for Do you mean VOX : Backup and Recovery : Backup Exec : Agent Update: Error connecting to the remote regis... VOX : Backup and Recovery : Backup Exec : Agent Update: Error connecting to the remote regis... Subscribe to RSS Feed Mark Topic as error connecting to the remote server ensure that the server is available New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Agent Update: Error connecting to the remote registry of Server St3phan Level 3 05-24-2011 02:42 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content I have a problem with the Agent Update of Backup Exec from 2010 R2 to R3. During theupdateof theagents(includingtheinstallationof agents), Inoticedthe following: I logged ontheBackupExecmediaserver with my personal accountthatisno member of thedomainadminsandalso has no access to someservers. Onthe mediaservers this account has local admin priviledges and is also listed as user in Backup Exec If Iwantto updatetheagentson theservers, I getthe error:Errorconnectingtotheremoteregistryofservers.Ensurethatthecurrentloggedinaccountisnotblockedfromaccessingtheremoteregistryandthattheremoteregistryisavailablebeforetryingagain. Thiswouldalsoseemlogicalas far aswhenI will not have awindowto set theusercredentialsfortheremote computer. I entered the correct remote computer credentials in this window: Theaccount thatIuseisdefinitelya localadminonallservers.Withthis account,theBackup
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
Error Connecting To The Remote Computer Backup Exec
suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches connect to remote registry windows 7 as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : Backup Exec : connect to remote registry using powershell Error connecting to the remote computer. Make sure... VOX : Backup and Recovery : Backup Exec : Error connecting to the remote computer. Make sure... Subscribe to RSS Feed Mark Topic as New Mark Topic as https://vox.veritas.com/t5/Backup-Exec/Agent-Update-Error-connecting-to-the-remote-registry-of-Server/td-p/396173 Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Error connecting to the remote computer. 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 Highlight Print Email to a Friend Report Inappropriate Content Hello, I can not install the Remote Agent Backup Exec 2010 R3 on https://vox.veritas.com/t5/Backup-Exec/Error-connecting-to-the-remote-computer-Make-sure-that-the/td-p/626777 Win Server 2008 R2 to backup Exchange 2010. Domain account with full administrator rights. The error is: Error connecting to the remote computer. Make sure that the computer is available, WMI is enabled and not blocked Windows Firewall.14 Firewall is turned off, antivirus is empty, the WMI service is enabled. Network access to server is have. I tried instal with local administrator account and gave all sorts of rights, but to no avail. Agent has been installed very good on the other server. Labels: 10.x and Earlier Agent for Microsoft Exchange Server Agents Backup and Recovery Backup Exec Troubleshooting Windows Server (2003-2008) 1 Kudo Reply 10 Replies Hi, Check out the TN CraigV Moderator Partner Trusted Advisor Accredited 04-29-2013 07:06 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi, Check out the TN below: http://www.symantec.com/business/support/index?page=content&id=TECH128062 Thanks! 0 Kudos Reply You can try doing a local pkh Moderator Trusted Advisor Certified 04-29-2013 07:03 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content You can try doing a local install of the remote agent. Go to the Agent directory under the BE installation directory and then copy
and greatly increased scalability for larger networks Learn more CommunitySupportProductsGFI http://www.gfi.com/support/products/Error-Connecting-to-remote-registry-failed-with-The-network-path-was-not-found-error-53-when-scanning-a-Windows-8-computer-with-GFI-EndPointSecurity ArchiverGFI EndPointSecurityGFI EventsManagerGFI FaxMakerGFI FaxMaker OnlineGFI LanGuardGFI MailEssentialsGFI WebMonitorProduct DocumentationProduct FeedbackContact supportContact usLog inGFI FaxMaker OnlineCustomer PortalPartner Portal Company ProductsGFI SecurityGFI LanGuardGFI WebMonitorGFI EventsManagerGFI EndPointSecurityGFI CommunicationsGFI MailEssentialsGFI ArchiverGFI FaxMakerGFI FaxMaker OnlineAll ProductsGFI WebMonitorGFI LanGuardGFI MailEssentialsGFI EventsManagerGFI ArchiverGFI EndPointSecurityGFI error connecting FaxMakerGFI FaxMaker OnlineCompanyCareersCareersWhy work at GFIPress centerIn the newsPress releasesBlogAbout usBrand PillarsAwardsCustomersLeadershipTrusted ExpertsContactWebcasts and eventsPartnersBecome a GFI PartnerGFI Partner Program: Frequently Asked QuestionsWhy Resell GFI?Find a distributorFind a resellerGFI Partner AreaGFI OEM PartnersGFI Technology PartnersDownloadsLanguagesEnglishDeutschEspañolFrançaisItalianoNederlands简体中文繁体中文Store Error: 'Connecting to remote error connecting to registry failed with: The network path was not found. (error 53)' when scanning a Windows 8 computer with GFI EndPointSecurity PROBLEM You receive the following error when scanning a Windows 8 computer with GFI EndPointSecurity: Connecting to remote registry failed with: The network path was not found. (error 53) This will display in the Devices list section for the scan under the Scanning tab. ENVIRONMENT GFI EndPointSecurity 2013 SR1 or later Windows 8 SOLUTION Scanning requires the Remote Registry service to be enabled. This service is not enabled by default on Windows 8. To enable this service on the target computer: Open the Start screen Type services.msc and press Enter Find the Remote Reg