I have added the Netapp under the firewall options in the Master and Media Server properties. 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 the client had not been backed up for the last 10 days, am not sure before that. ... 14:44:59.975  <2> bpcd main: <---- NetBackup 6.5 0 ------------initiated 14:44:59.975  Why would telnet fail with Marianne Moderator Partner Trusted Advisor Accredited Certified 10-18-2015 06:10 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend check over here
Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Error : "Cannot connect to socket (25)"Backup fails with Status code 58: Can't connect All rights reserved.Unauthorized reproduction or linking forbidden without expressed written permission. RE: cannot connect on socket (25) nortelneo (IS/IT--Management) (OP) 9 Sep 09 01:06 Hi,A single server is used as the master and media server. The bpcd log shows status 98.The bptm log lists a message: mount_open_media: error requesting media, TpErrno = Requested number of drives are not configured.These error messages indicate a mismatch between the
Problem started when we migrated our servers to private IP address. This fixed the problem. When I try to load >properties of this client from Host properties in the main console it gives >the error message "scigate.ncsi.iisc.ernet.in cannot connect on socket". >The status code is 25.
Cause Examine the bpcd log from the client for evidence of the following 10:44:50.087  <2> bpcd main: setup_sockopts complete10:44:50.091  <8> bpcd peer_hostname: gethostbyaddr failed : HOST_NOT_FOUND (1)10:44:50.091  <16> Go to Solution. Veritas does not guarantee the accuracy regarding the completeness of the translation. Bppllist -l Cannot Connect On Socket (25) Sorry, we couldn't post your feedback right now, please try again later.
Note: When testing connections to bpcd note the delta time difference between the bpcd log message e.g. "16:52:46.077 [1160.5436] <2> logconnections: BPCD ACCEPT FROM 10.82.105.254.44554 TO 10.82.110.6.13782 " and the log Netbackup Cannot Connect On Socket 25 Windows Providing you the BPCD log file around that time. Email Address (Optional) Your feedback has been submitted successfully! It is not connecting >>to a client, which is Redhat Linux 7.2 kernel 2.4.7-10.
It is not connecting >>>to a client, which is Redhat Linux 7.2 kernel 2.4.7-10. Bptestbpcd Main: Function Connecttobpcd Failed: 25 Through GUI hostproperties too, it doesnt connect. Close Sign In Print Article Products Related Articles Article Languages Subscribe to this Article Manage your Subscriptions Problem Status Code 25: "Cannot connect on socket" occurs during restore Error Message RE: cannot connect on socket (25) santhas (TechnicalUser) 23 Sep 09 06:09 Hi,Have you setup NDMP credentials ( a valid user / password) and have you added the filers as NDMP
Thanks RE: cannot connect on socket (25) johngiggs (TechnicalUser) 4 Sep 09 16:10 nortelneo,Can you ping the master server from the client?Can you ping the client from the master?If that works, Step 5: Ensure the client server has the bpcd and vnetd port in listening mode using the command netstat -a: On Windows: TCP dotto:vnetd dotto.veritas.com:0 LISTENING TCP dotto:bpcd dotto.veritas.com:0 LISTENING Netbackup Cannot Connect On Socket Linux You should talk with network team, and OS team as well. Bptestbpcd Cannot Connect On Socket 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!
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 check my blog Thank You! Sorry, we couldn't post your feedback right now, please try again later. It is possible that updates have been made to the original version after this document was translated and published. Netbackup Error 58 Can't Connect To Client
https://www.veritas.com/support/en_US/article.TECH27430 there is a basic troubleshooting that i can find from the following links: https://www-secure.symantec.com/connect/forums/25-cannot-connect-socket-0 https://www-secure.symantec.com/connect/forums/25-cannot-connect-socket 0 Kudos Reply Accepted Solution! Problem >started >>>when we migrated our servers to private IP address. RE: cannot connect on socket (25) nortelneo (IS/IT--Management) (OP) 15 Sep 09 01:18 Hi Aix,NDMP protocol version 4. http://ebprovider.com/cannot-connect/cannot-connect-socket-error-netbackup.php Close Reply To This Thread Posting in the Tek-Tips forums is a member-only feature.
Step 4: A very useful command to help with testing client and server resolution is the command bpclntcmd -pn when run from a NBU client or media server. Error Code 25 In Netbackup Create/Manage Case QUESTIONS? e.g.
The source server may have the wrong target server name in its environment or an invalid/wrong IP address for the target server. 0 Kudos Reply Thanks everybody for your alisdad Level Most likely firewall software or a TCP wrapper was placed on the ports. I've defined the Netapps as an NDMP host and the credentials are validated. Netbackup Error 25 Cannot Connect On Socket Windows 2008 Sorry, we couldn't post your feedback right now, please try again later.
If you can't do that, then NB isn't going to work. Problem >started >>>when we migrated our servers to private IP address. When I try to load >>properties of this client from Host properties in the main console it gives >>the error message "scigate.ncsi.iisc.ernet.in cannot connect on socket". >>The status code is 25. have a peek at these guys Email Address (Optional) Your feedback has been submitted successfully!
Join UsClose Help Remember Me? If you run bptestbpcd with -verbose -debug, you will notice that 1st connection attempt is on PBX (1556), then vnetd (13724). The only workaround, this being a Windows client and no way to reset a port that I knew of, was to reboot. If this fails consult with your Network Administrator and client server System Administrator to resolve the layer 3 or IP network connectivity.Double check the server's NIC's IP address and netmask to
All these responses look ok. I've already gone through the guides ( Configuring NDMP, Troubleshooting etc.) and have not found a solution. OLD bpcd log from client that shows connection attempt from OLD master (udib02.my.company.com) is not going to help anybody. Sorry, we couldn't post your feedback right now, please try again later.
If you can't do that, then NB isn't going >to work. > > If that's successful, the problem could be that the client is no longer >able to authenticate the NB Register now while it's still free! Drive type: Open the NetBackup administration consoleExpand Media and Device ManagementSelect Devices. The right column indicates the device topology in the upper view, and the lower view lists all drives.The Device By joining you are opting in to receive e-mail.
You may also refer to the English Version of this knowledge base article for up-to-date information. Cancel Red Flag SubmittedThank you for helping keep Tek-Tips Forums free from inappropriate posts.The Tek-Tips staff will check this out and take appropriate action. 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 Advanced Search Cannot connect on socket - Veritas Net Backup This is a discussion on Cannot connect on socket - Veritas Net Backup ; We have Veritas NetBackup 5.1 running on