• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 3674
  • Last Modified:

win sock error 10053


I am getting 10053 error in my SAP 2008 server, after few minutes of idle condition connection is automatically disconnecting, plz help on this, how to resolve this issue.
0
ajitguptain
Asked:
ajitguptain
1 Solution
 
JAN PAKULAICT Infranstructure ManagerCommented:
have you tried to switch of your antivirus + firewall
also check system event which application caused Software connection abort.

you can try process explorer

http://technet.microsoft.com/en-us/sysinternals/bb896653

check that

http://www.sockets.com/err_lst1.htm#DetailedErrorDescriptions

WSAECONNABORTED (10053) Software caused connection abort.

Berkeley description: A connection abort was caused internal to your host machine. The software caused a connection abort because there is no space on the socket's queue and the socket cannot receive further connections.

WinSock description: Partly the same as Berkeley. The error can occur when the local network system aborts a connection. This would occur if WinSock aborts an established connection after data retransmission fails (receiver never acknowledges data sent on a datastream socket).

TCP/IP scenario: A connection will timeout if the local system doesn't receive an (ACK)nowledgement for data sent. It would also timeout if a (FIN)ish TCP packet is not ACK'd (and even if the FIN is ACK'd, it will eventually timeout if a FIN is not returned).

User suggestions: There are a number of things to check, that might help to identify why the failure occurred. Basically, you want to identify where the problem occurred.

Ping the remote host you were connected to. If it doesn't respond, it might be off-line or there may be a network problem along the way. If it does respond, then this problem might have been a transient one (so you can reconnect now), or the server application you were connected to might have terminated (so you might not be able to connect again).
Ping a local host to verify that your local network is still functioning (if on a serial connection, see next step)
Ping your local router address. If you're on a serial connection, your local router is the IP address of the host you initially logged onto with SLIP or PPP.
Ping a host on the same subnet as the host you were connected to (if you know one). This will verify that the destination network is functioning.
Try a "traceroute" to the host you were connected to. This won't reveal too much unless you know the router addresses at the remote end, but it might help to identify if the problem is somewhere along the way.

Jan MA CCNA
0
 
PenguinNCommented:
You could try to repair your winsock.

http://support.microsoft.com/kb/299357
0
 
ajitguptainAuthor Commented:
Nortel VPN client for windows 7 64 bit
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now