Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP 9000 Networking: Advanced Server/9000 Administrator's Guide > Chapter 7 AS/U in a Subnetted Domain

Manually Configuring NetBIOS Names

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

If an Advanced Server domain spans routers and does not use WINS, Advanced Server/9000 can operate in the domain that spans routers by manually populating the NetBIOS name caches on the Advanced Server/9000s. Every AS/U server in each subnet must have a name cache that contains the server names and IP addresses of every AS/U and NT Server within the domain that is on a different subnet. Also, the name cache must contain an entry for the domain name and IP address of each AS/U and NT server on different subnets. This is done using the nbutil utility. See Advanced Server/9000 subnetted domain example.

Advanced Server/9000 Access

To allow an Advanced Server/9000 to access another Advanced Server/9000 and/or NT Server in the same domain but on different subnets, manually add the Server name and Domain name with their corresponding IP address of the remote Advanced Server/9000 and NT Servers to the Advanced Server/9000 NetBIOS name cache.

Example in a Subnetted Domain:

This example illustrates how to properly configure a NetBIOS name cache on a Advanced Server/9000 to enable functionality in a subnetted domain.

The domain 'SUB_DOM' contains NT and Advanced Server/9000s on multiple subnets. The following servers are in 'SUB_DOM'

AS/U Server 'ASU_Serv1' is on subnet A. Its IP address is 200.1.1.1. AS/U Server 'ASU_Serv2' is on subnet B. Its IP address is 200.1.2.1. The NT Server 'NT_Serv3' is on subnet B. Its IP address is 200.1.2.2.

To manually populate the cache on ASU_Serv1, issue the following commands.

nbutil -a ASU_Serv2 -A 200.1.2.1 -V

nbutil -a NT_Serv3 -A 200.1.2.2 -V

nbutil -a SUB_DOM -A 200.1.2.1 -D

nbutil -a SUB_DOM -A 200.1.2.2 -D

To manually populate the cache on ASU_Serv2, issue the following commands.

nbutil -a ASU_Serv1 -A 200.1.1.1 -V

nbutil -a SUB_DOM -A 200.1.1.1 -D

You can also add entries to the Advanced Server/9000 NetBIOS name cache by editing the /etc/opt/lmu/netbios/nbhost file and executing nbutil -L to load the entries from the file to the cache.

NOTE: The location of the NetBIOS name cache was moved from /etc/opt//lmu/wanext/nbhost to /etc/opt/lmu/netbios/nbhost. When the name cache is loaded with the nbutil -L or when the name cached is saved with nbutil -S, the file /etc/opt/lmu/netbios/nbhost is used. Move any existing nbhost file to /etc/opt/lmu/netbios/nbhost.

Below are the /etc/opt/lmu/netbios/nbhost file entries of ASU_Serv1 and ASU_Serv2 in the above example:

/etc/opt/lmu/netbios/nbhost file on ASU_Serv1

ASU_Serv2 200.1.2.1 #SERVER NT_Serv3 200.1.2.2 #SERVER SUB_DOM 200.1.2.1 #DOM SUB_DOM 200.1.2.2 #DOM

/etc/opt/lmu/netbios/nbhost file on ASU_Serv2

ASU_Serv1 200.1.1.1 #SERVER SUB_DOM 200.1.1.1 #DOM

NOTE: Note: It is important to use the -V and -D options with nbutil or the #SERVER, and #DOM keywords in the nbhost file in order to correctly populate the name cache.

Non Advanced Server/9000 Access

To allow a Windows NT 3.51 Server, Windows NT 3.51 Workstation, LAN Manager 2.2c client, or a Windows 95 client to access Advanced Server/9000s in the same domain but on a different subnet you must use at least one of the access methods listed below:

  1. Enable WINS lookup on the client or NT Server and manually add each Advanced Server/9000 name and Domain name with their corresponding IP address into the database of the WINS server.

  2. Edit the client's or NT Server's lmhosts file to include each Advanced Server/9000's NetBIOS name and IP address with the #DOM:domain name option, that is, add the following line to the lmhosts file: 1.2.3.4 Server_name #PRE #DOM:Server_Dom

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 1997 Hewlett-Packard Development Company, L.P.