Microsoft KB Archive/247146

From BetaArchive Wiki
Knowledge Base

Article ID: 247146

Article Last Modified on 5/14/2007


  • Microsoft Windows 95
  • Microsoft Windows 98 Standard Edition

This article was previously published under Q247146


Although you can install the Microsoft Winsock Proxy (WSP) Client program without problems on a Windows 95-based or Windows 98-based client, 32-bit Winsock programs (such as Ping and Telnet) may not function properly.

Other programs that may be affected include, but are not limited to:

  • Microsoft Internet Explorer
  • Microsoft MSN Messenger Service
  • Microsoft Outlook
  • Microsoft Outlook Express


This behavior can occur if a 32-bit Winsock program is being loaded at system startup. This prevents the Winsock Proxy client installation from replacing the 32-bit Winsock file on the client.


  1. Uninstall the Winsock Proxy client if it is already installed by using the Add/Remove Programs tool in Control Panel. It may be necessary to manually remove the Winsock Proxy client. See the following Microsoft Knowledge Base article for more information:

    218482 Proxy: How to Manually Remove the Winsock Proxy Client

  2. Configure the client so that no Winsock programs are loaded during the startup process. If you do not know which program is starting, use the information in one of the following Microsoft Knowledge Base articles to determine which programs are loading during startup:

    192926 How to Perform Clean-Boot Troubleshooting for Windows 98

    243039 How to Perform a Clean Boot in Windows 95

  3. When the program is no longer being loaded at system startup, install the Winsock Proxy client from the proxy server share point (usually \\Servername\Mspclnt\Setup.exe or http://Servername/Msproxy).


WSP Client Setup replaces Winsock files based on the version of Winsock installed on the client. 32-bit Winsock programs that use the Wsock32.dll file and are loaded at system startup may prevent WSP Client Setup from replacing the file.

Clients that use Winsock version 2.0 or later are not affected by this issue.

Keywords: kbenv kbprb KB247146