The information in this article applies to:
SYMPTOMSWhen 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). CAUSEThe following keys were not updated during the upgrade process: WINS CLIENT (TCP/IP)HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\NETBT\CurrentVersion\MajorVersion HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\NETBT\CurrentVersion\MinorVersion NETBEUI ProtocolHKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\NBF\CurrentVersion\MajorVersion HKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\NBF\CurrentVersion\MinorVersion NWLink NetBIOSHKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\NwlnkNB\CurrentVersion \MajorVersion 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 TransportHKEY_LOCAL_MACHINE\SOFTWARE\MICROSOFT\NwlnkIpx\CurrentVersion \MajorVersion 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. RESOLUTIONUse 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:
MajorVersion:REG_DWORD:0x4 STATUSMicrosoft 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 : kbnetwork kbbug4.00 ntsetup NTSrvWkst |
Last Reviewed: January 29, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |