On Fri, 04 Dec 1998, Bill Perpelitt wrote:
>Thomas,
>
>I had a similar problem with some Win95 machines that had the
>"client for Microsoft Networks" loaded. Apparently, the MS client
>tries to do a DNS lookup every x minutes whether it's needed or
>not. There's probably a way to filter this in the filter file, but I was
>never able to do it completely. I finally removed the Netbios service
>from my /etc/services file, which seemed to help. I swear the MS
>client caught on to what I had done and still managed to get diald to
>dial out, but without Netbios packets. I finally removed the MS client
>from the offending machine, and voila, no more phantom dials.
>
>Obviously, not a complete solution, especially for those needing MS
>peer functions or running Samba. But it worked for me.
>
>I'd be interested in hearing other solutions that allow the MS client
>to be active.
>
>Bill
>
A.N.Other (assuming that you have DNS running on your network, and
that you have it set up to provide names on your local network) fix
was to find out what name M$ was looking up (set "options query-log" in
/etc/named.boot and then look in /var/log/messages). You can then put
entries in your DNS configuration files to provide 'suitable' answers.
On a network that I administer, which has a netware server called 'viking'
which is accessed from win95 machines, they even seem to look up
the name 'viking' even though it doesn't run TCP/IP!! What a load of
old cobblers.
Regards
Mike Richardson
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
