Netbackup Error 25 Cannot Connect On Socket Windows 2008
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 cannot connect on socket 25 netbackup Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語
Netbackup Cannot Connect On Socket Linux
한국어 Português Español USA Site: Veritas Veritas PartnerNet Status Code 25: Cannot connect on socket when trying to open netbackup cannot connect on socket 25 windows the Netbackup Client properties from master server console. Article:000012138 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
Bppllist Cannot Connect On Socket 25
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 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 netbackup cannot connect to client 58 socket Cause Windows Firewall was enabled on Windows 2008 R2 server and port numbers 13782, 13724 & 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 por
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
Bptestbpcd Cannot Connect On Socket
Careers Legal Contact Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português
Bptestbpcd Main: Function Connecttobpcd Failed: 25
Español USA Site: Veritas Veritas PartnerNet GENERAL ERROR: Cannot connect to socket (25) and Backup fails with Status code 58: netbackup cannot connect on socket 25 solaris 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 https://www.veritas.com/support/en_US/article.000012138 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 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 https://www.veritas.com/support/en_US/article.000008360 ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations https://www.experts-exchange.com/questions/25863586/netbackup-cannot-connect-on-socket-error.html 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 cannot connect 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 Article Languages Subscribe to this Article Manage your Subscriptions Problem Unable to connect to a cannot connect on NetBackup client. Exit Status 25 - cannot 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.
for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Ask a Question Ask for Help Receive Real-Time Help Create a Freelance Project Hire for a Full Time Job Ways to Get Help Expand Search Submit Close Search Login Join Today Products BackProducts Gigs Live Careers Vendor Services Groups Website Testing Store Headlines Experts Exchange > Questions > netbackup cannot connect on socket error Want to Advertise Here? Solved netbackup cannot connect on socket error Posted on 2010-04-13 Storage Software Storage 2 Verified Solutions 4 Comments 4,423 Views Last Modified: 2013-12-01 I am getting this error when I got clients and "connect' or "properties" I get "cannot connect on socket " I can connect to the server that has the netbackup server running on it , I am guessing the first thing would be to restart the sevices on the client or reboot , and then check to see if the ports are open for comuunitcation , anything else ? 0 Question by:NAMEWITHELD12 Facebook Twitter LinkedIn Google LVL 4 Best Solution byjeb If you have upgraded the clients you cant connect to, to a version higher than you backup server this will cause that to happen and will having the wrong master server name on the clients. if you have Go to Solution 4 Comments LVL 4 Overall: Level 4 Storage Software 2 Storage 1 Message Accepted Solution by:jeb2010-04-13 If you have upgraded the clients you cant connect to, to a version higher than you backup server this will cause that to happen and will having the wrong master server name on the clients. if you have reinstalled or moved the master server to a new box with a different name they wont connect. 0 LVL 1 Overall: Level 1 Message Author Comment by:NAMEWITHELD122010-04-13 thanks , I will check this out when i get to work , I have no access from here