Cannot Connect Socket Error 25
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer
Cannot Connect On Socket Netbackup Error
Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate netbackup cannot connect on socket 25 windows Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch
Netbackup Cannot Connect On Socket Linux
Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet STATUS CODE 25: Troubleshooting procedures for client Status 25 errors. Article:000009351 Publish: Article URL:http://www.veritas.com/docs/000009351 Support netbackup error 25 cannot connect on socket / 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 Print Article Products Related Articles Article Languages Subscribe to bptestbpcd cannot connect on socket this Article Manage your Subscriptions Problem The master server is getting a status code 25 (cannot connect on socket) error when attempting to bring up the client host properties using the GUI or remote admin console. Cause A status 25 error results from either a TCP SYN request sent to a client from the NetBackup server that was not acknowledged or the server was not resolvable so a TCP SYN request was not sent. The majority of the causes of this issue are due to the client not listening on the bpcd or vnetd ports, the master server failing to resolve the client by hostname, or the client can not resolve the NetBackup server by its IP address. For NetBackup clients running 6.x release, although the vnetd daemon is used for incoming connections, it is still required that bpcd perform the hostname compare to authenticate the NetBackup server. Solution Troubleshooting: Step 1:
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 Relations Careers Legal Contact Us English
Bppllist -l Cannot Connect On Socket (25)
中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet netbackup error 58 can't connect to client Status Code 25: Cannot connect on socket when trying to open the Netbackup Client properties from master server console. Article:000012138 Publish:
Bptestbpcd Main: Function Connecttobpcd Failed: 25
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 https://www.veritas.com/support/en_US/article.TECH141839 set up your subscription. Close Sign In 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 https://www.veritas.com/support/en_US/article.000012138 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 then click Next3. On the Protocol and Ports page (shown in Figure below), select the TCP protocol. Click Specific Local Ports, type in the numbers of the port 13782 and then click Next. 4. On the Action page, select the desired behavior, and then click Next.5. Select "Allow all the connection"6. On the Profile page, select the profiles to which the rule should apply, and then click Next.7. On the Name page, type a name and a description for the rule, and then click Finish.Create the Inbound port rules for port numbers 13782, 13724, 1556 also.Repeat the same procedure for creating the Outbound TCP port rules for the port numbers 13782, 13724, 1556 as well.Try telnet from the Master Server to the Client it should work.Try
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 https://www.veritas.com/support/en_US/article.000008360 Corporate Profile Corporate Leadership Newsroom Research Exchange Investor 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? cannot connect 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 Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem Unable to connect to a NetBackup client. Exit Status 25 - cannot cannot connect on connect on socket. For example, if an attempt is made to connect to the client from the Host Properties tree in the NetBackup Administration 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 docume