Text 113, 80 rader
Skriven 2006-08-02 10:57:48 av Mike Luther (1:117/3001.0)
Ärende: Help on multiple NIC's
==============================
The use of multiple NIC cards in an OS/2 PeerLAN operation box has been
discussed here way back when.  But I never got it working then because the site
was a remote site and I couldn't match up the discussion with trip after trip
for the research.

I'm back trying to solve this issue now and the target box to get it on is here
at the developement site.  So please, if anyone would be so kind to nurse me
through this.  The hardware is better now anyway.

I have an Intel 915GEVL mobo box up on MCP2 latest, all latest TCP/IP,MPTN and
PEER fixes.  It is working just fine with the on-board Intel 10/100 NIC chipset
and the latest Intel 10/100 drivers for OS/2.  This Intel motherboard is a
current production board with 4 PCI slots.  It also has the capability to
assign hard IRQ's to any of those 4 PCI slots.  And pending Vladest's finish of
the Uniaudio drivers for the on board Intel 880 audio chipset, two of the PCI
slots are occupied.  One,on IRQ 10, has the SBLive 5.1 card which works fine
with the RC1.14.1 Uniaudio code.  In another PCI slot is a US Robotics PCI
controller based modem hard on IRQ 5 and functioning as COM2 with this board.

The working Intel NIC is on IRQ 11,  I want to add a Kingston KT-120 NIC card
in a PCI slot which is hard set on IRQ 9. That to as best as possible eliminate
IRQ conflicts with things,

The standard configuration for the MPTS setup for just the Intel 10/100 NIC
setup comes out fine at the 100 speed with full duplex against a capable full
duplex switch for LAN and DHCP assignment via the router. In standard use, the
loaded modes for that 10/100 driver are IBM NETBIOS and IBM TCP/IP for it.  It
is set on LAN0 as part of the TCP/IP configuration and properly named as to the
HOSTNAME as part of the MPTS setup operations for OS/2.

In normal operations for my collection of things, I use PEER logon and normal
shared and connected operations for access box to box on the LAN. This is
properly handled as part of the NETBIOS settings in the MPTS setup as well.

But in this case, I want to use just this one new box for a dual purpose.  I
want to use it for DCHP connection via a router to the Internet, but connect it
to the local LAN and *NOT* allow the exposure to the local LAN to the Internet.
 I visualize that can be done by choosing to leave my WAN connectivity via
TCP/IP on only the on-board LAN0 Intel 10/100 chipset.  And then I propose to
use the second NIC in the PCI slot to communicate with the local LAN via
'standard' OS/2 NETBIOS.   And no, *NOT* as NETBIOS over TCP/IP, grin!

So I go in and remove the NETBIOS protocol in the MPTS setup from the LAN0
Intel 10/100 setup.  I then add the second NIC, the Kingston KT-120 unit as
LAN1 and set it up only for NETBIOS there.  Looking at the NETBIOS setup
parameters in that part of the MPTS configuration, I see that we are still set
up this way for the proper NETBIOS host name and so on.  Of course we reboot to
get things going in CONFIG.SYS.

Then I go in to the TCP/IP LOCAL setup via the desktop, the TCP/IP folder and
so on.  In it I leave the DHCP operation for the LAN0 interface enabled.  In
OS/2 it is only LAN0 which can use DHCP so I am taught.  And, when booted, the
box on TCP/IP only on that LAN0 is still working fine with a Linksys WRT-54GL
router connected to my cable service through DCHP for temporary test and
research addressing.

Then I go into the LAN1 interface and enable it.  I arbitrarily assign this
interface a non-used 192.168.1.## address with a net mask of 255.255.255.0 as
'normal'.  I reboot.

The boot run during CONFIG.SYS produces a LAN loader error.  If LAN0 does not
have IBM NETBIOS enabled on it we get the error.  With that we do not.  But if
I also enable IBM NETBIOS on LAN0, then the second NIC,the Kingston KT-120 card
is automatically given a new hostname!  If, for example, this box was 4041 as a
'hostname' to start with, suddenly the NETBIOS setup in MPTS will have a second
'hostname' of 40111 along with the original 'hostname' of 4011 of all things!

And in no case can the Kingston KT-120 NIC see the local LAN at all!  It can't
see any thing of a server to choose from to establish connections to when I go
in and look at connections with sharing and connecting.

What am I doing wrong?


--> Sleep well; OS/2's still awake! ;)

Mike @ 1:117/3001

--- Maximus/2 3.01
 * Origin: Ziplog Public Port (1:117/3001)