Linux router supporting Win95&98 workstations - Win95 cannot find other LAN hosts

Linux router supporting Win95&98 workstations - Win95 cannot find other LAN hosts

Post by Paul L. Goldma » Wed, 12 Apr 2000 04:00:00



I have built the following LAN:
Pentium 90 with two NICs running as a router under Redhat 6.1. Eth0 accesses
my cable modem ISP, RoadRunner, while Eth1 supports a LAN with two machines,
one Win 95, one Win 98.  The two Win machines were configured with static IP
addresses - 192.168.1.2 & 3, the Linux machine is 192.168.1.1.  The Linux
/etc/hosts file shows all machine names with the appropriate IP addresses.
I use IP chains and  IPv4 forwarding to allow the two Win machines to access
the internet via RoadRunner.

The Win machines have no problems accessing the Internet, or AOL for that
matter.

My problem is as follows:  The Win 98 machine can ping the Win 95 machine
using both its static ip address and its host name.  The Win 95 machine can
ping the Win 98 machine using only its static ip address, pinging with the
Win 98 host name results in an unkown host error.  Using the "find computer"
option in Win 98, the Win 95 machine is found with no problems and any
shared files can be accessed by the Win 98 machine.  The Win 95 machine
cannot "find" the Win 98 machine.  The machines are configured for TCP/IP
only - for Internet DNS they are configured to use the RoadRunner DNS with
the Linux router as Gateway.

I can add NetBEUI as an additional protocol for the two Win machines and
everything on the LAN works as it should and they can still access the
Internet via TCP/IP.   However, I would be interested in running the LAN as
TCP/IP only and so any help in figuring out the problem would be
appreciated.  Why does the Win 98 machine behave very well while the Win 95
machine doesn't seem to be able to find LAN resources?

Regards,
Paul

 
 
 

Linux router supporting Win95&98 workstations - Win95 cannot find other LAN hosts

Post by Andrey Smirno » Wed, 12 Apr 2000 04:00:00


You probably need to have entries for Win98 and Linux machines in
c:\windows\hosts file on Win95 machine.

Good luck!



Quote:> I have built the following LAN:
> Pentium 90 with two NICs running as a router under Redhat 6.1. Eth0
accesses
> my cable modem ISP, RoadRunner, while Eth1 supports a LAN with two
machines,
> one Win 95, one Win 98.  The two Win machines were configured with static
IP
> addresses - 192.168.1.2 & 3, the Linux machine is 192.168.1.1.  The Linux
> /etc/hosts file shows all machine names with the appropriate IP addresses.
> I use IP chains and  IPv4 forwarding to allow the two Win machines to
access
> the internet via RoadRunner.

> The Win machines have no problems accessing the Internet, or AOL for that
> matter.

> My problem is as follows:  The Win 98 machine can ping the Win 95 machine
> using both its static ip address and its host name.  The Win 95 machine
can
> ping the Win 98 machine using only its static ip address, pinging with the
> Win 98 host name results in an unkown host error.  Using the "find
computer"
> option in Win 98, the Win 95 machine is found with no problems and any
> shared files can be accessed by the Win 98 machine.  The Win 95 machine
> cannot "find" the Win 98 machine.  The machines are configured for TCP/IP
> only - for Internet DNS they are configured to use the RoadRunner DNS with
> the Linux router as Gateway.

> I can add NetBEUI as an additional protocol for the two Win machines and
> everything on the LAN works as it should and they can still access the
> Internet via TCP/IP.   However, I would be interested in running the LAN
as
> TCP/IP only and so any help in figuring out the problem would be
> appreciated.  Why does the Win 98 machine behave very well while the Win
95
> machine doesn't seem to be able to find LAN resources?

> Regards,
> Paul


 
 
 

Linux router supporting Win95&98 workstations - Win95 cannot find other LAN hosts

Post by patrick.them.. » Thu, 13 Apr 2000 04:00:00




Quote:> I have built the following LAN:
> Pentium 90 with two NICs running as a router under Redhat 6.1. Eth0
accesses
> my cable modem ISP, RoadRunner, while Eth1 supports a LAN with two
machines,
> one Win 95, one Win 98.  The two Win machines were configured with
static IP
> addresses - 192.168.1.2 & 3, the Linux machine is 192.168.1.1.  The
Linux
> /etc/hosts file shows all machine names with the appropriate IP
addresses.
> I use IP chains and  IPv4 forwarding to allow the two Win machines to
access
> the internet via RoadRunner.

> The Win machines have no problems accessing the Internet, or AOL for
that
> matter.

> My problem is as follows:  The Win 98 machine can ping the Win 95
machine
> using both its static ip address and its host name.  The Win 95
machine can
> ping the Win 98 machine using only its static ip address, pinging with
the
> Win 98 host name results in an unkown host error.  Using the "find
computer"
> option in Win 98, the Win 95 machine is found with no problems and any
> shared files can be accessed by the Win 98 machine.  The Win 95
machine
> cannot "find" the Win 98 machine.  The machines are configured for
TCP/IP
> only - for Internet DNS they are configured to use the RoadRunner DNS
with
> the Linux router as Gateway.

