Table 9.1 NetBIOS Node Types
\r\nNode Type | Description |
---|---|
B-node (broadcast) | B-node uses broadcast NetBIOS name queries for name registration and resolution. B-node has two major problems: (1) Broadcasts disturb every node on the network. (2) Routers typically do not forward broadcasts, so only NetBIOS names on the local network can\r\nbe resolved. |
P-node (peer_peer) | P-node uses a NetBIOS name server, such as a WINS server, to resolve NetBIOS names. P-node does not use broadcasts; instead, it queries the name server directly. |
M-node (mixed) | M-node is a combination of B-node and P-node. By default, an M-node functions as a B-node. If an M-node is unable to resolve a name by broadcast, it queries a NetBIOS name server using\r\nP-node. |
H-node (hybrid) | H-node is a combination of P-node and B-node. By default, an H-node functions as a P-node. If an H-node is unable to resolve a name through the NetBIOS name server, it uses a broadcast to resolve the name. |
\r\nFrom [link|http://www.microsoft.com/mspress/books/sampchap/4245.asp#5|http://www.microsoft...mpchap/4245.asp#5]\r\n
\r\n\r\nI'm nobody's fool but mine, Ross :)\r\n