Protocols Major and Minor Version Registry Keys Not Updated When Upgrading from 3.51 to 4.0
Article ID: 158980
Article Last Modified on 11/1/2006
APPLIES TO
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Server 4.0 Standard Edition
This article was previously published under Q158980
SYMPTOMS
When you use Srvinfo.exe that ships with the Windows NT 4.0 Resource Kit
against a server that was upgraded to Windows NT 4.0 from a previous
version of Windows NT, the protocols may be listed as being from the
previous version (even though they were upgraded to the Windows NT 4.0
version of those protocols).
CAUSE
The following keys were not updated during the upgrade process:
WINS CLIENT (TCP/IP)
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\NETBT\CurrentVersion\MajorVersi
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\NETBT\CurrentVersion\MinorVersiNETBEUI Protocol
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\NBF\CurrentVersion\MajorVersi
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\NBF\CurrentVersion\MinorVersiNWLink NetBIOS
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\NwlnkNB\CurrentVersion
\MajorVersi
NOTE: The above registry key is one path; it has been wrapped for
readability.
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\NwlnkNB\CurrentVersion
\MinorVersion
NOTE: The above registry key is one path; it has been wrapped for
readability.
NWLINK IPX/SPX Compatible Transport
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\NwlnkIpx\CurrentVersion
\MajorVersi
NOTE: The above registry key is one path; it has been wrapped for
readability.
HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\NwlnkIpx\CurrentVersion
\MinorVersion
NOTE: The above registry key is one path; it has been wrapped for
readability.
RESOLUTION
Use Registry Editor to change the MajorVersion from 3 to 4 and change
the MinorVersion from 51(decimal) to 0. To do this, perform the following
steps:
- Start Registry Editor (Regedt32.exe) and edit each of the earlier
protocol subkeys to the following:
MajorVersion:REG_DWORD:0x4
MinorVersion: REG_DWORD:0
- Quit Registry Editor and restart your computer.
STATUS
Microsoft has confirmed this to be a problem in Windows NT version 4.0. We
are researching this problem and will post new information here in the
Microsoft Knowledge Base as it becomes available.
Keywords: kbbug kbnetwork kbpending KB158980