Sockets.exe Required for Internet Explorer with 16-Bit TCP/IP

Last reviewed: May 19, 1997
Article ID: Q159693

The information in this article applies to:

Microsoft Internet Explorer versions 2.0, 2.01, 2.1, 3.0, 3.01, 3.02a for Windows 3.1

SYMPTOMS

When you attempt to start any of the Microsoft Internet Explorer for Windows 3.1 versions listed above on a Windows or Windows for Workgroups version 3.1 or 3.11-based computer that is running the 16-bit version of the Microsoft TCP/IP protocol, the following error message may be displayed:

   Winsock API Initialization Error

   The DOS Sockets TSR is not loaded.

If you are using Internet Explorer version 2.1 for Windows 3.1, the following error message is displayed when you click OK:

   The program could not initialize the network. Make sure your network
   connection is configured correctly. You can still view local files.

When you click OK again, Internet Explorer continues starting, but you are unable to access Web pages on the Internet. If you are using any other version of Internet Explorer for Windows 3.1 listed above, Internet Explorer continues starting when you click OK after the first error message is displayed, but you are unable to access Web pages on the Internet.

CAUSE

This problem can occur when the Sockets.exe program has not been started. To use Internet Explorer for Windows 3.1 with the 16-bit version of the Microsoft TCP/IP protocol, you must start Sockets.exe before starting Internet Explorer.

RESOLUTION

To work around this problem, follow these steps:

Verify that the TCP/IP protocol is installed properly. To do so, consult the documentation included with the version of the TCP/IP protocol you are running or see the following article in the Microsoft Knowledge Base:

      ARTICLE-ID: Q93736
      TITLE     : Enabling the Microsoft TCP/IP Protocol with WFWG 3.1

Use any text editor (such as Notepad) to open the Autoexec.bat file.

Insert the following line after the lines that load the TCP/IP protocol

      c:\<folder>\sockets.exe

where <folder> is the folder in which the TCP/IP protocol files are installed.

Save and then close the Autoexec.bat file.

Restart your computer. If an error message is displayed when the line in the Autoexec.bat file that contains Sockets.exe is processed, please see the following article in the Microsoft Knowledge Base:
```
      ARTICLE-ID: Q129986
      TITLE     : Error Using Microsoft Network Client SOCKETS.EXE
```

KBCategory: kbnetwork kbenv kberrmsg
KBSubcategory: msiew31msnets ndis2
Additional reference words: 2.00 2.01 2.10 3.00
Keywords : ndis2 kbenv kberrmsg kbnetwork
Version : 2.0 2.01 2.10 3.0 3.01 3.02a
Platform : WINDOWS

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: May 19, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.