Knowledge Base

Windows Sockets GetHostByName() API Hangs Standard-Mode Windows

Article ID: 134345

Article Last Modified on 11/17/2003

Microsoft LAN Manager 2.2c, when used with:
- Microsoft MS-DOS 6.22 Standard Edition
Microsoft Windows 3.1 Standard Edition

This article was previously published under Q134345

SYMPTOMS

While you are running Windows 3.1 in Standard Mode, your computer reboots itself or Windows 3.1 hangs.

This problem occurs on your computer running LAN Manager for MS-DOS, version 2.2c with TCP/IP if Domain Name Resolver (DNR) is loaded and a program calls GetHostByName() or another Windows Sockets API that uses a callback function.

CAUSE

There is a problem in the Windows Sockets Standard Mode callback mechanism.

This code is central to the operation of many Windows Sockets APIs. Therefore, this problem affects all the "Get..." functions and other sockets functions including "Connect..." and "Accept..."

STATUS

Microsoft has confirmed this to be a problem in LAN Manager for MS-DOS, version 2.2c. A fix to this problem is in development, but has not been regression-tested and may be destabilizing in production environments. Microsoft does not recommend implementing this fix at this time. Contact Microsoft Product Support Services for more information on the availability of this fix.

Additional query words: prodlm 2.20c winsock

Keywords: KB134345