Marco Ghidinelli wrote:
> Bas Kelderman wrote:
> >
> > Hi,
> >
> > I have seen a lot of problems with people that get too many diald calls
> > because Windows is looking up it's network name. I have noticed that with
> > each susequent windows install (and I do that a lot ...) I never have this
> > problem, is this due to the fact that I don't use netbeui?
> > If this is the case can this be incorporated into the docs? You don't need
> > netbeui to connect to a samba server or NT box, some people will need
> > IPX/SPX to play games over the network but that is it.
> >
> > I install all the machines that run on our network and we have never seen
> > this problem (I never install netbeui).
>
> i have netbeui and i have problems!!
>
> > Currently we are running Win95/98/NT/linux and all is going well.
>
Win9x clients send out repeated requests for the IP address of a node going by
the name of the workgroup, which is complete bollocks as far as the typical home
Samba setup is concerned. This causes a dial out because, by default, if a
NetBIOS lookup doesn't return the address, the query is converted into a DNS
query. If the name server on your local network can't translate the name either,
then depending on your DNS setup, your local DNS may forward the request to
another DNS outside your network or the Win client may try that other DNS
directly.
Apparently this behaviour can be defeated via a Windows registry hack which
disables all conversion of NetBIOS lookups to DNS lookups. It's been documented
on this list back in January. One each client, you need to create a .reg file
containing these lines:
REGEDIT4
[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP]
"EnableDNS"="0"
and put a line into your autoexec.bat that imports this into the registry each
time the machine boots up.
Ugh! What a kludge! Even so this is probably the most straightforward solution.
But if you want to have your own DNS server there is another way which is more
flexible *and* less of a hack. That is, to set up your DNS server as a cacheing,
forwarding DNS which is authoritative for your local private domain (this has
its own benefits anyway, particularly when you use diald to connect your network
to the internet). Thus, even if a NetBIOS request for a host address within your
own domain (such as the workgroup name) is converted to a DNS reverse lookup, it
will go to your local nameserver and no further. As a bonus, lookups for hosts
which are explicitly outside your local domain can still be forwarded via DNS,
though I guess that's only any use to you if you want to route NetBIOS between
remote domains connected over a WAN or the internet.
--
[EMAIL PROTECTED] Ralph Clark, Virgo Solutions Ltd (UK)
__ _
/ / (_)__ __ ____ __ * Powerful * Flexible * Compatible * Reliable *
/ /__/ / _ \/ // /\ \/ / *Well Supported * Thousands of New Users Every Day*
/____/_/_//_/\_,_/ /_/\_\ The Cost Effective Choice - Linux Means Business!
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
