From: "Jochen Kächelin" <[EMAIL PROTECTED]>

> Linuxbox: 192.168.0.1 jochen.wa-p.off
> Win98-Clients: 192.158.0.2/5 "USER".wa-p.off

192.158.0.2 is not an address you should use unless it is assigned to
you by internet authorities. Use 192.168.25.2 instead - unless your ISP
assigned you that address as a network block. In otherwords check whether
the numbers below or above are correct.

Also a /5 size subnet on a 192.168.x.y address is "unusual." A /24 size
subnet is more common. You have included an impressive range of addresses
as your local network which is a guarantee of interesting routing problems.

Note that Windows machines chronicly set you up with a 255.255.0.0 mask for
a 192.168.x.y address. This can work IF all boxes on that network have the
same mask. Reset it to 255.255.255.0 for most situations and if you were
trying for a 32 address subnet the mask would be 255.255.255.224 on all
machines to make it work.

> Connection: T-DSL Flatrate (works on Linuxbox)
>
> On the Linuxbox (jochen.wa-p.off):
>
> Connection to the web -> works fine!
> ping 192.168.0.5 -> works fine!
> ping julius.wa-p.off -> works fine!
>
> On Win98 (192.168.0.5)
>
> Connection to the web -> NO CHANCE!
> ping 192.168.0.1 -> works fine!
> ping jochen.wa-p.off -> unknown host!
>
>
>
> /sbin/route shows the following:
>
> Ziel            Router          Genmask         Flags Metric Ref    Use Iface
> pD951845B.dip.t localhost       255.255.255.255 UGH   0      0        0 lo
> 217.5.98.32     *               255.255.255.255 UH    0      0        0 ppp0
> 192.168.0.0     jochen          255.255.255.0   UG    0      0        0 eth0
> 192.168.0.0     *               255.255.255.0   U     0      0        0 eth0
> 127.0.0.0       *               255.0.0.0       U     0      0        0 lo
> default         217.5.98.32     0.0.0.0         UG    0      0        0 ppp0
>
>
> nslookup localhost shows the following:
>
> Server: 194.25.2.129
> Address: 194.25.2.129#53
> Name: localhost
> Address: 127.0.0.1
>
>
> nslookup 127.0.0.1 shows the following
> Server: 194.25.15.11
> Address: 194.25.15.11#53
> 1.0.0.127.in-addr.arpa name = localhost.
>
> nslookup 192.168.0.1 shows the following
> Server: 194.25.2.129
> Address: 194.25.2.129#53
> ** server can't find 1.0.168.192.in-addr.arpa.: NXDOMAIN

Unless you setup bind properly you are toast. You must explicitly enter into
the bind configuration the addresses of the machines in question. It appears
you have not done this.

> I tried to managed it with bindconf - not successfully!

I've done it manually all the time so I don't know what bindconf wants by
way of setup. An example configuration for an older version of bind exists
at http://home.earthlink.net/~jdow/dns_files.zip. This is the "obfuscated"
configuration I run here with multiple subnets on multiple connections here
on our testing campus at "Wizardess Keep." (We run a lot of "oddball" "things"
on our network from time to time. It helps to keep them separate.)

> Hoping to find someone who can/will help a Windows NT user
> who wan't to become a Linux user!

I've been sliding the other way since what I am getting paid handsomely to
do does not exist for Linux and probably never will unless the preemptive
kernel patches and low latency kernel patches get adopted. (For those who
are unsane enough to wonder visit Matrox, look up "DigiSuite LE". It will
not likely ever run X. But that aside it is a very nice video system for
broadcasting or "prosumers".)

{^_^}



_______________________________________________
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list

Reply via email to