Re: [SLUG] Networking Win95/Linux problem. (and another SLUG!)

["Aussie" <aussie@nospam.aussie.mine.nu>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 31 May 00, at 20:26, Heracles wrote:

> Tom Massey wrote:
> 
> > Hi, I'm trying to network a Win95 machine to my Linux (Mandrake 7) box
> > so that Win95 can access the Internet through a dial up PPP connection
> > on the Linux box. I've got an ISA NE-2000+ card in each machine,
> > connected with a crossover cable. <snip> Winipcfg shows the card with
> > all the right settings, and I can ping 192.168.1.2 but not 192.168.1.1
> > - I also can't ping either bob.localdomain or bib.localdomain, it
> > looks as though Windows isn't looking in the Hosts file. Nothing shows
> > up in tcpdump on Linux when I try pinging from Windows.
> >
> > Can anybody tell me what I'm doing wrong here? I'm wondering if it's a
> > bad cable? Thanks. BTW, in searching for info about this I stumbled
> > across another SLUG - the Sarnia LUG <http://www.sar-net.com/slug/>.
> > Just thought somebody might be interested. --

Hmmm, this sounds a LOT like my network setup and the same problem. 
Cable works perfectly, Linux is set up perfeclty and works ok, Windows 
appears to work but no info is sent between the computers.

> I have a windoze machine networked to my Linux machine. I had none of
> the trouble you are having. A few comments: 1. I presume you went into
> the properties box for the network on the windoze machine shows the card
> and has the TCP/IP protocol set up for it. 2. I also presume the machine
> is named and addressed in the identification area of the properties box.

Yup, just like I did, Windows was setup perfectly for the network, 
correct protocols, IP, netmask etc.

> This having been done, does Network Neighbourhood show one or both
> computers in the network?

There will be no Network Neighbourhood as such. If the network is 
browsed, you'll get an error.

> If there is still a problem, check the cable is correctly wired and
> continuous.

I'm betting the cable is perfect.

> If all this is OK then I would think about the use of IRQ3.  I assume
> you don't have a com port using that IRQ. On my old beast my mouse uses
> IRQ3 and my external modem IRQ4.

The problem for mine was that the BIOS was assigning IRQ 9 for the NIC, 
but Windows was assigning IRQ 10. Have a very close look at the IRQ's 
for the card, both in the bios startup screen (after the memory check) 
and in Windows and make sure the same IRQ is listed in both places. I 
manually set the IRQ's to the same and the network has worked ever 
since.

HTH
Aussie


-----BEGIN PGP SIGNATURE-----
Version: PGP 6.0.2 -- QDPGP 2.60 
Comment: Please verify this signature.  http://www.pgpi.com

iQA/AwUBOTSEkJZb9oayhFBBEQKmXgCdExLpKj7Q5P4/Pw2k+3CsPLgZgn4AoORs
DLI3//G++wFRWdUw4rTaC+6Q
=Bmdx
-----END PGP SIGNATURE-----

PGP Key Block available at:
http://aussie.mine.nu/aussie/pgp_key.txt
--
SLUG - Sydney Linux Users Group Mailing List - http://www.slug.org.au
To unsubscribe send email to slug-request@nospam.slug.org.au with
unsubscribe in the text