> I can add NetBEUI as an additional protocol for the two Win machines
and
> everything on the LAN works as it should and they can still access the
> Internet via TCP/IP.   However, I would be interested in running the
LAN as
> TCP/IP only and so any help in figuring out the problem would be
> appreciated.  Why does the Win 98 machine behave very well while the
Win 95
> machine doesn't seem to be able to find LAN resources?

> Regards,
> Paul

this seems more a win9x problem than linux networking,

anyway, check the network properties on both win-machines.
i would look especially at the following:
the 'identification' tab,
the name given here should match the ipname under tcpip properties
(i think its dns, and hostname there)
also check that they belong to the same workgroup.
check that 'netbios over tcp' is enabled

last resort, create a hosts and a lmhosts file,
both from one of the .sam-files that win provides,
add all of your machines and their ipadresses ,
and copy it to the %systemroot-folder ( usually c:\windows )

hth

--
'...' said the joker to the thief
'there's too much confusion, i cant get no relief...
so let us not talk falsely now, the hour's getting late'

Sent via Deja.com http://www.deja.com/
Before you buy.

 
 
 

1. M$ Win95/98/NT hosts on LAN causing dialout

This is for everyone who has M$ hosts on their lan. I had seen postings
before about people having problems w/ M$ Windows trying to initiate a
dial-connection all the time. I personally had/have a problem where
pinging a host on the lan w/ an ip address was no problem, but pinging
by name caused a dial-up connection (I still had a modem in the Win98
machine as well). Once the DUN connection was cancelled, Win98 would
come up w/ the proper name for the host on the lan no problem... it
just insists on trying to dial out first. I had hunted down some info
via dejanews about the M$ hosts and lmhosts and networks files in the
c: \windows directory, from some samba groups, w/ the theory being that
if you rename the hosts.sam(ple)& lmhosts.sam files to hosts and
lmhosts, respectively, and modify them according to your needs, that
Win95 would use these files in the same manner that linux
uses /etc/hosts and /etc/resolv.conf if so configured. And I dug up
documents from M$'s Knowledge Base regarding editing the registry in
Win95 and WinNT to set the priority(order) in which Windows looks to
various sources for name resolution. I haven't tried those personally,
as I don't have a Win95 or WinNT client handy. What I have, as I
mentioned, is Win98. Turns out that Win98 uses Winsock 2.0 vs. Winsock
1.1 like 95/NT, and therein lies the problem. Winsock 2.0 doesn't
appear to support the ability to configure Windows to look in the hosts
files _first_, unlike win95/NT. I had tried just about everything I had
found up to this point,
including editing /mnt/router/etc/named.hst and named192.rev in freesco
(what the heck does the ' IN A' AND 'IN PTR' stand for in those files,
BTW?), setting up c:\windows\hosts, lmhosts, and networks, adding keys
to the registry. Thought I was losing my little mind ;) I finally got
thru to M$ support in an attempt to get them to send me the patched c:
\windows\system\rnr20.dll (dated May-something-99) and some additional
documentation. So far I have been 'escalated' twice, and will
presumably receive another phone call or the new patch file 85881.exe
in the next 2-5 business days. It seems that the file in question
is 'not fully regression tested' or something like that.  Perhaps if
some more people contact M$ regarding this, we can make some progress.
Here's hoping!

I hope this helps someone else out there. Here are the relevant M$
Knowledge Base Document Numbers:

Q158474 Windows TCP/IP Registry Entries
Q216470 Windows Socets 2.0 Does Not use DnsNbtLookupOrder Value
Q172218 M$ TCP/IP Host Name Resolution Order
Q139270 howto Change Name Resolution Order on Win95/NT

And finally, last, but not least, for those of you who just upgraded
Win95 to Win98, good news! You can 'downgrade' your Winsock 2.0 to
Winsock 1.1 (Win95) per the following

Q185860 How to Restore the Winsock 1.x configuration in Win98

Monte

--
There are basically three kinds of men.  There
are the ones who learn by reading.  Then there are
the few who learn by observation.  The rest just
have to pee on the electric fence for themselves.

Sent via Deja.com http://www.deja.com/
Before you buy.

2. Just a few questions...

3. M$ Win95/98/NT hosts on LAN causing dial-out

4. Linux Security Week, September 25th 2000

5. Need good Linux equiv to Win95/98/NT4 find text in file function

6. how to copy a running system?

7. Win95/98/NT/2K install times & Linux

8. X Setup

9. how to ppp(win95) - pppd(linux)+eth0 -- lan -- win95

10. Setting up Linux as PPP router with Win95 workstations

11. ISP/Modem Share w/ FreeBSD & Win95/98 network

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