Cannot Connect On Socket Error 25 Netbackup
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success netbackup cannot connect on socket linux 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 bptestbpcd cannot connect on socket Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Unable to connect to a NetBackup client. Exit Status 25 - cannot connect on socket. netbackup error 58 can't connect to client Article:000008360 Publish: Article URL:http://www.veritas.com/docs/000008360 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 subscription. Close Sign In Print Article Products Article Languages
Bppllist -l Cannot Connect On Socket (25)
Subscribe to this Article Manage your Subscriptions Problem Unable to connect to a 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 lo
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 bptestbpcd main: function connecttobpcd failed: 25 Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact error code 25 in netbackup Us English 中文(简体) English Français Deutsch Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet Status
Netbackup Error 25 Cannot Connect On Socket Windows 2008
Code 25: Cannot connect on socket when trying to open 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 https://www.veritas.com/support/en_US/article.000008360 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 When trying to open the Netbackup Client properties from Master https://www.veritas.com/support/en_US/article.000012138 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 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 "
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success https://www.veritas.com/support/en_US/article.000007335 Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange Investor Relations Careers Legal Contact Us English 中文(简体) English Français Deutsch http://fixunix.com/veritas-net-backup/481379-cannot-connect-socket.html Italiano 日本語 한국어 Português Español USA Site: Veritas Veritas PartnerNet GENERAL ERROR: Cannot connect to socket (25) and Backup fails with Status code 58: Can't cannot connect 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 subscription. Close Sign In Print Article cannot connect on 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:
- Veritas Net Backup ; We have Veritas NetBackup 5.1 running on a window 2000 Server. Problem started when we migrated our servers to private IP address. It is not connecting to a client, which is Redhat Linux 7.2 kernel 2.4.7-10. When I try to ... Forum Technology Forums Veritas Veritas Net Backup Cannot connect on socket + Reply to Thread Results 1 to 5 of 5 Thread: Cannot connect on socket LinkBack LinkBack URL About LinkBacks Bookmark & Share Digg this Thread!Add Thread to del.icio.usBookmark in TechnoratiTweet this thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Cannot connect on socket We have Veritas NetBackup 5.1 running on a window 2000 Server. Problem started when we migrated our servers to private IP address. It is not connecting to a client, which is Redhat Linux 7.2 kernel 2.4.7-10. 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. We have several other Linux clients. One of these is Red hat Linux 7.1. It works fine for all other clients. Any help will be appreciated. Thanks Re: Cannot connect on socket "Filbert Minj"