Netbackup Error Cannot Connect On Socket
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 netbackup cannot connect on socket linux on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible netbackup cannot connect on socket 25 windows matches as you type. Showing results for Search instead for Do you mean VOX : Backup and Recovery : NetBackup : error
Bppllist Cannot Connect On Socket 25
( Cannot Connect On Socket ) VOX : Backup and Recovery : NetBackup : error ( Cannot Connect On Socket ) Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this
Netbackup Cannot Connect To Client 58
Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution error ( Cannot Connect On Socket ) Vickie Level 6 07-26-2013 10:01 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hey Everybody, I was working on a Issue, The error ( Cannot Connect On Socket ) occurs while trying communicate a Client from Master server. Checked bptestbpcd cannot connect on socket BPCD logs and test the connectivity b/w client and master, which is not happening. Found that "Windows Firewall" service is running on the server. Now by disabling the Firewal this issue could get resolved. But my concern is ( as Firewall is used to protect the server from virus or any harmful objects ). Why we have to Disable it ? Why NBU connection failed when server is Behind firewll ? Why can not we take backup along with Firewall Enabled ? Solved! Go to Solution. Labels: Backing Up Backup and Recovery NetBackup Windows 8 1 Kudo Reply 1 Solution Accepted Solutions Accepted Solution! you can make a connection RamNagalla Moderator Partner Trusted Advisor Certified 07-26-2013 10:38 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content you can make a connection when firewall is on.. but you need to add the netbackup ports to the firewall excepsssion list..(1556,13782,13724) by default window firewall does not keep the ports in excepsssion list, becasue it does not know about it.. where ever there is any port requirement for any application that is the admin task to add them in excepstion list trun on the firewall.. add the ports in excepstion list and check
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer
Netbackup Cannot Connect On Socket 25 Solaris
Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate bptestbpcd main: function connecttobpcd failed: 25 Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français <16>bptestbpcd main: cannot connect on socket Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Status Code 25: Cannot connect on socket when trying to open the Netbackup Client https://vox.veritas.com/t5/NetBackup/error-Cannot-Connect-On-Socket/td-p/586049 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 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 https://www.veritas.com/support/en_US/article.000012138 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 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 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 Profile Corporate Leadership Newsroom Research Exchange Investor https://www.veritas.com/support/en_US/article.000008360 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 Sign In Remember me Forgot Password? Don't have a Veritas Account? Create a Veritas Account now! Welcome First Last Your Profile Logout cannot connect 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. For example, if an attempt is made to connect to the client from the Host Properties tree in the NetBackup Administration cannot connect on 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, 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 En