[1626] in linux-net channel archive
Re: Win95 <-> Linux
daemon@ATHENA.MIT.EDU (Avery Pennarun)
Sun Jan 14 19:09:34 1996
Date: Sun, 14 Jan 1996 18:58:58 -0500 (EST)
From: Avery Pennarun <apenwarr@foxnet.net>
To: Bas Rijniersce <basrijn@hacom.nl>
cc: linux-net@vger.rutgers.edu
In-Reply-To: <199601141747.SAA13334@box.hacom.nl>
On Sun, 14 Jan 1996, Bas Rijniersce wrote:
> I have two computers, one 486sx25/8Mb running Win95, the other running
> Linux. I use an arcnet network to connect them. With both machines running
> Win95 eveything works fine.
>
> I have ftp-ed the latest ARCnet driver and I have recompiled the kernel with
> arcnet support. At boot-time the arcnet card is detected.
> I have changed all configuration file that I know of (i am not an
> experienced user, so maybe i have missed something, but i read the NAG etc.)
>
> When I Telnet/FTP local everything works fine. But when I try to telnet from
> the Win95 machine to the Linux machine nothing happens :(((
> NETSTAT -i show that there are packets received OK, but no response is send
> :( (i think)
> Could it be a routing problem? What else should i look for?
Look for kernel messages (the dmesg command). If there's a routing problem,
you may be getting "could not build ICMP header..." messages.
Windows 95, in its "16-bit NDIS driver" mode, uses an ARCnet protocol
incompatible with the standard. You either need to use the "16-bit ODI
driver" in Windows (have some Novell Client disks ready) or use 2.00 or
greater of Linux-ARCnet and its "arc0e" virtual arcnet device. Read the
driver docs for more information about this.
If you continue to have problems, you will probably want to write to me (the
author of the Linux-ARCnet driver) directly rather than bother this mailing
list. It may be a problem unrelated to the above, as Windows 95's
networking can be a real pain to configure properly.
Have fun,
Avery
