- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Dropped TCP/IP connection on Windows Client
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
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
Discussion Boards
Community
Resources
Forums
Blogs
- 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
05-13-2004 07:23 AM
05-13-2004 07:23 AM
Dropped TCP/IP connection on Windows Client
The client server application uses basic ICMP. The client opens the recieving endpoint of a socket, performs some transactions, goes to sleep for 20 minutes (waiting on an external event, not on a select) and then wakes up attempting to perform another transaction. WSAGetLastError() returns WSAECONNRESET on the client.
The server does believe the client has closed the socket. This occurs shortly after the client goes to sleep. I haven't debugged the server yet to determine the WinSock value.
Any ideas on the above?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2004 04:11 AM
05-14-2004 04:11 AM
Re: Dropped TCP/IP connection on Windows Client
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2004 04:33 AM
05-14-2004 04:33 AM
Re: Dropped TCP/IP connection on Windows Client
What is the server application? Does it have an inactivity timeout?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-14-2004 05:49 AM
05-14-2004 05:49 AM
Re: Dropped TCP/IP connection on Windows Client
The application does not make explicit ICMP calls.
The server application is Legato NetWorker. I am currently working with server engineers to determine the server timeout behavior. Its one of those cases where this use to work, but two customer escallations have appeared, both on GigE and large databases that would expose any changes in timeout behavior.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-08-2004 09:22 AM
06-08-2004 09:22 AM
Re: Dropped TCP/IP connection on Windows Client
Thomas
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-09-2004 04:44 AM - last edited on 09-16-2024 02:21 AM by support_s
06-09-2004 04:44 AM - last edited on 09-16-2024 02:21 AM by support_s
Re: Dropped TCP/IP connection on Windows Client
First and foremost, I ask you to contact Legato Technical Support about your issue.
Secondly, we have the following information from HP, and are working with the customer to determine the impact:
http://wwss1pro.compaq.com/support/reference_library/viewdocument.asp?
source=BU030627_CW01.xml&dt=3
http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?objectID=PSD_CO040408_CW01&locale=en_US.
Thanks,
Matthew Buchman
- Tags:
- bios