Windows for Workgroups (WFW) 3.11 Fails to Work with Remote Winsock Service (RWS) (172418)


The information in this article applies to:

  • Microsoft Proxy Server 1.0
This article was previously published under Q172418

SYMPTOMS

If you use Microsoft Windows for Workgroups (WFW) version 3.11 client with the Remote Winsock Service (RWS), you may get the following error message when you run Chkwsp16.exe from the Mspclnt share on the Proxy Server:
Failed to copy the configuration files.
NOTE: Use of the Web Proxy Service on the Proxy Server is still possible but all Winsock connections (for example, Telnet, SMTP, FTP, and other Winsock applications) fail.

CAUSE

When a Windows for Workgroups 3.11 client makes a universal naming convention (UNC) connection for the Remote Winsock Service, it needs to reserve a drive letter for that connection even though it does not use it. If the LastDrive statement in the Config.sys file on the WFW client is configured with a letter too near the beginning of the alphabet, and all available drive letters are used, then WFW may not have a drive letter available to reserve and will not make the connection.

WORKAROUND

Configure LastDrive=Z (or as close to the end of the alphabet as possible) in the Config.sys file for the WFW client.
Modification Type:MajorLast Reviewed:8/11/1999
Keywords:kbprb KB172418
©2002 Microsoft Corporation. All rights reserved.