Here are the machines:
Linux machine: cyrix PR120/32M/1G/3c509 (going to cable modem)/linksys ne2000
compatable (home network)/Slackware 3.5 - this is my gateway for the...
Windoze machine: AMD 233/48M/2.5G/3c59x (used to go to cable modem)/linksys
ne2000 compatable (home network) /win95 with a small slackware install

This is the problem:  I can't ping either direction on my home network.

Here is the saga:
I recently (yesterday) upgraded the PR120 from a 486/66 and the operation went
flawlessly.  Except for the loss of my home network.  I can get on the internet
(obviously) and can ping loopback on both machines, so it appears that TCP/IP
is configured correctly.  I installed 2.0.35 just so I could be somewhat sure
that it wasn't a Linux software problem and I booted the win95 machine into
linux to see if it was a win95 problem.  Neither of these worked.  The cheesy
NIC diagnostic that came with the linksys says the cards are ok.
Here is what my ifconfig says: (192.168.0.1 -windoze)
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Bcast:127.255.255.255  Mask:255.0.0.0
          UP BROADCAST LOOPBACK RUNNING  MTU:3584  Metric:1
          RX packets:244 errors:0 dropped:0 overruns:0 frame:0
          TX packets:244 errors:0 dropped:0 overruns:0 carrier:0 coll:0

eth0      Link encap:Ethernet  HWaddr 00:40:05:4C:18:39
          inet addr:192.168.0.2  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:72 errors:0 dropped:0 overruns:0 carrier:0 coll:0
          Interrupt:9 Base address:0x320

eth1      Link encap:Ethernet  HWaddr 00:60:08:D1:4D:24
          inet addr:204.210.228.230  Bcast:204.210.228.255  Mask:255.255.255.0
          UP BROADCAST NOTRAILERS RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:754 errors:0 dropped:0 overruns:0 frame:0
          TX packets:563 errors:0 dropped:0 overruns:0 carrier:0 coll:1
          Interrupt:10 Base address:0x300

My last resort is to switch the mb back to the 486 and try to eliminate that
as a possible cause.  After that I am stumped.

Anybody have any idea what the problem might be or what else I can check?

Thanks,
Needing a clue - Scott

Reply via email to