Article ID: 163837 - Last Review: November 1, 2006 - Revision: 1.1 SNMP Query to Windows NT Returns Same Value for NTS and NTWThis article was previously published under Q163837 SYMPTOMS
When you use an SNMP utility to obtain the system type from a computer
running Windows NT, the value returned is the same for both Windows NT
Server and Windows NT Workstation. The system types appear to be identical.
Because Windows NT workstations and servers have different capabilities, it is necessary to differentiate between these versions of Windows NT, especially when managing a large network. In addition, it is necessary to differentiate between Windows NT Servers and Domain Controllers, since they also have different roles in the domain model. CAUSE
The SysObjectID field (1.3.6.1.4.1.311.1.1.3.1) returned by the computer
running Windows NT is the same if the computer is running Windows NT Server
or Windows NT Workstation.
RESOLUTION
A change was made in Windows NT 4.0 Service Pack 2 (SP2) and Windows NT
3.51 post-SP5 to the SNMP components so that the different system types are
now reported as follows:
1.3.6.1.4.1.311.1.1.3.1.1 for Windows NT Workstation
This enables the user of the SNMP utility to more precisely identify the
type of Windows NT system.
1.3.6.1.4.1.311.1.1.3.1.2 for Windows NT Servers 1.3.6.1.4.1.311.1.1.3.1.3 for Windows NT Domain Controllers STATUS
Microsoft has confirmed this to be a problem in Microsoft Windows NT
version 4.0. This problem was corrected in the latest Microsoft Windows NT
4.0 U.S. Service Pack. For information on obtaining the service pack, query
on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K
Microsoft has confirmed this to be a problem in Windows NT version 3.51. A
supported fix is now available, but is not fully regression-tested and
should be applied only to systems experiencing this specific problem.
Unless you are severely impacted by this specific problem, Microsoft
recommends that you wait for the next Service Pack that contains this fix.
Contact Microsoft Product Support Services for more information.
| Article Translations
|

Back to the top
