home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.microsoft.com
/
2002-07-02_ftp.microsoft.com.zip
/
peropsys
/
windows
/
public
/
tcpip
/
update.txt
< prev
Wrap
Text File
|
1994-11-23
|
8KB
|
196 lines
DOCUMENT:Q122544 23-NOV-1994 [PROTOCOL]
TITLE :README: TCP/IP-32 version 3.11a Update
PRODUCT :Cross Product Network Protocol Issues
PROD/VER:3.11a
OPER/SYS:WINDOWS
KEYWORDS:kbreadme kbfixlistTCP/IP-32a
----------------------------------------------------------------------
The information in this article applies to:
- Microsoft TCP/IP-32 version 3.11a
----------------------------------------------------------------------
The following is the complete README.TXT file that accompanies Microsoft's
TCP/IP-32 3.11a update.
---------------------------------------------------------------------------
Microsoft TCP/IP-32 version 3.11a Update
---------------------------------------------------------------------------
1.0 Introduction.
2.0 Installation Instructions for TCP/IP-32 version 3.11a.
2.1 List of Bugs Fixed in TCP/IP-32 3.11a.
2.2 Descriptions of Bugs Fixed in TCP/IP-32 3.11a.
1.0 Introduction
-----------------
TCP/IP-32 version 3.11a is an update to Microsoft's TCP/IP-32, a 32-bit
TCP/IP network protocol stack for Windows for Workgroups version 3.11. This
update is a complete refresh of TCP/IP-32 and contains all components of
the product.
2.0 Installation Instructions for TCP/IP-32 3.11a
--------------------------------------------------
There are two ways you can install the TCP/IP-32 version 3.11a upgrade on
your computer. You can completely reinstall your TCP/IP-32 network protocol
stack with TCP/IP-32 3.11a, 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.
Complete Reinstall:
1. From the Network group, choose the Network Setup icon.
2. Choose the Drivers button (Under Network Drivers, you will see your
Network Interface Card (NIC) and the network protocols used on that
NIC).
3. Select TCP/IP-32 3.11.
4. Choose the Setup button, review and write down all of your TCP/IP-32
configuration information.
5. Choose the Cancel button to return to the Network Drivers dialog box.
6. If TCP/IP-32 3.11 is your only network protocol, then temporarily add
the NetBEUI network protocol by following these steps:
A. Choose the Add Protocol button.
B. Select Microsoft NetBEUI.
C. Choose the OK button (Microsoft NetBEUI will appear under Network
Drivers).
7. Select TCP/IP-32 3.11.
8. Choose the Remove button and then the Yes button to confirm.
9. Choose the Add Protocol button.
10.Select Unlisted or Updated Protocol and Choose the OK button.
11.In the Install Driver dialog box, enter the path to the updated TCP/IP-
32 3.11a files (You should then see Microsoft TCP/IP-32 3.11a in the
Unlisted or Updated Protocol dialog).
12.Choose the OK button (You should then see Microsoft TCP/IP-32 3.11a in
the Network Drivers dialog box).
13.Choose the Setup button and configure TCP/IP-32 3.11a based on the
information you wrote down in step 4.
14.If you added Microsoft NetBEUI as a network protocol in step 6 and do
not want to keep it, select Microsoft NetBEUI, choose the Remove button
and then the Yes button to confirm.
15.Choose the Close button to exit the Network Divers dialog box.
16.Choose the OK button to exit the Network Setup dialog box (Setup will
modify system files).
17.Choose the OK button (Network Setup prompts you to reboot).
18.Choose the Restart Computer button (The TCP/IP-32 3.11a upgrade is now
complete).
Manual Installation for Advanced Users:
1. Copy the following files to the C:\<win_root> directory:
NOTE: By default, the Windows root directory referred to above is
C:\WINDOWS. If you installed Windows into a directory other than
C:\WINDOWS, copy these files to that directory.
11/21/94 12:00a 39,771 WINSOCK.DLL
11/21/94 12:00a 57,152 TELNET.EXE
11/21/94 12:00a 9,604 WSOCK.386
11/21/94 12:00a 53,935 TRACERT.EXE
11/21/94 12:00a 67,595 NETSTAT.EXE
11/21/94 12:00a 33,227 NBTSTAT.EXE
2. Copy the following files into the C:\<win_root>\SYSTEM directory:
11/21/94 12:00a 89,545 VNBT.386
11/21/94 12:00a 18,295 WSTCP.386
11/21/94 12:00a 9,604 WSOCK.386
2.1 List of Bugs Fixed TCP/IP-32 3.11a
---------------------------------------
NOTE: 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.
Q121317: TCP/IP-32 version 3.11 Does Not Include Terminal Font
Q120051: DNS Reverse Name Resolution Requests Are Incorrect
Q120052: NBT Query Can Hang Computer or Drop Back To MS-DOS
Q122293: LMHOSTS Lookup Can Cause Intermittent System Pauses
Q119575: TCP/IP-32 Winsock Stops FD_READ Notification
Q119918: Winsock: Accept() Sockets Are Unexpectedly Aborted
2.2 Description of Bugs Fixed in TCP/IP-32 3.11a
-------------------------------------------------
TCP/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.
Additional reference words: prodtcp32 1.00 3.11 3.11a wfw
KBCategory: kbreadme kbfixlistTCP/IP-32a
KBSubcategory: ntdistrib nttcp
=============================================================================
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.
Copyright Microsoft Corporation 1994.