The NetBIOS scope identifier is an optional string of characters that identify different logical NetBIOS networks that run on the same physical TCP/IP network.
In most configurations the NetBIOS scope identifier does not need to be changed. The simplest way to configure NetBIOS is to use a single logical network. If you think that you need to use the scope identifier, make sure you fully understand the implications of changing it before doing anything. If you do change the identifier, you should list all the NetBIOS nodes in your network and keep a record of which scope identifier is assigned to which node.
Keeping track of all the scope identifiers in a NetBIOS network can be complicated and time consuming. Avoid using this feature unless you have a very specific need for it.
Before setting the value of the scope identifier, check its value on the other machines in the network. If you have MS-DOS or OS/2 workstations on the network, the NetBIOS scope identifier should be set to NULL on all machines on the network. Many implementations of NetBIOS for TCP/IP allow you to use only the NULL scope identifier. If you have any other AFPS-compatible machines on the network, check their documentation for restrictions.
The scope identifier's setting depends on the implementation of TCP/IP. SCO TCP/IP sets the scope identifier with the NB_SCOPE parameter in the file /etc/inet/nb.conf. A typical example of the scope identifier's syntax would be: