Home > Cannot Connect > Cannot Connect On Socket Netbackup 6.5

Cannot Connect On Socket Netbackup 6.5

Can you ping the server? Go to Solution Problems with backup, cannot connect on socket(25) Eamonn Level 3 ‎05-31-2011 02:28 PM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a You may also refer to the English Version of this knowledge base article for up-to-date information. All rights reserved.Unauthorized reproduction or linking forbidden without expressed written permission. news

As soon as I switch Daemon connection port back to default we go back to the job failing. Are you aComputer / IT professional?Join Tek-Tips Forums! Thanks. 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

Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Join UsClose Register now while it's still free! Handy NetBackup Links 0 Kudos Reply Sorry what I meant was I had Eamonn Level 3 ‎06-01-2011 08:47 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print

Attaching both files. Thank you both for the log commands, helped point me in the right direction, and find a work around until I get a solution in place. Please create bpcd log directory on client, then post output of the following commands: On client: bpclntcmd -self bpclntcmd -hn bpclntcmd -ip On media server: bpclntcmd -hn (use RE: cannot connect on socket (25) nortelneo (IS/IT--Management) (OP) 23 Sep 09 11:55 Hi santhas,Yes, the filers credentials are verified, and I have added it as NDMP host.

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 Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem The master server is getting a status code 25 (cannot connect on 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 https://vox.veritas.com/t5/NetBackup/25-Cannot-connect-to-Socket/td-p/253715 when i go to client properties and double client the same server it shows (25) cannot connect to socket.

You may also refer to the English Version of this knowledge base article for up-to-date information. And only one network card is used on this server as well as the Netapps. Or give me sometime, i’ll change few things and would post asap. Hope this will shed some light on the issue. 0 Kudos Reply Contact Privacy Policy Terms & Conditions Veritas.com Support Veritas Open Exchange Login or Join Communities Information Governance Backup and

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 Services Overview https://www.veritas.com/support/en_US/article.TECH141839 Resources Join | Indeed Jobs | Advertise Copyright © 1998-2016 ENGINEERING.com, Inc. 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 Step 6: Locally on the client create a bpcd log and increase the verbose level to 5.

As soon as I switch Daemon connection port back to default we go back to the job failing. http://electrictricycle.net/cannot-connect/cannot-connect-on-socket-25-netbackup-7-0-1.html 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 Showing results for  Search instead for  Do you mean  VOX : Backup and Recovery : NetBackup : Problems with backup, cannot connect on socket(25) VOX : Backup and Recovery : NetBackup What might be blocking the socket connection?

Article:000009351 Publish: Article URL:http://www.veritas.com/docs/000009351 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 Create/Manage Case QUESTIONS? I ran the bptestbpcd at around 14:39:55 and it ran till 14:45:07. http://electrictricycle.net/cannot-connect/cannot-connect-on-socket-netbackup.html Did you add separate hostnames for multiple NICs in hosts file on client itself?

Remove advertisements Sponsored Links m.d.ludwig View Public Profile Find all posts by m.d.ludwig « Previous Thread | Next Thread » Thread Tools Show Printable Version Email this Page Subscribe to 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 OLD bpcd log from client that shows connection attempt from OLD master (udib02.my.company.com) is not going to help anybody.

I've defined the Netapps as an NDMP host and the credentials are validated.

If it had been working try to determine what changes may have been made to the client server's OS or the network links. After pressing enter it goes show nothing n comes back to comman prompt again... No Yes How can we make this article more helpful? Veritas does not guarantee the accuracy regarding the completeness of the translation.

set loging level to 5 to get complete details since your saying ping telnet and host resolution is fine, if this is the newclient that is having problem try restarting NB It is possible that updates have been made to the original version after this document was translated and published. If you run bptestbpcd with -verbose -debug, you will notice that 1st connection attempt is on PBX (1556), then vnetd (13724). click site Would appreciate if it could be done without the logs cause they’re too big to change IPs and hostnames.

Does anyone know where the problem is? Go to Solution.