Win95 to Linux from Ground Zero

Win95 to Linux from Ground Zero

Post by Kurt Schweitze » Tue, 11 Mar 1997 04:00:00



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/

 
 
 

Win95 to Linux from Ground Zero

Post by dsp » Tue, 11 Mar 1997 04:00:00



> 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/

man ifconfig
man route
---
check your route table on the linux box.

default route should point to your ppp link
a route to your 192.168.1.0 network
and, your loopback

also make sure your eth0 has 192.168.1.1 bound to it with proper subnet,
broadcast.
        use ifconfig

 
 
 

Win95 to Linux from Ground Zero

Post by Kurt Schweitze » Wed, 12 Mar 1997 04:00:00



> man ifconfig
> man route
> ---
> check your route table on the linux box.

> default route should point to your ppp link
> a route to your 192.168.1.0 network
> and, your loopback

route -n yields:

Kernel routing table
Destination     Gateway         Genmask         Flags MSS    Window Use
Iface
192.168.1.0     *               255.255.255.0   U     1436   0        0
eth0
127.0.0.0       *               255.0.0.0       U     1936   0       12
lo
default         *               *               U     1436   0        0
eth0

Note that pppd is not running, so no routes through ppp.

ifconfig eth0 yeilds:

eth0      Link encap:10Mbps Ethernet  HWaddr 00:60:97:19:2B:29
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0
          TX packets:3 errors:0 dropped:0 overruns:0
          Interrupt:10 Base address:0x300

This says to me that everything SHOULD be happy. Right? So why can't I
seem to talk to anything via eth0?

--

Kurt Schweitzer
Sunrise Consulting, Inc.
716-427-7574

http://www.sunriseconsulting.com/
Small Business Technoplex - http://www.technoplex.com

 
 
 

Win95 to Linux from Ground Zero

Post by Kalevi Hautanie » Thu, 13 Mar 1997 04:00:00


: > man ifconfig
: > man route
: > ---
: > check your route table on the linux box.
: >
: > default route should point to your ppp link
: > a route to your 192.168.1.0 network
: > and, your loopback
: >

: route -n yields:

: Kernel routing table
: Destination     Gateway         Genmask         Flags MSS    Window Use
: Iface
: 192.168.1.0     *               255.255.255.0   U     1436   0        0
: eth0
: 127.0.0.0       *               255.0.0.0       U     1936   0       12
: lo
: default         *               *               U     1436   0        0
: eth0

: Note that pppd is not running, so no routes through ppp.

: ifconfig eth0 yeilds:

: eth0      Link encap:10Mbps Ethernet  HWaddr 00:60:97:19:2B:29
:           inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
:           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
:           RX packets:0 errors:0 dropped:0 overruns:0
:           TX packets:3 errors:0 dropped:0 overruns:0
:           Interrupt:10 Base address:0x300

: This says to me that everything SHOULD be happy. Right? So why can't I
: seem to talk to anything via eth0?

No! All is not OK. Comment out a line which says:

/sbin/route add default gw ${GATEWAY} metric 1

from your /etc/rc.d/rc.inet1 by putting '#' into front of it. You'll
need no default gateway when you're working with machines in your
local network. In the options file for your pppd, remember include
'defaultroute' into it.
--
                        Kalevi J Hautaniemi
----------------------------------------------------------------------------
Marjatankatu 12       |tel: +358-3-364-7446           |fax: +358-3-364-2476

FINLAND               |http://www.sci.fi/~khmi/       |On air:  OH3FG, KO4BC
----------------------------------------------------------------------------

 
 
 

Win95 to Linux from Ground Zero

Post by Kurt Schweitze » Thu, 13 Mar 1997 04:00:00



> No! All is not OK. Comment out a line which says:

> /sbin/route add default gw ${GATEWAY} metric 1

> from your /etc/rc.d/rc.inet1 by putting '#' into front of it. You'll
> need no default gateway when you're working with machines in your
> local network. In the options file for your pppd, remember include
> 'defaultroute' into it.

I've taken your advice.

route -n yields:

Kernel routing table
Destination     Gateway         Genmask         Flags MSS    Window Use
Iface
192.168.1.0     *               255.255.255.0   U     1436   0        0
eth0
127.0.0.0       *               255.0.0.0       U     1936   0       12
lo

ifconfig eth0 yeilds:

eth0      Link encap:10Mbps Ethernet  HWaddr 00:60:97:19:2B:29
          inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0
          TX packets:3 errors:0 dropped:0 overruns:0
          Interrupt:10 Base address:0x300

I still can't ping one of the Win95 systems, and they can't seem to ping
me. Any other suggestions?

--

Kurt Schweitzer
Sunrise Consulting, Inc.
716-427-7574

http://www.sunriseconsulting.com/
Small Business Technoplex - http://www.technoplex.com

 
 
 

Win95 to Linux from Ground Zero

Post by Kalevi Hautanie » Fri, 14 Mar 1997 04:00:00


: eth0      Link encap:10Mbps Ethernet  HWaddr 00:60:97:19:2B:29

Hello Kurt.

Sorry, it wasn't it.

