NBT Manual

Installation and Configuration
NBT Manual—424773-001
2-5
NetBIOS Scopes
Thus a name request can be resolved via the lookup table, by a remote node responding
to a local broadcast, or remain unresolved. If unresolved, the NCB CALL or SEND
DATAGRAM is rejected with an indication that the remote name could not be found. If
resolved, NBT uses the resulting Internet address in the TCP CONNECT (for NCB
CALL) request. Compaq NonStop TCP/IP software handles the routing to local and
remote Internet networks.
NetBIOS Scopes
RFC1001 provides for partitioning of a network into logically separate scopes, with
each scope having a unique scope ID. NetBIOS nodes interoperate only with remote
nodes having identical scope IDs. This allows multiple groups of NetBIOS nodes to
operate simultaneously on the same Internet without interfering with each other.
The scope ID can be null, or it can be one or more names separated by periods.
RFC1001 implementations differ with respect to case sensitivity in scope IDs. Some
implementations, notably the Microsoft Windows For Workgroups, Microsoft Windows
NT, Microsoft Windows 98, and Microsoft Windows 95, are case-sensitive, treating
upper- and lower-case as unique. Most RFC1001 implementations are case-insensitive,
treating upper- and lower-case as equivalent. NBT can be configured to interoperate
with both types of remote nodes via the CASE field of the ADD DOMAIN command.
If possible, it is recommended to use the null scope ID. In NBT, this is done by using
SCOPE *NONE* on the ADD DOMAIN command. If a scope ID is used that is not
null, it is recommended to use all upper-case letters to ensure compatibility with case-
sensitive RFC1001 implementations.