To access a remote server through NetBIOS, you must first have installed and configured communication software for both the client and server workstations. See Software Requirements for the communication protocol requirements for your platform. See Possible Client-to-Server Connectivity Scenarios for the supported communication protocols for your particular client and server.
Before completing the steps in this section, be sure that you have completed the instructions in Setting the DB2COMM Registry Parameter.
The following steps are required to set up NetBIOS communications:
step 1. | Identify and record parameter values. |
step 2. | Configure the server:
|
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 19. NetBIOS Values Required at the Server
Parameter | Description | Sample Value | Your Value |
---|---|---|---|
Adapter number (adapter_number) |
The local logical adapters that will be used for the NetBIOS connection. The server uses adapter 0 if this parameter is not
configured.
| 0 | |
Workstation name (nname) |
The NetBIOS name of the server workstation. nname is a name, chosen by the user, which must be unique among all NetBIOS server nodes in the network. If you are using DB2 Enterprise - Extended Edition, ensure that the last 4 characters are unique among all NetBIOS server nodes in the network. For more information on workstation names, see Workstation Name (nname) Rules
| server1 |
The following steps describe how to configure this protocol on the server. Replace the sample values with your values and record them on your worksheet.
DB2 uses registry parameters to control its use of the
NetBIOS resources on the server. Use the db2nbadapters
registry parameter when you want to specify a value other than the default
Logical adapter number 0.
|
For the DB2 server, set the db2nbadapters parameter by entering the db2set db2nbadapters=adapter_number command. The adapter_number can be a list of adapter numbers separated by commas. For the Administration Server, set the db2nbadapters parameter by entering the db2set db2nbadapters=adapter_number -i DB2DAS00 command. The adapter_number can be a list of adapter numbers separated by commas. |
To view or modify the NetBIOS interface configuration, which maps network routes to adapter numbers, perform the following steps:
step 1. | Double-click on the MPTS icon. |
step 2. | Click on the Configure push button. |
step 3. | Select the LAN adapters and protocols radio button and click on the Configure push button. |
step 4. | Record the Logical adapter number associated with the IBM OS/2 NETBIOS entry in the Current Configuration window. |
step 5. | If you want to change the logical adapter number associated with NetBIOS, select the IBM OS/2 NetBIOS entry from the Current Configuration window and click on the Change number push button. |
step 6. | Select a logical adapter number and click on the Change push button. |
step 7. | Record the new logical adapter number associated with the IBM OS/2 NETBIOS entry in the Current Configuration window on your worksheet. |
step 8. | Click on OK. |
step 9. | Click on the Close push button. |
step 10. | Click on the Exit push button. |
step 11. | Ensure that the Update CONFIG.SYS check box is selected and click on the Exit push button. |
step 12. | Click on the Exit push button. |
step 13. | The Network Settings Change pop-up box opens. You must shutdown and reboot your system for these changes to take effect. Select the No push button to shutdown and reboot your system at a later time.
|
step 1. | Click on Start and select Settings->Control Panel. |
step 2. | Double-click on the Network icon and select the Services tab. |
step 3. | Select the NetBIOS Interface icon from the Network Services window and click on the Properties push button. |
step 4. | Scroll through the network routes until you find the Logical adapter number associated with Nbf and record it on your worksheet. If this adapter number is associated with Nbf, and you do not want to change it, go to step 7. |
step 5. | To change the logical adapter number associated with Nbf, select the associated Lan Number, and click on the Edit push button. Enter the new adapter number 0 or the value that you set for the db2nbadapters) registry variable. |
step 6. | Record the new adapter number associated with Nbf on your worksheet. |
Click on OK. | |
step 8. | Click on the Close push button. The Network Settings Change window opens. |
step 9. | You must shutdown and reboot your system for these changes to take effect. Select the Yes push button to shutdown and reboot your system or select the No push button to shutdown and reboot your system at a later time.
|
| Each adapter number must be uniquely associated with a network route. Windows NT has a built in checking facility that will not allow you to specify the same adapter number for different network routes. If a Network route already exists that is using the adapter number 0, assign a different number to that route. (The valid range for adapter numbers is 0 to 255.) This will allow you to select 0 as the adapter number that corresponds to Nbf. Approve the changes by clicking on OK. |
You must update the database manager configuration file with the server's Workstation name (nname) parameter.
To update the database manager configuration file, perform the following steps:
step 1. | Log on to the system as a user with System Administrative (SYSADM) authority. For more information, see Working with the System Administrative Group. |
step 2. | Update the database manager configuration file with the server's Workstation name (nname) parameter by entering the following commands: update database manager configuration using nname nname db2stop db2start For example, if the server's workstation name (nname) is server1, use: update database manager configuration using nname server1 db2stop db2start After the database manager is stopped and started again, view the database manager configuration file to ensure that these changes have taken effect. View the database manager configuration file by entering the following command: get database manager configuration If you are configuring the Administration Server for NetBIOS, you must update the admin server configuration file. Use the following command: update admin configuration using nname nname db2admin stop db2admin start
|
If your NetBIOS protocol was configured when you installed the server (or the instance-owning machine on DB2 Enterprise - Extended Edition), the setup program automatically created a NetBIOS dependency for the server and Administration Server. You will need to manually create a dependency on NetBIOS for any new instances.
To create this dependency, perform the following steps:
step 1. | Go to the x:\sqllib\misc directory, where x: is the drive on which the server was installed |
step 2. | Enter the db2depnb command as follows: db2depnb instance_name where instance_name is the name of the instance that you want to create a dependency for.
|
This records a dependency on the startup order which causes NetBIOS to
start before a DB2 instance starts.
|
If you remove the NetBIOS protocol from your network, you must remove the dependencies that were created during installation, and any dependencies that you created for additional instances. Failure to remove these dependencies may cause problems when running DB2 after the NetBIOS protocol has been removed from the network. To remove a dependency, enter the db2depnb command as follows: db2depnb instance_name /r where instance_name is the name of the instance for which you are
removing a dependency.
|