Netbackup 7.1 Error 25 Cannot Connect On Socket
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 netbackup cannot connect on socket linux Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français netbackup cannot connect on socket 25 windows Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Status Code 25: Cannot connect on socket when
Bppllist Cannot Connect On Socket 25
trying to open the Netbackup Client properties 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
Bptestbpcd Cannot Connect On Socket
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 When trying to open the Netbackup Client properties from Master Server Administrator console, getting Status Code 25 : Cannot connect on socket. netbackup cannot connect on socket 25 solaris Error Message Status Code 25: Cannot connect on socket Cause Windows Firewall was enabled on 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, t
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 helps you quickly
Bptestbpcd Main: Function Connecttobpcd Failed: 25
narrow down your search results by suggesting possible matches as you type. Showing results for <16>bptestbpcd main: cannot connect on socket Search instead for Do you mean VOX : Backup and Recovery : NetBackup : (25) Cannot connect to Socket VOX : Backup and server status cannot connect on socket rman Recovery : NetBackup : (25) Cannot connect to Socket Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page (25) Cannot connect to Socket MOIMOI https://www.veritas.com/support/en_US/article.000012138 Level 4 08-06-2009 12:36 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi All, I just added a server on my Netbackup Master Server and did the usual stuff like the pushing agent, host name etc etc... every thing is working fine...but when i add the server in the policy and try to add the folders it show cannot connect to client. when i go https://vox.veritas.com/t5/NetBackup/25-Cannot-connect-to-Socket/td-p/253715 to client properties and double client the same server it shows (25) cannot connect to socket. All i did is the normal procedures that i do to all my other servers but this one is not able to connect. What could be the problem Antivirus ?(i use the same AV for the other servers but it is working fine). What might be blocking the socket connection? i dont know how to check the logs for bpbrm and other logs.i also dont know how to configure those logs so that i can see the error for this particular server. Any ideas or suggesstions? Coz this is really strange problem i never faced before. Abby Labels: 7.1.x and Earlier Backup and Recovery NetBackup 1 Kudo Reply 27 Replies Have you checked all the usual Andy_Welburn Moderator Trusted Advisor 08-06-2009 12:46 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content name resolution checks, bpclntcmd, ping etc etc. Is the NB client running on the new client? Not sure of your NB version but the following probably cover the same things: In-depth Troubleshooting Guide for Exit Status Code 25 in Veritas NetBackup (tm) Server / NetBackup ... In-depth Troubleshooting Guide for Exit Status Code 25 in NetBackup (tm) Server / NetBackup Enterpr... 0 Kudos Reply can you ping \ telnet t
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 https://www.veritas.com/support/en_US/article.000008360 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 Unable to 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 cannot connect 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 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 cannot connect on to a NetBackup client. Exit Status 25 - cannot connect on socket. 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 informati