Text 47, 50 rader
Skriven 2006-04-29 16:35:00 av Mike Luther (1:117/3001.0)
     Kommentar till text 44 av Sean Dennis (1:18/200)
Ärende: Dual NIC problem
========================
Aha insight!

 PK> Just a wild guess here, but it sounds to me like 
 PK> it could be a problem
 PK> of an IRQ conflict, or an inabilty of a driver to 
 PK> share IRQ's. A good
 PK> test would be to try a diffent make/model of NIC for the second card
 PK> and see what happens.

 SD> I'd second that opinion-I've had that same problem 
 SD> before.  The same model seems to share IRQs.  I 
 SD> usually mix up my NICs (i.e. 3COM with a Davicom-based 
 SD> NIC) and that works nicely.

A while back I tried to set up a box at a client's site with two NIC's on MCP2
latest.  I never did get that to work there.  Subsequent to the work I learned
that the LAN0 NIC had to be the one on which DHCP was installed.  The LAN1 NIC
could then be used for something else, but not for anything that was concerned
with DCHP.

Well, looking back on this from fuzzy memory, I thought I'd tried that and it
still didn't work.  But suddenly now, I realize you are saying that what seems
to work is different NIC brands and drivers.  At the time I was trying this I
was using two Kingston KT-110 NIC PCI cards. And though I think I thought that
they were on two differnt IRQ's, you know I can't recall running PCI-Sniff to
look at this.    Hmmmm.

I still need to get this done.  The reason is we want one and only one box on
the LAN side of things to have access to the IP -- and all the rest of the LAN,
which also goes to this box, to be completely isolated from the IP side.

In this case a massive update of the target box has been done and it has been
completely re-furbished to an Intel 915GAV motherboard and has the 'standard'
LAN service operating just fine with the Intel PRO100 OS/2 drivers released
late last year.

So in a few weeks or so when I go to the site to try this again, I'll
substitute the PRO100 operation for the DSL and DHCP operation against the IP
service that is to be set up there.  Then I'll add one of the Kingston NIC
cards we use to that motherboard and use that one on pure OS/2 NETBIOS to
handle the LAN job for that side of the connection. Hopefully that will break
the log jam I hit the last time I tried this at the site!


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

Mike @ 1:117/3001

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