A problem, my TCP connection closes.

[Kim Andersen]

Hi.





I got a problem. I have a program that has a permanent TCP connection.
Sometimes the link is broken, and I got the error code to be:



10053 - WSAECONNABORTED



An established connection was aborted by the software in your host machine.





My program does not close the link at any time. The program runs under
Windows Server 2003 Std. with a 100Mbit link to a switch. What can the
problem be, and how to fully understand the error code.



Bad link to switch, damaged cable, wrong settings on the network card?



Kind regards

Kim

 

[Roland Hall]

: I got a problem. I have a program that has a permanent TCP connection.
: Sometimes the link is broken, and I got the error code to be:
: 10053 - WSAECONNABORTED
: An established connection was aborted by the software in your host
machine.
:
: My program does not close the link at any time. The program runs under
: Windows Server 2003 Std. with a 100Mbit link to a switch. What can the
: problem be, and how to fully understand the error code.
:
: Bad link to switch, damaged cable, wrong settings on the network card?

What are the duplex settings for the port on the switch and the NIC?

--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Online Support for IT Professionals -
http://support.microsoft.com/servicedesks/technet/default.asp?fr=0&sd=tech
How-to: Windows 2000 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308201
FAQ W2K/2K3 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;291382

 

[Kim Andersen]

: I got a problem. I have a program that has a permanent TCP connection.
: Sometimes the link is broken, and I got the error code to be:
: 10053 - WSAECONNABORTED
: An established connection was aborted by the software in your host
machine.
:
: My program does not close the link at any time. The program runs under
: Windows Server 2003 Std. with a 100Mbit link to a switch. What can the
: problem be, and how to fully understand the error code.
:
: Bad link to switch, damaged cable, wrong settings on the network card?

What are the duplex settings for the port on the switch and the NIC?

I have been told that the switch is set on 100Mbit Full Duplex, and I can
see that den computers NIC is set to auto.

Can that create an error 10053 - WSAECONNABORTED ?



I am in this situation that I cannot change the settings for the switch or
the computer. So I have to know if this error code is a result of wrong
configuration of switch settings or NIC settings.



/Kim

 

[Alexander Nickolov]

That means you received TCP RST packet from the other party.
This can happen for a variety of reasons... I suggest you install
a network sniffer (Ethereal for example) on both ends and follow
the conversation until your connection is aborted. The data just
prior to the RST may tell you something.

--
=====================================
Alexander Nickolov
Microsoft MVP [VC], MCSD
email: (e-mail address removed)
MVP VC FAQ: http://www.mvps.org/vcfaq
=====================================

 

[Roland Hall]

in message :
: : >
: > What are the duplex settings for the port on the switch and the NIC?
:
: I have been told that the switch is set on 100Mbit Full Duplex, and I can
: see that den computers NIC is set to auto.
:
: Can that create an error 10053 - WSAECONNABORTED ?
:
: I am in this situation that I cannot change the settings for the switch or
: the computer. So I have to know if this error code is a result of wrong
: configuration of switch settings or NIC settings.
:

It may not be either. It is an unknown at this point. However, you can get
disconnects from mismatched duplex settings, NIC drivers, latency,
bottlenecks, etc. As the other responder suggested, watching the
conversation at the packet level should help to determine the cause or at
least point you in a direction for further testing.

I've seen Cisco WS-C2924C switches send resets when the duplex is mismatched
and sometimes it requires auto at the NIC and the switch. If you do not
have a packet analyzer, you should verify the duplex on both ends and if at
all possible, set them at HD if they are currently at FD. If the switch is
auto and the NIC is FD, then I'd first set the NIC at FD. We have a lot of
moves with 1500+ users. More often than not a computer has moved that has a
HD setting and is now connected to a port set to FD.

Another issue could be the design of your network. If you're connecting too
many systems at 100/FD without being able to handle it on the backplane of
your switches, then you may experience disconnects/resets due to saturation.

--
Roland Hall
/* This information is distributed in the hope that it will be useful, but
without any warranty; without even the implied warranty of merchantability
or fitness for a particular purpose. */
Online Support for IT Professionals -
http://support.microsoft.com/servicedesks/technet/default.asp?fr=0&sd=tech
How-to: Windows 2000 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;308201
FAQ W2K/2K3 DNS:
http://support.microsoft.com/default.aspx?scid=kb;EN-US;291382