XCLN: Winsock Application Starts When Exchange Client Starts

 Last reviewed: September 23, 1997
Article ID: Q152344
The information in this article applies to:
  • Microsoft Exchange Windows 3.x client, versions 4.0 and 5.0
  • Microsoft Exchange Windows 95 client, versions 4.0 and 5.0

SYMPTOMS

When you install a Microsoft Exchange client for Windows 3.x on a computer that is running both the IPX/SPX and TCP/IP network protocols, even if you configure the Microsoft Exchange client to use just the IPX/SPX protocol, when you start the Microsoft Exchange client, it will make a call to Winsock.dll. This might cause a Winsock application to attempt to dial the modem that it is configured to use.

RESOLUTION

You can also remove the winsock application from the path statement.

MORE INFORMATION

Removing TCP/IP from the binding order will not resolve this problem.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Exchange version 4.0 Windows client. This problem was corrected in the latest Microsoft Exchange Server U.S. Service Pack. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces): 

   S E R V P A C K
If SP2 does not seem to fix this issue, you may need to add the following line to the MAPISVC.INF file to disable Winsock: 

   [MSEMS_MSMail_Section]
   66180003=01000000
To disable both Winsock and the IPX protocol, use this line: 

   [MSEMS_MSMail_Section]
   66180003=03000000
Once you add either of these lines, you will need to create a new profile with the original profile's settings.

Additional query words: tcp tcpip ip sockets autodial faq proxy
Keywords : kbbug4.00 kbfix4.00.sp2 XCLN kb3rdparty
Version : 4.0 5.0
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: September 23, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.