There really is something odd in your system. Can you ping between
those Win95 -boxes? How is your cabling? Have you hooked your net
up with coax or what? Have you tried to swap those NICs mutually
between your machines?

The hardware address shown above looks weird to be 3Com product, but
I do not have documents here at job to check. I'll be back after
I've found it.
--
                        Kalevi J Hautaniemi
----------------------------------------------------------------------------
Marjatankatu 12       |tel: +358-3-364-7446           |fax: +358-3-364-2476

FINLAND               |http://www.sci.fi/~khmi/       |On air:  OH3FG, KO4BC
----------------------------------------------------------------------------

 
 
 

Win95 to Linux from Ground Zero

Post by Kurt Schweitze » Fri, 14 Mar 1997 04:00:00


After sending out last night's message, I stumbled across a route
command in Win95. No, it is NOT very similar to the Linux route command
(Microsoft just HAS to do things THEIR way!), but it did provide me with
some useful information (like TCP/IP was actually working in those
boxes!)

Anyway, I have now successfully ping'd each Win95 system FROM THE OTHER,
but NOT from the Linux box. When I attempt to ping the Linux box from
either of the Win95 boxes, I get timeout errors.

At this point I'm suspicious of the setup of the 3C509 card in the Linux
box. I'm going to boot it into DOS (gasp!) and use the configuration
disk that came with the card to play around with its setup. I suspect
the media selection (thinnet vs. 10baseT) is not set correctly. I'll
drop another note with my results (just in case anyone is actually
reading this thread!)

--

Kurt Schweitzer
Sunrise Consulting, Inc.
716-427-7574

http://www.sunriseconsulting.com/
Small Business Technoplex - http://www.technoplex.com

 
 
 

Win95 to Linux from Ground Zero

Post by Kurt Schweitze » Fri, 14 Mar 1997 04:00:00


A final message to close this thread. (Yes, my problem is solved!)

It turned out that the problem with talking between the Win95 boxes and
the Linux box was in the setup of the 3Cs09 card. My particular card has
both thinnet and 10baseT connectors on it. The default configuration
tells it to automatically choose which connector to use. I needed to
force the configuration to BNC (thinnet) to get things to work. I also
disabled the PlugNPlay feature, although I don't think that's necessary
in my old ISA box.

Once I had the card using thinnet, things went smoothly. I was able to
ping the Linux box from one of the Win95 boxes. More importantly, I was
able to telnet and ftp from the Win95 boxes to the Linux box. And as a
capper, I was able to fire up PPP on the Linux box, ftp to an Internet
site, and pull down more software in my ever-widening quest to turn this
used 486 machine into a Linux-based Net-serving Demon!

Next challenge: Making the Linux box a dial-out gateway. (Next message
thread!)

I'd like to thank everybody for their assistance!

Kurt

--

Kurt Schweitzer
Sunrise Consulting, Inc.
716-427-7574

http://www.sunriseconsulting.com/
Small Business Technoplex - http://www.technoplex.com

 
 
 

1. Can't even get past ground zero :-(

 I'm trying valiently to get Linux up on a HP NetServer (486/66). This
 machine has an embedded SCSI controller. The printing on the controller
 sez that it's an adaptec 7770, however anything that talks to it identifies
 it as an AHA274x.

 When I attempt to boot I get the following message, followed by a total
 hang:

   aha274x warning: ignoring channel B of 274x-twin
   aha274x: extended translation disabled
   AHA274X AT EISA SLOT 9
       irq 11
       bus release time 60 bclks
       data fifo threshold 100%
       SCSA CHANNEL A:
           scsi id 7
           scsi bus parity check enabled
           scsi selection timeout 256 ms
           scsi bus reset at power-on enabled
           scsi bus termination disabled
   scsi0 : Adaptec AHA274x/284x (EISA/VL-bus -> Fast SCSI) 1.28/1.11/1.29
   scsi : 1 host.
   scsi : aborting command due to timeout : pid 0, scsi0, id0, lun 0, Test
   Unit Ready 00 00 00 00 00
   scsi : aborting command due to timeout : pid 0, scsi0, id0, lun 0, Test
   Unit Ready 00 00 00 00 00
   SCSI  host 0 abort() timed out - resetting
   aha274x: attempting to reset scsi bus and card
   scsi : aborting command due to timeout : pid 0, scsi0, id 0, lun 0 Test
   Unit Ready 00 00 00 00 00

 Anybody have any hints as to what's goin' on here?

 Thanks,

 ..glen

2. Backup Windows Box on Linux Box via SMB?

3. Ground Zero Plans Call For Super-Tall Building :-)

4. Red hat 6.0 FTP Server

5. Can't even get past ground zero :-(

6. SOLUTION AT LAST: rvplayer as helper app in Redhat-5.2

7. Ground Zero - help?

8. Post install help??

9. Floppy reports size as zero sectors, zero tracks, zero bytes

10. Bash grinding, grinding and using all my memory?

11. samba: win95->linux works, linux->win95 doesnt

12. getting win95 shares on win95 machines to map with a login script with samba and win95

13. newbie:installing linux from ground up