Home > Cannot Connect > Cannot Connect On Socket 25 Veritas Netbackup

Cannot Connect On Socket 25 Veritas Netbackup

Contents

Hope this will shed some light on the issue. 0 Kudos Reply Contact Privacy Policy Terms & Conditions Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare On the client server to test whether the bpcd binary is executable and will generate a log issue the following command: UNIX: netbackup/bin/bpcd Windows program files\VERITAS\netbackup\bin\bpcd This will generate Thanks 0 Kudos Reply After making the hosts file epsilon22222 Level 4 ‎01-31-2013 05:31 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend I will post logs below. news

No Yes Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Veritas.com Support Communities Go to Solution bptestbpcd: EXIT status = 25 cannot connect on socket MaykelF0209 Level 3 ‎01-30-2013 01:51 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email Error Message Exit Status 25 - cannot connect on socket. No Yes Did this article save you the trouble of contacting technical support? https://www.veritas.com/support/en_US/article.TECH141839

Netbackup Error 25 Cannot Connect On Socket

Veritas does not guarantee the accuracy regarding the completeness of the translation. Other servers are communicating ok with the media server. This command does the following: The client retrieves the first server listed in it's server's list (this should be the master server) does a forward lookup of that hostname with 'gethostbyname

in case anything else is blocking communications 0 Kudos Reply Thanks for the replies guy. What might be blocking the socket connection? If the forward lookup fails or the client does not have the bprd port 13720 defined (in the registry for Windows clients or in /etc/services for UNIX clients) this message is Bptestbpcd Cannot Connect On Socket After pressing enter it goes show nothing n comes back to comman prompt again...

in /etc/hosts.allow) Windows 2008 clients may have the Domain Firewall, Private Firewall, and Public Firewall turned on. Netbackup Cannot Connect On Socket Linux Can you ping the server? CALL US: 1 (866) 837-4827 Solutions Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government Products Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z Services Education Services Business Critical Go to Solution.

Just simply click apply and OK to commit those changes.   If unable to resolve this issue, place a call to Symantec Technical Support for NetBackup for help in troubleshooting this Bppllist -l Cannot Connect On Socket (25) It is possible that updates have been made to the original version after this document was translated and published. 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 to client properties and double client the same server it shows (25) cannot connect to socket.

Netbackup Cannot Connect On Socket Linux

Is the NB client running on the new client? Either disable these firewalls in Windows firewall properties. Netbackup Error 25 Cannot Connect On Socket Email Address (Optional) Your feedback has been submitted successfully! Netbackup Cannot Connect On Socket 25 Windows I'm running 7.5 M4 Thanks 0 Kudos Reply I wonder, do you have the epsilon22222 Level 4 ‎01-31-2013 08:07 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight

There isn't a seperate backup network. navigate to this website Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? In-depth Troubleshooting Guide for Exit Status Code 25 in NetBackup (tm) Server / NetBackup Enterpr... 0 Kudos Reply can you ping \ telnet the server rj_nbu Level 6 Employee Accredited Certified net.jpg ‏31 KB 0 Kudos Reply « Previous 1 2 Next » Contact Privacy Policy Terms & Conditions Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Netbackup Error 58 Can't Connect To Client

Sorry, we couldn't post your feedback right now, please try again later. Step 8: If the client had been working at NBU 5.x release but now fails after upgrading to NBU 6.x, you can try using 5.x defaults for the client connection to Hosts entries? More about the author No Yes Did this article save you the trouble of contacting technical support?

To be checked in your case: Please check vnetd logs for IPC Sting port during the backup and also find via "netstat -a -o" to know which 'non-netbackup' process is trying Bptestbpcd Main: Function Connecttobpcd Failed: 25 Can you ping MOIMOI Level 4 ‎08-06-2009 11:22 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content hi Rajeev, 1. is displayed.

Labels: 7.1.x and Earlier Backing Up Backup and Recovery Configuring Error messages Monitoring NetBackup Troubleshooting 1 Kudo Reply 1 Solution Accepted Solutions Accepted Solution!

The bprd log on the master server shows the incoming connection and the attempt to connect to the client using the client host properties. Thank You! Abby 0 Kudos Reply Enabeling logs Venkatesh_K Level 5 ‎08-10-2009 12:34 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Error Code 25 In Netbackup Further information Eamonn Level 3 ‎06-01-2011 01:13 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content So Iran one of

It is possible that updates have been made to the original version after this document was translated and published. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? I will MaykelF0209 Level 3 ‎01-31-2013 06:00 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content I did not try click site Step 6: Locally on the client create a bpcd log and increase the verbose level to 5.

Sorry, we couldn't post your feedback right now, please try again later. As soon as I switch Daemon connection port back to default we go back to the job failing. Attachment Products Subscribe to Article Search Survey Did this article answer your question or resolve your issue? If any of these telnet tests fails to generate a log entry then there is something outside of NBU that is preventing access to the client's port.

Step 3: If the master server can not connect to the client when trying to access the client host properties, below are steps you can take to further troubleshoot this issue: May be some errors in common in the details, but that doesn't mean the same solution would apply. 0 Kudos Reply both are from the same RamNagalla Moderator Partner Trusted Advisor No Yes Menu Close Search SOLUTIONS Solutions Overview Unstructured Data Growth Multi-Vendor Hybrid Cloud Healthcare Government PRODUCTS Product Overview Backup and Recovery Business Continuity Storage Management Information Governance Products A-Z SERVICES All i did is the normal procedures that i do to all my other servers but this one is not able to connect.

Consider the below scenario where bpbrm wants to fork bpbkar in client.