Observed Versus Described Behavior of P-NODE Name Resolution

 Last reviewed: September 11, 1997
Article ID: Q140473
The information in this article applies to:
  • Microsoft Windows NT Workstation versions 3.5 and 3.51
  • Microsoft Windows NT Server versions 3.5 and 3.51
  • Microsoft LAN Manager version 2.2c
  • Microsoft TCP/IP-32 for Windows for Workgroups versions 3.11, 3.11a, and 3.11b

SUMMARY

When you use Network Monitor to determine Node type, you may come to an invalid conclusion, if the assumption is made that any P-NODE client will not issue a broadcast for NetBIOS name resolution. This also applies to H- NODE detection in some cases.

MORE INFORMATION

The following is an excerpt from a White Paper on TCP/IP implementation, TCPIPIMP.DOC, available for download from CIS or the Microsoft FTP server.

NodeType Key: Netbt\Parameters Value Type: REG_DWORD - Number Valid Range: 1,2,4,8 (b-node, p-node, m-node, h-node) Default: 1 or 8 based on the WINS server configuration

Description: This parameter determines what methods NetBT will use to register and resolve names. A b-node system uses broadcasts. A p-node system uses only point-to-point name queries to a name server (WINS). An m- node system broadcasts first, then queries the name server. An h-node system queries the name server first, then broadcasts. Resolution via LMHOSTS and/or DNS, if enabled, will follow these methods. If this key is present it will override the DhcpNodeType key. If neither key is present, the system defaults to b-node if there are no WINS servers configured for the client. The system defaults to h-node if there is at least one WINS server configured.

The described behavior of the p-node client is correct unless the internet group name associated with type 1C is returned from the WINS server or if a LMHOSTS file has a 0 (zero) entry for broadcast. In these cases a single broadcast will be observed from the client. This does not effect network operation and causes no problems. A single broadcast from a client will not adversely affect network operations.

This is expected behavior as an internet address of all zeros is used to address the network as a whole.

Additional query words:
Keywords : nttcp wfw wfwg kbnetwork
Version : 2.20c 3.11 3.11a 3.11b 3.50 3.51
Platform : WINDOWS

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.

Last reviewed: September 11, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.