Error message: 10053 software caused connection to abort (204594)



The information in this article applies to:

  • Microsoft Windows NT Workstation 4.0
  • Microsoft Windows NT Server 4.0

This article was previously published under Q204594

SYMPTOMS

When you attempt to browse an Internet site, the following error message may be displayed in the Web browser window:
Proxy Reports:
10053 Software caused connection abort

CAUSE

This error message can occur under any of the following circumstances:
  • The external Internet Protocol (IP) address is resolved by internal clients. This can occur if Windows Internet Naming Service (WINS) name resolution is used and the external network adapter has registered itself instead of the internal network adapter.
  • The client's IP address is not contained within the Local Address Table (LAT).
  • The Internet publishing server (destination server) is on a Microsoft Proxy server as well as the client that is trying to reach this server. This can occur if the Proxy server containing the publishing server does not have the Publishing option enabled. This option is disabled by default.
Note that "10053" is a generic WinSock error code that may be displayed for other reasons than those listed in this article.

RESOLUTION

To resolve the issue, use the appropriate method:
  • Delete the IP address entry that corresponds to the the Proxy server's external adapter, disable WINS support on the external adapter, and then reboot the server. To unbind the WINS client (TCP/IP) interface:
    1. In Control Panel, double-click Network.
    2. Click the Bindings tab.
    3. In the Show Bindings For box, click All Adapters.
    4. Expand all of the adapters.
    5. Click WINS Client (TCP/IP), and then click Disable.
    For additional information, please refer to the WINS documentation.

  • Add the IP address of the client receiving the error message to the LAT table on the Proxy server:
    1. Start the Internet Service Manager tool.
    2. Right-click Web Proxy, and then click Properties.
    3. Click Local Address Table.
    4. Add the appropriate range that contains the IP address of the client.
    5. Click OK.
    6. Click OK.
  • Test from the Proxy server itself or another from another client that is not behind a Proxy server to determine whether it is able to connect. If not, contact the administrator of the Publishing server and ask to have the Publishing option enabled on the Proxy server, which will allow incoming requests on port 80.

STATUS

This behavior is by design.

Modification Type:MajorLast Reviewed:4/3/2006
Keywords:kbenv kberrmsg kbprb KB204594