Very Computer

So, I have set up this intranet with 2 PCs connected with a cat5 crossover
cable between 2 TRENDnet TE100-PCIA adapters (21143).  Both these machines
are able to boot multiple OS's.  The Slackware 7.1 installation detects
these cards (uses de4x5 driver) and asks me two simple Q's: 1) IP and 2)
Netmask for which I enter 192.168.42.x and 255.255.255.0, respectively.  
It automatically set up network, broadcast.  So, now I have these two
machines with static IP's 192.168.42.1 and 192.168.42.2.  They do
everything I want (ping, telnet, browses each others web server).

I do the same thing booting these machines with Win98. Same
addresses.  They ping each other, and see each other in their Net 'hoods.

The problem is that when I boot one as Linux and the other as Win98, they
can't even ping each other.

I've looked at several tutorials on the subject.  Most of these tutorials
include a lot of stuff I don't need so I omit them - like setting up
samba, masquerading.  I know I don't need Samba, and I'm pretty sure I
don't need masquerading, that is for providing internet access, right?

Some additional info:  I also boot Redhat 6.1 on one of these machines.  
It's install wanted to use the tulip driver for this card, but it didn't
work.  I cleared out the IRQ field, and then eth0 came up, but it didn't
talk to anything.  I changed to the de4x5 driver, and then it was able to
talk to Linux.

I guess the next thing I'll try, is the most up to date tulip driver, but
this looks a little hairy for me, so, I thought I'd post this to see if
anybody has a tip.

Thanks!

Even after your detailed description, it could be a lot of things.

Quote:>The problem is that when I boot one as Linux and the other as Win98, they
>can't even ping each other.

Are you sure the ip info is correct on both boxes? On linux you can
run ifconfig to get the info for each device.

Quote:>these cards (uses de4x5 driver) and asks me two simple Q's: 1) IP and 2)
>Netmask for which I enter 192.168.42.x and 255.255.255.0, respectively.  
>It automatically set up network, broadcast.  So, now I have these two
>machines with static IP's 192.168.42.1 and 192.168.42.2.  They do

Quote:>I have been trying to get a very simple network going for a few days,
>now.  This network is intended to allow my Win98 machine to talk to my
>Linux box.  The Linux box will simply provide stuff like telnet, http, and
>possibly ftp or database services.  It does NOT need to provide access to
>the internet, DNS, etc.

>So, I have set up this intranet with 2 PCs connected with a cat5 crossover
>cable between 2 TRENDnet TE100-PCIA adapters (21143).  Both these machines
>are able to boot multiple OS's.  The Slackware 7.1 installation detects
>these cards (uses de4x5 driver) and asks me two simple Q's: 1) IP and 2)
>Netmask for which I enter 192.168.42.x and 255.255.255.0, respectively.  
>It automatically set up network, broadcast.  So, now I have these two
>machines with static IP's 192.168.42.1 and 192.168.42.2.  They do
>everything I want (ping, telnet, browses each others web server).

>I do the same thing booting these machines with Win98. Same
>addresses.  They ping each other, and see each other in their Net 'hoods.

>The problem is that when I boot one as Linux and the other as Win98, they
>can't even ping each other.

>I've looked at several tutorials on the subject.  Most of these tutorials
>include a lot of stuff I don't need so I omit them - like setting up
>samba, masquerading.  I know I don't need Samba, and I'm pretty sure I
>don't need masquerading, that is for providing internet access, right?

>Some additional info:  I also boot Redhat 6.1 on one of these machines.  
>It's install wanted to use the tulip driver for this card, but it didn't
>work.  I cleared out the IRQ field, and then eth0 came up, but it didn't
>talk to anything.  I changed to the de4x5 driver, and then it was able to
>talk to Linux.

>I guess the next thing I'll try, is the most up to date tulip driver, but
>this looks a little hairy for me, so, I thought I'd post this to see if
>anybody has a tip.

>Thanks!

I had worked on this for days, trying things every which way.  Finally, I
broke down and posted to this newgroup.  About a half hour later I tried a
different driver and it worked fine!  I canceled my post, but apparently
too late!

The tulip driver that comes with Slackware 7.1 did the trick.  I didn't
think it would work, because I had actually tried another version of it
from a Redhat partition in this setup, and it failed (yes, there are 6
bootable partitions among these 2 computers).

So then, I figure I'll get the latest tulip driver, install it on my
Redhat partition, and it'll surely work, right?  Wrong!  As much as I'd
like to get to the bottom of all this, I'm too damn tired.  I've got
something that works.

Thanks again for all your time.