Quick Beginnings

Configuring NetBIOS on the Client

This section assumes that NetBIOS is functional on the client and DB2 Connect server workstations. See "Software Requirements" for the communication protocol requirements for your platform. See "Possible Client-to-DB2 Connect Gateway Connectivity Scenarios" for the supported communication protocols for your particular client and server.

The following steps are required to set up a client to use NetBIOS communications:

Identify and record parameter values.
Configure the client:
1. Record the network route for the Logical adapter number.
2. Update the database manager configuration file.
3. Catalog the NetBIOS node.
4. Catalog the database.
Test the connection between the client and server.

Step 1. Identify and Record Parameter Values

As you proceed through the configuration steps, complete the Your Value column in the following table. You can fill in some of the values before you start configuring this protocol.

Table 35. NetBIOS Values Required at the Client

Parameter Description Sample Value Your Value
Logical adapter number (Adapter_number)
The logical network adapters that will be used for the NetBIOS connection.
0
Workstation name (nname) - on the client The NetBIOS name of the client workstation.
nname is chosen by the user and must be unique among all NetBIOS nodes in the network.
client1
Workstation name (nname) - on the server
The NetBIOS name of the server workstation.
Locate this parameter in the database manager configuration file on the server.
server1
Node name (Node_name)
A local alias, or nickname, that describes the DB2 Connect server to the node where the database resides. You can choose any name you want, however, all Node name values within your local node directory must be unique.
db2node

Parameter	Description	Sample Value
Logical adapter number (`Adapter_number`)	The logical network adapters that will be used for the NetBIOS connection.	`0`
Workstation name (`nname`) - on the client	The NetBIOS name of the client workstation. `nname` is chosen by the user and must be unique among all NetBIOS nodes in the network.	`client1`
Workstation name (`nname`) - on the server	The NetBIOS name of the server workstation. Locate this parameter in the database manager configuration file on the server.	`server1`
Node name (`Node_name`)	A local alias, or nickname, that describes the DB2 Connect server to the node where the database resides. You can choose any name you want, however, all Node name values within your local node directory must be unique.	`db2node`

Step 2. Configure the Client

The following steps describe how to configure this protocol on the client. Replace the sample values with your worksheet values.

A. Record the Logical Adapter Number Used for the NetBIOS Connection

To view and record the Logical adapter number (Adapter_number) used for the NetBIOS connection, perform the following:

For OS/2:
1. Double-click on the MPTS icon.
2. Click on the Configure push button.
3. Select the LAN adapters and protocols radio button and click on the Configure push button.
4. Record the Logical adapter number associated with the IBM OS/2 NETBIOS entry in the Current Configuration window.
5. Click on the Cancel push button.
6. Click on the Close push button.
7. Click on the Exit push button.
For Windows 3.x
Record the Logical adapter number 0. If you experience problems making your NetBIOS connection, refer to the Troubleshooting Guide.

For Windows 95:

There is no interface on the Windows 95 operating system that you can use to record the adapter number used for the NetBIOS connection. Complete the following steps to have the NetBIOS protocol default to use the adapter number 0.

Click on the Start button and select Settings->Control Panel.
Double-click on the Network icon.
Select NetBEUI from The following Network components are installed window.
Click on the Properties push button.
Select the Advanced tab.
Select the Set this protocol to be the default check box.
Click on OK to exit this window.
Click on OK.
Record the value 0 as the Logical adapter number on your worksheet.
Shut down and reboot your system for these changes to take effect.

For Windows NT:

The Logical adapter number (Adapter_number) that you use must be associated with the Nbf Network Route for a native NetBIOS operation.
1. Click on the Start button and select Settings->Control Panel.
2. Double-click on the Network icon and select the Services tab.
3. Select the NetBIOS Interface option from the Network Services window and click on the Properties push button.
4. Scroll through the network routes until you find the logical adapter number associated with Nbf and record it on your worksheet.
5. Click on OK.
6. Click on the Close push button.

B. Update the Database Manager Configuration File

You must update the database manager configuration file with the client's workstation name (nname) parameter.

To update the database manager configuration file, perform the following steps:

Log on to the system as a user with System Administrative (SYSADM) authority.

If you have trouble logging on to the system, see "Logging on to the System".
Update the database manager configuration file with the client's Workstation name (nname) parameter using the following commands in the command line processor:
```
   update database manager configuration using nname nname
   terminate
```
For example, if the client's workstation name (nname) is client1, use:
```
   update database manager configuration using nname client1
   terminate
```

C. Catalog the NetBIOS Node

You must add an entry to the client's node directory to describe the remote node.

This entry specifies the chosen alias (Node_name), the remote server's Workstation name (nname), and the Logical adapter number (Adapter_number) that are to be used to access the remote DB2 server.

To catalog the NetBIOS node, perform the following steps:

Log on to the system as a user with System Administrative (SYSADM) or System Controller (SYSCTRL) authority.

If you have trouble logging on to the system, see "Logging on to the System".

If you are configuring communications for a Windows 3.x client, you can use the Client Setup tool to complete this task. Go to "Using the Client Setup Tool to Configure a Windows 3.x Client" to catalog a node using the Client Setup tool.

Catalog the node by issuing the following commands in the command line processor:
```
   catalog netbios node Node_name remote nname adapter Adapter_number
   terminate
```
For example, to catalog a remote database server server1 on the node called db2node, using the Logical adapter number 0, use:
```
   catalog netbios node db2node remote server1 adapter 0
   terminate
```

