[TriLUG] NAT / home network connectivity problem

[Robert Baker]

Have you tried downloading any NIC utilities from 3Com?  Set the NIC not to
auto-negotiate on the 95 box.  Set it to either 10 or 100 (whichever you are
using).

We had the same problems here on our 'mixed' speed Windows network.  Once we
changed the NIC to match our switches (100 Mbit) we stopped having
connection problems.  

>>> Rob Baker <<<
Webcentric Applications Developer

-----Original Message-----
From: Reginald Reed [mailto:reginald at cisco.com] 
Sent: Thursday, October 24, 2002 11:46 AM
To: trilug at trilug.org
Subject: RE: [TriLUG] NAT / home network connectivity problem


Ditto on this one too.  I think you can set the speed and duplex in the
network control panel for Win95.  I'd hardcode the settings for 100/full.

--Reggie

> -----Original Message-----
> From: trilug-admin at trilug.org
> [mailto:trilug-admin at trilug.org] On Behalf Of Jason Tower
> Sent: Thursday, October 24, 2002 10:29 AM
> To: trilug at trilug.org
> Subject: Re: [TriLUG] NAT / home network connectivity problem
> 
> 
> some 3Com cards have trouble with detecting the cable or
> negotiating the link 
> speed and/or duplex (one of my 3com NICs ran into this at the NCSU 
> installfest).  not sure if it's a linux kernel module issue 
> or a hardware 
> (but i'm inclined to say hardware).  supposedly there exists 
> a DOS utility 
> that can be used to change the bios setting on the nic 
> itself, that might 
> bring you some relief.  i'm sure cnet.com or mr. google can 
> help you find the 
> utility.
> 
> jason
> 
> On Thursday 24 October 2002 00:36, Alan Ellis wrote:
> > I have an old Dell Optiplex GXPro running RedHat 7.2.  It
> is doing IP
> > Masq / NAT for my family's Win95 machine.  Ethernet
> configuration is:
> > eth1: Linksys 10/100 LNE100TX v5.1 => cable modem
> > eth0: built-in 3c905 with 3c59x module => 192.168.0.1
> >
> > The win95 machine (192.168.0.2) has a 3com Fast Etherlink 10/100
> > Bus-Master PCI card.  This is connected directly to eth0 by 
> a 20-foot
> > crossover cable.
> >
> > Everything works *great* except that whenever we turn the win95
> > machine on the two machines can't even ping each other.  
> Consistently
> > I can solve the problem by unplugging the crossover cable from eth0
> > and plugging it back in, and then the win95 machine can see 
> both the
> > NAT server and the outside world.  Anybody know a better
> solution?  Or
> > where the problem is likely to be?
> >
> > Thanks!
> > --Alan
> >
> >
> > BTW (to follow up on an earlier thread) I did get Time
> Warner to come
> > install cable for RoadRunner.  I removed the hard drives
> temporarily
> > from my Linux box and swapped in a hard drive with Win98.  The tech
> > looked at this long enough to check system requirements (32MB RAM, 
> > 110MB free, and no conflicts in device manager) then handed 
> me the RR
> > software CD.  I shelved the CD, replaced the hard drives,
> and was in
> > business in minutes (though a little surprised when Linux knew the
> > hostname that had been recorded in Win98!).  Thanks again 
> to those who
> > advised this solution.
> >
> > _______________________________________________
> > TriLUG mailing list
> >     http://www.trilug.org/mailman/listinfo/trilug
> > TriLUG Organizational FAQ:
> >     http://www.trilug.org/~lovelace/faq/TriLUG-faq.html
> 
> --
> Jason Tower
> Cerient Technologies
> jason at cerient.net _______________________________________________
> TriLUG mailing list
>     http://www.trilug.org/mailman/listinfo/trilug
> TriLUG Organizational FAQ:
>     http://www.trilug.org/~lovelace/faq/TriLUG-faq.html
> 

_______________________________________________
TriLUG mailing list
    http://www.trilug.org/mailman/listinfo/trilug
TriLUG Organizational FAQ:
    http://www.trilug.org/~lovelace/faq/TriLUG-faq.html