I've been reading this newsgroup for several days now, and have seen
many good suggestions for doing things similar to what I'm attempting.
However, it seems that my situation has too many differences from the
other descriptions I've seen, so even after trying numerous suggestions
I'm still not up and running.
My situation: I have two PCs running Win95. A third PC has Linux,
recently installed from year-old Slackware disks.
The Win95 machines have been used for PPP dial-up to the Internet for
months or years. I recently installed ethernet cards in them, and have
successfully constructed a peer-to-peer Win95 network. I have TCP/IP
protocol stacks installed as well.
The Linux machine has been successful at communicating with my ISP via a
PPP connection.
I recently installed a 3C509-TP card in the Linux machine. On the advice
of a previous post, I disabled Plug-N-Play even though the box is an
older one that shouldn't be affected by it.
For my internal LAN I've assigned IP addresses 192.168.1.x for the three
machines. (x = 1 for the Linux machine, 2 or 3 for the Win95 PCs.)
Here's where things start "not working". On the Linux machine, if I ping
myself (192.168.1.1) it says it works, but the packets are routed
through the loopback interface (lo). If I ping Win95-1 (192.168.1.2) it
fails, and netstat says the packets were routed through the 3C509
(eth0).
On the Win95 machines, if I try to ping the Linux box (192.168.1.1) the
dial-up networking kicks in and trys to establish a connection with my
ISP!
I guess my questions are 1) what do I need to do on the Linux box to be
able to successfully ping out across my in-house ethernet, and 2) what
do I need to do on my Win95 boxes to be able to successfully ping the
Linux box?
I appreciate you assistance.
P.S. could you respond via e-mail as well as posting? Even with reading
this group twice a day I get the feeling I'm missing some posts. Thanks!
--
Kurt Schweitzer
Sunrise Consulting, Inc.
716-427-7574
http://www.sunriseconsulting.com/