If you need to change values that were set with the catalog node command, first run the uncatalog node command in the command line processor as follows:

   uncatalog node Node_name

Recatalog the node with the value that you want to use.

D. Catalog the Database

Before a client application can access a remote database, the database must be cataloged on the server node and on any client nodes that will connect to it. When you create a database, it is automatically cataloged on the server with the Database alias (Database_alias) the same as the Database name (Database_name). The information in the database directory, along with the information in the node directory, is used on the client to establish a connection to the remote database.

To catalog a database on the client, perform the following steps.

Log on to the system as a user with System Administrative (SYSADM) or System Controller (SYSCTRL) authority.

If you have trouble logging on to the system, see "Logging on to the System".

Fill in the Your Value column in the following worksheet.

Table 36. Parameter Values for Cataloging Databases

Parameter Description Sample Value Your Value
Database name (Database_name) The Database alias (Database_alias) of the remote database. When you create a database, it is automatically cataloged on the server with the Database alias name (Database_alias) the same as the Database name (Database_name). sample
Database alias (Database_alias) An arbitrary local nickname for the remote database, on the client. If you do not provide one, the default is the same as the Database name (Database_name). This is the name that you use when connecting to a database from a client. tor1
Node name (Node_name) The name of the node directory entry that describes where the database resides. Use the same value for Node name (Node_name) that you used to catalog the node in the previous step. db2node

If you are configuring communications for a Windows 3.x client, you can use the Client Setup tool to complete this task. Go to "Using the Client Setup Tool to Configure a Windows 3.x Client" to catalog a database node using the Client Setup tool.

Parameter	Description	Sample Value
Database name (`Database_name`)	The Database alias (`Database_alias`) of the remote database. When you create a database, it is automatically cataloged on the server with the Database alias name (Database_alias) the same as the Database name (Database_name).	`sample`
Database alias (`Database_alias`)	An arbitrary local nickname for the remote database, on the client. If you do not provide one, the default is the same as the Database name (`Database_name`). This is the name that you use when connecting to a database from a client.	`tor1`
`Node name (Node_name)`	The name of the node directory entry that describes where the database resides. Use the same value for Node name (`Node_name`) that you used to catalog the node in the previous step.	`db2node`

Catalog the database by issuing the following commands in the command line processor:

   catalog database Database_name as Database_alias at node Node_name
   terminate

For example, to catalog a remote database called sample so that it has the alias tor1, on the node db2node, use:

   catalog database sample as tor1 at node db2node
   terminate

If you need to change values that were set with the catalog database command, first run the uncatalog database command in the command line processor as follows:

   uncatalog database Database_alias

Recatalog the database with the value that you want to use.

Step 3. Test the Client-to-DB2 Connect Server Connection

When the configuration of the server and client is complete, use the following steps to verify that you can access data from a remote database:

You will need to connect to a remote database to test the connection.

Start the database manager by issuing the db2start command on the server (if it was not automatically started at boot time).
Issue the following command in the client's Command Center or command line processor to connect the client to the remote database:
```
   connect to Database_alias user userid using password
```

The values for userid and password must be valid for the system on which they are authenticated. Authentication for connecting to host databases is set while configuring the DB2 Connect server. Refer to the DB2 Connect User's Guide for more information.

If the connection is successful, you will get a message showing the name of the database to which you have connected. You are now able to retrieve data from that database. For example, to retrieve a list of all the table names listed in the system catalog table, enter the following SQL command in the Command Center or command line processor:

   "select tabname from syscat.tables" (for UNIX-based platforms)
   select tabname from syscat.tables   (for other platforms)

When you are finished using the database connection, issue the connect reset command to end the database connection.

You are ready to start using the DB2 server. See Chapter 35. "Getting Started with the DB2 Universal Database" for details.

Troubleshooting the Client-to-Server Connection

If the connection fails, check the following items:

At the server:

The DB2COMM registry parameter includes the value netbios.

Check the settings for the DB2COMM registry value by issuing the db2set DB2COMM command. For more information, see Chapter 39. "Controlling Your DB2 Environment".
The Logical adapter number is equal to 0 (or the db2nbadapters registry value was updated to override the default value).
The server's Workstation name (nname) parameter was updated correctly in the database manager configuration file (or the admin server configuration file, if you are setting up the Administration Server).
The network route associated with the Logical adapter number is Nbf-for Windows NT servers only.
The database was created and cataloged properly.
The database manager was stopped and started (issue the db2stop and db2start commands on the server).

If there are problems starting a protocol's connection managers, a warning message is displayed and the error messages are logged in the db2diag.log file. The location of this file depends on your operating system.

UNIX-based Platforms: $HOME/sqllib/db2dump directory, where $HOME is home directory of the instance owner.
Other Platforms: x:\sqllib\%db2instance% directory, where x: is the drive that the client is installed and %db2instance% represents the DB2 instance.

Refer to the Troubleshooting Guide for information on the db2diag.log file.

At the client:

The client's Workstation name (nname) parameter was updated correctly in the database manager configuration file
The node was cataloged with the correct server's Workstation name (nname) and Logical adapter number (Adapter_number)
The Node name (Node_name), specified in the database directory, points to the correct entry in the node directory.
The database was cataloged properly, using the server's Database alias (Database_alias) that was cataloged when the database was created on the server, as the Database name (Database_name) on the client.

After you verify these items, refer to the Troubleshooting Guide if the connection still fails.

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]