- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Socket error 10054
Operating System - HP-UX
1819876
Members
2593
Online
109607
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-20-2002 10:49 PM
08-20-2002 10:49 PM
Socket error 10054
hello,
lastly we have made a migration of 10.20 version to 11.00 and we are having problem with the application. when the user tries to be connected to the application this messages appears: "error SOCKET 10054"
I have been consulted information in the forum and I have seen a similar case in: http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xe25bc5ea0230d411ade80090279cd0f9,00.html
After I read this case I have changed in the regedit of the client and I have increased the tcp_rexmit_interval_max parameter to three minutes but we continue with the same problem.
Can you help me for solve this problem?
regards,
lastly we have made a migration of 10.20 version to 11.00 and we are having problem with the application. when the user tries to be connected to the application this messages appears: "error SOCKET 10054"
I have been consulted information in the forum and I have seen a similar case in: http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xe25bc5ea0230d411ade80090279cd0f9,00.html
After I read this case I have changed in the regedit of the client and I have increased the tcp_rexmit_interval_max parameter to three minutes but we continue with the same problem.
Can you help me for solve this problem?
regards,
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-21-2002 09:46 AM
08-21-2002 09:46 AM
Re: Socket error 10054
I saw your post on the referenced forum URL but there you say it happens when you switch to the backup node.
You would expect that to happen since the TCP/IP connection does not exist on the secondary machine so when it gets a packet addressed to a port on which it has no established connection it would have to send out a reset to tell the client that to start over.
If that's not the case and the problem occurs with a new session after the switch then you would look at
lanadmin
lan
display
for errors and other problems.
Make sure you have the same speed/duplex on both the HP and the switch and not autonegotiating.
netstat -a |grep x
where x is the port number it should be listening on to see if it's listening.
netstat -s to see if any errors are increasing.
Try to telnet to the port from the Window box.
Ron
You would expect that to happen since the TCP/IP connection does not exist on the secondary machine so when it gets a packet addressed to a port on which it has no established connection it would have to send out a reset to tell the client that to start over.
If that's not the case and the problem occurs with a new session after the switch then you would look at
lanadmin
lan
display
for errors and other problems.
Make sure you have the same speed/duplex on both the HP and the switch and not autonegotiating.
netstat -a |grep x
where x is the port number it should be listening on to see if it's listening.
netstat -s to see if any errors are increasing.
Try to telnet to the port from the Window box.
Ron
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Learn About
News and Events
Support
© Copyright 2025 Hewlett Packard Enterprise Development LP