Mike Patterson wrote:
> Hi there--
> My latest excursion has been into the realm of Kahn, a variation on
> Kali. Of course, I'm having some problems, and the answer doesn't seem to
> be obvious to other Kahn users, so I'm guessing that it's a problem with
> my network.
> The setup is this:
> 188.8.131.52 is a linux machien running kahnd
> 184.108.40.206 is a win95 dialing into 220.127.116.11
> 18.104.22.168 is a win95 machine on the same lan as 22.214.171.124
> Connect through mgetty/pppd just fine. 126.96.36.199 and 188.8.131.52 can both read
> the samba drives on 184.108.40.206.
> Now, both .2 and .3 can connect to the kahnd on 220.127.116.11, and can talk to
> each other, but .2 doesn't show on .3's list.
Which "list" is that? If you mean "When I open 'Network Neighborhood'
on 18.104.22.168 I can't see 22.214.171.124" then you've discovered one of the
gross inadequacies of NetBIOS (and NetBT). You see, when LanManager
was conceived (yes, this is what we now call "Microsoft Networking")
they wanted it to be *easy* to use, not like that confusing TCP/IP
stuff. So, rather than have a distributed, managed name space a la
DNS they decided that they would use a flat name space and let
chaos rule. Machines sharing a network literally "fight it out"
to decide who's going to be the "Browse Master"--the computer
responsible for knowing who all is on the network. At any rate, in
NetBT (read as "using Microsoft Networking over TCP/IP") UDP
broadcast is used to look up machines (to map machine name to
IP address) and UDP broadcast packets are *not* routed which
means if 126.96.36.199 is trying to find 188.8.131.52 by name, it won't find
it. The solution to this is to set up a WINS server--sorta like
a DNS server. You can do this in Linux, you just need SAMBA (which
it seems like you already have. The program is nmbd and you need
to create a file which maps host names to IP addresses (and which
looks like an /etc/hosts file) and 'nmbd -H your-lm-hosts-file'
will then run the server. Then on your Win95 client go into TCP/IP
settings and set 184.108.40.206 as a WINS server. If you've got '-proxyarp'
being passed to pppd on your Linux box, you should be there.
> In addition, when trying to play a game (any game!), I can see the network
> game, but when I attempt to join it, the attempt fails. I assume this means
> that either global or direct packets aren't making it.
> Any ideas would be helpful, or at least where to look. Thanks.
I hope this helps. Your post was actually a little too vague to be
able to tell what problem you're having.
Jens B. Jorgensen
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
Trouble? e-mail to email@example.com .
- Re: kahnd
- From: Hamish Moffatt <firstname.lastname@example.org>
- From: Mike Patterson <email@example.com>