Article ID: 122544 - View products that this article applies to.
This article was previously published under Q122544
The following text duplicates the Microsoft TCP/IP-32 for Windows for Workgroups version 3.11b UPDATE.TXT file. For information on how to obtain this TCP/IP-32 Update, query on the following word in the Microsoft Knowledge Base (without the spaces):
Microsoft TCP/IP-32 version 3.11b
2.0 Installation Instructions for TCP/IP-32 version 3.11b
2.1 List of Bugs Fixed in TCP/IP-32 3.11b
2.2 Descriptions of Bugs Fixed in TCP/IP-32 3.11b
3.0 More Information
1.0 IntroductionThe Microsoft TCP/IP-32 version 3.11b is the latest update to the TCP/IP-32 stack for Windows for Workgroups 3.11. It has been updated since version 3.11a and includes a number of fixes, primarily to provide compatibility with several third-party WinSock applications, and to correct problems with using DNS to resolve NetBIOS names. This also has updated code related to Windows 95. This update is a complete refresh of TCP/IP-32 and contains all components of the product.
This product is compatible with and supported exclusively on Windows for Workgroups version 3.11. If you are running a different TCP/IP product on your computer, you must remove it before installing Microsoft TCP/IP-32. If you experience difficulties with another vendor's product, remove the existing TCP/IP stack, exit Network Setup completely, reboot your system, and then proceed to add the Microsoft TCP/IP-32 drivers by following the instructions given in the documentation.
NOTE: When you upgrade to TCP/IP-32 3.11b, you should also update your Windows for Workgroups operating system with the files found on the Windows NT version 3.51 CD-ROM. This update is necessary to logon to a Windows NT domain over routers when using TCP/IP-32 3.11b. These files are also available on various electronic services in the self-extracting file, WFWFILES.EXE. For additional information, please see the following article in the Microsoft Knowledge Base:
(https://support.microsoft.com/kb/133255/EN-US/ )README.TXT: Windows for Workgroups Update Files
2.0 Installation Instructions for TCP/IP-32 3.11bThere are two ways you can install the TCP/IP-32 version 3.11b upgrade on your computer. You can completely reinstall your TCP/IP-32 network protocol stack with TCP/IP-32 3.11b, which will overwrite your previous TCP/IP settings with default settings. Alternatively, advanced users can manually copy just the updated binary files to the proper directories. This will retain your TCP/IP-32 settings, but will not update the TCP/IP-32 version number.
2.1 List of Bugs Fixed TCP/IP-32 3.11bNOTE: Use the Qxxxxxx number that precedes the title of the bug fix to query the Microsoft Knowledge Base to find an article about that bug.
(https://support.microsoft.com/kb/121317/EN-US/ )TCP/IP-32 version 3.11 Does Not Include Terminal Font
(https://support.microsoft.com/kb/120051/EN-US/ )DNS Reverse Name Resolution Requests Are Incorrect
(https://support.microsoft.com/kb/120052/EN-US/ )NBT Query Can Hang Computer or Drop Back To MS-DOS
(https://support.microsoft.com/kb/122293/EN-US/ )LMHOSTS Lookup Can Cause Intermittent System Pauses
(https://support.microsoft.com/kb/119575/EN-US/ )TCP/IP-32 Winsock Stops FD_READ Notification
(https://support.microsoft.com/kb/125486/EN-US/ )Ioctlsocket Function Returns Incorrect Data
(https://support.microsoft.com/kb/125437/EN-US/ )Winsock calls return WSAEINPROGRESS
(https://support.microsoft.com/kb/121619/EN-US/ )ARP Cache Commands May Not Work Correctly
(https://support.microsoft.com/kb/125963/EN-US/ )IPCONFIG Shows Leftover DHCP Parameters On Non-DHCP Clients
(https://support.microsoft.com/kb/128725/en-us/ )Domain Name Ignored by Windows for Workgroups with TCP/IP-32
2.2 Description of Bugs Fixed in TCP/IP-32 3.11bTCP/IP-32 version 3.11 Does Not Include Terminal Font:
Beta versions of Microsoft TCP/IP-32 included a font named "Terminal" in the Telnet application. This font is not included in the released version of the TCP/IP-32 Telnet application.DNS Reverse Name Resolution Requests Are Incorrect:
TCP/IP-32 does not return the correct IP name when it queries the Domain Name Service (DNS) because it sends an improperly formatted query to the DNS.NBT Query Can Hang Computer or Drop Back To MS-DOS:
Your computer running Windows for Workgroups version 3.11 with TCP/IP-32 network protocol stops responding (hangs) or drops back to MS-DOS when the 32-bit NetBIOS over TCP/IP (NBT) makes a query to the Domain Name Service (DNS).LMHOSTS Lookup Can Cause Intermittent System Pauses:
Your computer running Windows for Workgroups version 3.11 with TCP/IP-32 intermittently stops responding (hangs) for about 20 seconds at a time. This occurs if TCP/IP-32 is installed as a non-default network protocol and the Enable LMHOSTS Lookup option in Network Setup is checked.TCP/IP-32 Winsock Stops FD_READ Notification:
FD_READ notification in a Winsock application may stop while the application is running. This may cause data to be left in the input buffer, or, it may cause the application to hang. This occurs when the application disables and then re-enables FD_READ notification during a period of time while the Windows message queue is full.Winsock: Accept() Sockets Are Unexpectedly Aborted:
Occasionally, when you execute a PUT command from an FTP client, your session to the FTP server is aborted.Winsock calls return WSAEINPROGRESS
Windows Sockets applications running on Microsoft TCP/IP-32 may receive error 10036 (WSAEINPROGRESS). This problem occurs when applications process a large number of Windows Sockets calls.ARP Cache Commands May Not Work Correctly
ARP -S commands may not function correctly under Microsoft TCP/IP-32 when the arp cache is empty.IPCONFIG Shows Leftover DHCP Parameters On Non-DHCP Clients
If TCP/IP-32 client is configured to use DHCP and then is re-configured to not use DHCP, when the command "IPCONFIG /ALL" is executed, it will show old (DHCP supplied) values for certain parameters.Domain Name Ignored by Windows for Workgroups with TCP/IP-32
When a Dynamic Host Configuration Protocol(DHCP) client running TCP/IP-32 version 3.11 requests an IP address from a DHCP server, the IP address is received but the domain name is not recognized by the Windows for Workgroups client computer.
3.0 More InformationFor known problems and various support options, please read README.TXT that accompanies Microsoft's TCP/IP-32 3.11b update.
Article ID: 122544 - Last Review: October 10, 2003 - Revision: 2.0
Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.