Cannot Connect On Socket Netbackup Error
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 nbu cannot connect on socket Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español netbackup cannot connect on socket 25 windows USA Site: Veritas Veritas PartnerNet Status Code 25: Cannot connect on socket when trying to open the Netbackup Client properties netbackup cannot connect on socket linux from master server console. Article:000012138 Publish: Article URL:http://www.veritas.com/docs/000012138 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 bptestbpcd cannot connect on socket 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 When trying to open the Netbackup Client properties from Master Server Administrator console, getting Status Code 25 : Cannot connect on socket. Error Message Status Code 25: Cannot connect on socket Cause Windows Firewall was enabled on
Bppllist Cannot Connect On Socket 25
Windows 2008 R2 server and port numbers 13782, 13724 & 1556 are blocked due to windows firewall. Solution Check the bpclntcmd -ip, pn, -hn this works fine.Telnet working from Netbackup Client but does not work from Netbackup Master Server to NetBackup client for port numbers 13782, 13724We need to create the Inbound and Outbound port rules on the Windows 2008 R2 Netbackup Client. 1. In the Windows Firewall with Advanced Security console tree, select and then right-click Inbound Rules and click New Rule, click next.2. On the Rule Type page, click Port, and then click Next3. On the Protocol and Ports page (shown in Figure below), select the TCP protocol. Click Specific Local Ports, type in the numbers of the port 13782 and then click Next. 4. On the Action page, select the desired behavior, and then click Next.5. Select "Allow all the connection"6. On the Profile page, select the profiles to which the rule should apply, and then click Next.7. On the Name page, type a name and a description for the rule, and then click Finish.Create the Inbound port rules for port numbers 13782, 13724, 1556 also.Repeat the same procedure for creating th
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
Netbackup Error 25 Cannot Connect On Socket Windows 2008
Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us netbackup error 58 can't connect to client English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Unable to bptestbpcd main: function connecttobpcd failed: 25 connect to a NetBackup client. Exit Status 25 - cannot connect on socket. Article:000008360 Publish: Article URL:http://www.veritas.com/docs/000008360 Support / Article Sign In Remember me Forgot Password? Don't have a https://www.veritas.com/support/en_US/article.000012138 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 Unable to connect to a NetBackup client. Exit Status 25 - cannot connect on socket. https://www.veritas.com/support/en_US/article.000008360 For example, if an attempt is made to connect to the client from the Host Properties tree in the NetBackup Administration Console. Error Message Exit Status 25 - cannot connect on socket. Cause Examine the bpcd log from the client for evidence of the following 10:44:50.087 [9501] <2> bpcd main: setup_sockopts complete10:44:50.091 [9501] <8> bpcd peer_hostname: gethostbyaddr failed : HOST_NOT_FOUND (1)10:44:50.091 [9501] <16> bpcd peer_hostname: gethostbyaddr failed to return peer host, herrno = 110:44:50.091 [9501] <16> bpcd main: Couldn't get peer hostname Solution This condition is indicative of a problem with host name resolution via either DNS or the hosts file. Verify that the client's hostname resolves correctly to its IP address and that the reverse is true. That is, that the IP address reverse lookup corresponds to the client's hostname. Perform this verification on both the client and the master server. 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, andGovernance 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 https://vox.veritas.com/t5/NetBackup/Backup-server-cannot-connect-on-socket-unable-to-restore-files/td-p/520185 Sign In CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you https://www.experts-exchange.com/questions/25863586/netbackup-cannot-connect-on-socket-error.html type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : Backup server\cannot connect on socket\unable to r... VOX : Backup and cannot connect Recovery : NetBackup : Backup server\cannot connect on socket\unable to r... Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution Backup server\cannot connect on socket\unable to restore files with a NDMP policy type rhyden26 Level 3 Partner Accredited 02-04-2013 02:17 cannot connect on AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi Symantec Support, Please help to advise regarding the “(25) cannot connect on socket” issue on the NetApps backup policy. Due to this error, we are unable to restore files with a NDMP policy type. (phgclbps01ms0f3b and phgclbps01ms0f4b) We are in urgent need to restore files from NetApps, but we are failed to restore the files due to this problem. We have also tried your recommendation and did various isolation to resolve the issue but still the error persists. Appreciate your utmost support on this. Thank you in advance. Please contact me on this number(632) 792-5804. Regards, Rochelle Gonzales System Administrator ICT Infrastructure & Operations Group STMicroelectronics, Inc. - PTM Calamba cal.sysad3-ext@st.com Solved! Go to Solution. Labels: 7.1.x and Earlier Backing Up Backup and Recovery NetBackup Restore 1 Kudo Reply 1 Solution Accepted Solutions Accepted Solution! Thank you for clarifying that Andy_Welburn Moderator Trusted Advisor 02-05-2013 11:34 PM
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 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 > netbackup cannot connect on socket error Want to Advertise Here? Solved netbackup cannot connect on socket error Posted on 2010-04-13 Storage Software Storage 2 Verified Solutions 4 Comments 4,399 Views Last Modified: 2013-12-01 I am getting this error when I got clients and "connect' or "properties" I get "cannot connect on socket " I can connect to the server that has the netbackup server running on it , I am guessing the first thing would be to restart the sevices on the client or reboot , and then check to see if the ports are open for comuunitcation , anything else ? 0 Question by:NAMEWITHELD12 Facebook Twitter LinkedIn Google LVL 4 Best Solution byjeb If you have upgraded the clients you cant connect to, to a version higher than you backup server this will cause that to happen and will having the wrong master server name on the clients. if you have Go to Solution 4 Comments LVL 4 Overall: Level 4 Storage Software 2 Storage 1 Message Accepted Solution by:jeb2010-04-13 If you have upgraded the clients you cant connect to, to a version higher than you backup server this will cause that to happen and will having the wrong master server name on the clients. if you have reinstalled or moved the master server to a new box with a different name they wont connect. 0 LVL 1 Overall: Level 1 Message Active today Author Comment by:NAMEWITHELD122010-04-13 thanks , I will check this out when i get to work , I have no access from here , thanks again for the reply 0 LVL 31 Overall: Level 31 Storage Software 21 Storage 9 Message Assisted Solution by:Rodney Barnhardt2010-04-14 I have seen this before and restarting the system with the issue usually resolves the problem if there have been no changes to the configurations. Otherwise, you need to document any recent changes with your question. 0 LVL 1 Overall: Level 1 Message Active today Author Closing Comment