Err Msg: Unable to Initialize Windows Sockets...

Last reviewed: September 9, 1996
Article ID: Q131353
The information in this article applies to:
  • Microsoft Windows for Workgroups version 3.11
  • Microsoft TCP/IP-32 for Windows for Workgroups, version 3.11a

SYMPTOMS

When using one of the Microsoft TCP/IP-32 command line utilities (PING.EXE, FTP.EXE, etc.), the following error message appears:

   Unable to initialize Windows Sockets interface, error code 0

CAUSE

This error occurs when WSOCK.386 is corrupted or not loaded in memory.

RESOLUTION

To correct this problem perform the following steps:

   1. Remove the TCP/IP protocol using the Network Setup icon.

   2. Exit Windows for Workgroups. From the command prompt, change to the
      Windows System subdirectory.

   3. Rename the file WSOCK.386 by typing the following command:

         REN WSOCK.386 WSOCK.BAD

   4. Restart your computer and start Windows for Workgroups. Re-add the
      TCP/IP protocol using the Network Setup icon and directing Setup to
      the location of your TCP/IP-32 files. Remove the TCP/IP protocol from
      Network Setup and then reinstall it. Answer "Yes to All" to replace
      existing files.

For more information on downloading the TCP/IP-32, see the Knowledge Base article:

   Article :Q99891
   Title   :How to Obtain TCP/IP-32 3.11b for Windows for Workgroups


KBCategory: kbnetwork kberrmsg
KBSubcategory: nttcp
Additional reference words: 3.11 3.11a wfwg msnets netutils ndis3.x



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: September 9, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.