Configuring NetBios over TCP/IP with Warp Connect
courtney@timken.com


Assuming you've got IBM Peer working using NETBIOS over NETBEUI, here are
the steps I follow when adding support for NETBIOS over TCP/IP:

1.  Install TCP/IP if you don't already have it on the system.  You can use
    the "Warp Connect Install/Remove" function in the OS/2 System folder
    to accomplish this.

2.  From an OS/2 command line, or from the Workplace Shell, use MPTS.EXE
    to add the NETBIOS over IP protocol.
    a.  From MPTS's first screen, select "Configure" (not Install!)
    b.  Choose "LAN Adapters and Protocols" on the next screen, then go to
        the "Configure" button.
    c.  In the lower-left listbox, select your desired network adapter.  It
        should already be installed and the hardware settings configured.  Do
        not add a new adapter from the upper-left corner.
    d.  With the adapter highlighted, select "NETBIOS over TCP/IP" in the
        upper-right listbox and click on "Add" nearby.  You should see this
        protocol added to the lower-left listbox.
    e.  Single-click on the new protocol in the lower-left listbox and click
        "change number".  You can't have two NETBIOS protocols be the
        same logical adapter number.  If all the existing numbers are "0" you
        can make the new protocol "1".  Note:  It doesn't matter what the
        number is for TCP/IP itself...this setting only applies to NETBIOS
        type functions.
     f.  In the same listbox, click "Edit".  You'll see a dialog box with
         three radio buttons.  Set things up as shown below:
         f1.  Driver Parameters
              You'll see a LONG list of text entries.  Near the bottom is one
              that says "Maximum number of name-IP address pairs..." and
              defaults to zero.  Change it to a reasonable number, such as
              30.  This limits how many NETBIOS over IP devices you can
              connect to that are reached through an IP router.  E-mail me if
              you want a detailed explanation of this.
         f2.  Names List
              Use this dialog to map the NETBIOS computername to an IP
              address.  Only necessary for nodes that are NOT on your own
              IP subnet.  The entry in step "f1" above is the max number
              of items in this list, and the results of this step wind up in
              a file called RFCNAMES.LST.
         f3.  Broadcast List
              Add an entry of each IP broadcast address you want to use.
              For example, I connect to nodes in subnet 147.185.104.xxx,
              so my Broadcast List has 147.185.104.255.
         Save and exit this screen.
    g.  Back at the LAPS Configuration dialog where you added the
        new protocol, click OK to save and exit.  You'll return to the
        "Configure" dialog.  There is an option called "TCP/IP Socket
        Access" that says "Must configure".  Fortunately, all that is
        required to accomplish this is to click on the "Configure" button!
     h.  Click "Close" to save and exit this dialog.  Then exit from MPTS
        and let it make the changes it wishes to your CONFIG.SYS and
        PROTOCOL.INI files.
     i.  MPTS will tell you to shut down and reboot.  NOT NEEDED YET!

2.   Use OS/2 Peer install routine to "tell" Peer about the second logical adapter.

     a.  In the OS/2 Peer folder, choose the install program and run it.
     b.  You'll get a warning message that multiple adapters were detected
         but that you have to use MPTS to configure them.  No problem---
         you just finished that step.
     c.  Proceed through the OS/2 Peer installation...at each step, just tell
         it "OK" without changing anything.  Make sure both of your logical
         adapters are enabled.  ***CAUTION***  When it asks you if you
         want to reset "NET.ACC", tell it NO!!!  Otherwise you will reset
         your local admin password, user accounts, access lists, etc.  Yech!
         (However, if you ever forget your password, this is how to reset to
         the defaults without reinstalling...)
      d.  Save and exit.  Again, the install program will want to modify
          CONFIG.SYS and IBMLAN.INI...let it.
3.  Shut down and reboot.

With this configuration, OS/2 Peer will first try to reach the other node on
your NETBEUI network, and will use TCPBEUI only if that times out.  This
has the side effect of making initial connections (only) to TCP/IP nodes a
little slower, but once you have connected the speed is normal.

I have successfully used this configuration to communicate amongst the 
following node types, within and across subnets on a WAN:

OS/2 Peer (on Warp Connect)
Windows NT 3.5
DEC Pathworks 1.3g running on ULTRIX 4.3a
DEC Pathworks 5.0 running on Open/VMS

If you need further help, you are welcome to e-mail me as
"courtney@timken.com".
