Home > Cannot Connect > Cannot Connect On Socket 25 Restore
Cannot Connect On Socket 25 Restore
No Yes How can we make this article more helpful? Consider the below scenario where bpbrm wants to fork bpbkar in client. 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 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 http://electrictricycle.net/cannot-connect/cannot-connect-on-socket-25-netbackup-restore.html
Looking further however I can't find anything connecting on the ports being requested in the vnetd log, so again I'm left with a puzzle of why this is failing on the Step 7: Test telnet from the master server to the client's bpcd port: telnet [client hostname] 13782 That should generate a log entry as seen below showing the master You may also refer to the English Version of this knowledge base article for up-to-date information. bptestbpcd -verbose -debug -client Note: See the Related Article linked below for additional details on use of the bptestbpcd command.
Cannot Connect On Socket 25 Netbackup
If it had been working try to determine what changes may have been made to the client server's OS or the network links. By joining you are opting in to receive e-mail. Now vnetd uses the "IPC STING" port to direct the connection to bpbrm. Abby 0 Kudos Reply hi Rajeev, 1.
Hosts entries? Netbackup Cannot Connect On Socket Linux Regards, Rochelle phgclbps01ms0f4b_log entries.txt 17 KB 0 Kudos Reply If it doesnt have a netbackup Mark_Solutions Moderator Partner Trusted Advisor Accredited Certified 02-05-2013 02:24 AM Options Mark as New Bookmark Exit Status 25 - cannot connect on socket. click After pressing enter it goes show nothing n comes back to comman prompt again...
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 <16>bptestbpcd Main: Cannot Connect On Socket HankHill Level 5 05-29-2013 08:32 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Error stopped, not sure why. 0 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 Solution Troubleshooting: Step 1: When troubleshooting status 25 errors on a NetBackup client, verify that the client was working prior to the issue.
Netbackup Cannot Connect On Socket Linux
Just my thoughts ..... Already a member? Cannot Connect On Socket 25 Netbackup Note the NetBackup daemon running and listening check and the bpps check in section three.On Windows, verify that the %SystemRoot%system32driversetcservices file has the correct entries for bpcd, bpdbm, and bprd.Also, verify Netbackup Cannot Connect On Socket 25 Windows So going by that article I'll needto identify the non-NetBackup process that is randomly connecting, as leaving the setting as Daemon port only is not a desired setup for us.
Appreciate your further analysis on this. navigate to this website You may also refer to the English Version of this knowledge base article for up-to-date information. 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 Reverse lookup enabled on DNS? Bptestbpcd Main: Function Connecttobpcd Failed: 25
Q1: Are you restoring to an equivalent device (NetApps filer) that has been fully configured within NetBackup? Or create exceptions for ports 13724, 13782, and exceptions, if necessary for Netbackup processes. Check what services the client is running for Windows clients (Try Turning off MS firewall software for a quick test) or check the hosts.allow and hosts.deny files on the UNIX clients http://electrictricycle.net/cannot-connect/cannot-connect-on-socket-netbackup-restore.html in /etc/hosts.allow) Windows 2008 clients may have the Domain Firewall, Private Firewall, and Public Firewall turned on.
Perform this verification on both the client and the master server. Netbackup Cannot Connect On Socket 25 Solaris Is the NB client running on the new client? Step 6: Locally on the client create a bpcd log and increase the verbose level to 5.
The restore will now initiate.
Sorry, we couldn't post your feedback right now, please try again later. Join your peers on the Internet's largest technical computer professional community.It's easy to join and it's free. Sorry, we couldn't post your feedback right now, please try again later. Bptestbpcd Cannot Connect On Socket If name resolution it exceeds that timeout then try using a host file entry to avoid DNS latency.
from the master server, run telnet Client_Name 13782 ...... The values on the Network tab are written to the services file when the NetBackup Client service starts.Also, see "Verifying Host Names and Services Entries" in the Troubleshooting Guide.4.On Sun Solaris, The bprd log on the master server shows the incoming connection and the attempt to connect to the client using the client host properties. click site To change the drive type: Double-click the drive nameFrom the Change Drive dialog box, select the correct drive type from the Drive Type pull down menu to match the media type
Create/Manage Case QUESTIONS? Most likely firewall software or a TCP wrapper was placed on the ports. Article:000007335 Publish: Article URL:http://www.veritas.com/docs/000007335 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 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
There isn't a seperate backup network. Go to Solution Cannot connect on socket(25) HankHill Level 5 02-28-2013 08:26 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Step 2: In 6.x and above environments you can use the command- bptestbpcd to verify you can connect to both the vnetd and bpcd ports on the client 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
Ensure the processes are listening on the appropriate ports. netstat -n -a [-p] | egrep '13724|13782' 7. Either disable these firewalls in Windows firewall properties. 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 All i did is the normal procedures that i do to all my other servers but this one is not able to connect.
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 RE: cannot connect on socket Gaskin69 (IS/IT--Management) (OP) 14 Jan 04 08:24 Master server (Netbackup 4.5 Datacenter) is Win 2k not Unix and it is on a SSO environment, it acts If these processes are not running, start them.