Netbackup 7.5 Error 25 Cannot Connect On Socket
Contents |
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
Netbackup Cannot Connect On Socket Linux
Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português netbackup cannot connect on socket 25 windows Español USA Site: Veritas Veritas PartnerNet STATUS CODE 25: Troubleshooting procedures for client Status 25 errors. Article:000009351 Publish: Article bppllist -l cannot connect on socket (25) 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 to Subscribe Please sign
Netbackup Error 58 Can't Connect To Client
in to set up your subscription. 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 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
Bptestbpcd Cannot Connect On Socket
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: When troubleshooting status 25 errors on a NetBackup client, verify that the client was working prior to the issue. If it had been working try to determine what changes may have been made to the client server's OS or the network links. 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. e.g. bptestbpcd -verbose -debug -client
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community bptestbpcd main: function connecttobpcd failed: 25 MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate
Error Code 25 In Netbackup
Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) netbackup cannot connect on socket 25 solaris English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet GENERAL ERROR: Cannot connect to socket (25) and Backup fails with https://www.veritas.com/support/en_US/article.TECH141839 Status code 58: Can't connect to client. 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 to Subscribe Please sign in to set up your https://www.veritas.com/support/en_US/article.000007335 subscription. 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 to client. Cause The problem turned out to be the Windows Firewall Service in Windows 2008 Server. Solution DETAILS:
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 https://www.veritas.com/support/en_US/article.000012138 English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Status Code 25: Cannot connect on socket when trying to open the Netbackup Client properties from master server console. Article:000012138 http://www.tek-tips.com/viewthread.cfm?qid=1567850 Publish: 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 cannot connect to 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 & cannot connect on 1556 are 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 Clie
FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. 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! Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. Symantec: NetBackup Forum at Tek-Tips HomeForumsServer RackBack-up SystemsSymantec: NetBackup Forum cannot connect on socket (25) thread776-1567850 Forum Search FAQs Links MVPs cannot connect on socket (25) cannot connect on socket (25) nortelneo (IS/IT--Management) (OP) 4 Sep 09 05:17 Hi,I've installed Netbackup Administration 6.0 and updated this to MP7, on a new updated Windows Server 2003 SP2 server. I have a Netapps filer with NDMP enabled and volumes defined. I've defined the Netapps as an NDMP host and the credentials are validated. But when I try to add this as a client, I receive the error 'cannot connect on socket (25)'. All the services, except for Device Manager are running. The netbackup server, the netapps, and a domain controller are in a seperate test vlan, part of the same domain. There are no firewalls active anywhere. I have added the Netapp under the firewall options in the Master and Media Server properties. I've already gone through the guides ( Configuring NDMP, Troubleshooting etc.) and have not found a solution. 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, from the client, can you telnet to port 13782 on the master?John RE: cannot connect on socket (25) nortelneo (IS/IT--Management) (OP) 4 Sep 09 17:05 Hi,Yes, I am able to ping in both cases. However, I am unable to telnet on port 13782. But, I've checked the settings on the Netapps and am not able to find any settings where any ports are blocked or a firewall is enabled. How can I check this?Thanks. RE: cannot connect on socket (25) nortelneo (IS/IT--M