On Wed, 16 Dec 1998, Arun K. Khan wrote:
> Another alternative is to 'ignore' the Netbios name lookup packets by editing
> /usr/lib/diald/standard.filter - look for the netbios-ns comments/section
> and modify the lines below it to 'ignore' and voila you don't have to mess
> with any of the Win9x/NT boxes in your network. Also make sure the filter
> is included in your diald.conf.
Actually, this will only solve part of the problem. On my system, this
was already in place. The problem my system was having was it didn't find
a netbios nameserver to respond. so, it resorted to doing plain old DNS
lookups. there was no way to filter just these DNS lookups out and not
filter "ligitmate" DNS lookups. However, I found that just by running
samba (it didn't even need to be configged to do anything useful :) it was
responding to the win95 netbios lookups, so my win95 machine didn't do DNS
lookups for netbios anymore. Problem solved.
> HTH
> - Arun Khan
>
> At 08:41 AM 12/16/98 +0000, Mike Sharp wrote:
> >Brian,
> >
> >Joel Knight [[EMAIL PROTECTED]] posted this a while back. Think it
> >might sort your problem.....
> >
> >Joel Knight [[EMAIL PROTECTED]]:
> >Hello.
> >
> >I have multiple Win9x boxes that access the net through a linux gateway
> >using ip_masq and diald. I also noticed the unrequested dialing out on the
> >linux server. To me it appeared that whenever someone logged onto the
> >network, diald would dial out. I finally found an article on some webboard
> >that explain a solution for this. I don't have that article any more, but
> >I do have the solution.
> >
> >If you goto Start / Run and type 'winipcfg' on the windows boxen and look
> >for the box that says "NetBIOS uses DNS" (or something to that affect) it
> >will most likely have a check mark in it. The article I had said that
> >this causes windows to use DNS to do netbios name lookups. This seems
> >to coincide with the reports of others on the list who say that they
> >fixed the problem by setting up a name server for their local net (which
> >I did not do).
> >
> >Now, copy the following lines to a file call dns-fix.reg:
> >
> >
> >REGEDIT4
> >
> >[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP]
> >"EnableDNS"="0"
> >
> >
> >Import dns-fix.reg into the registry by double clicking the file. Now run
> >winipcfg again. The check mark should be gone. Reboot and see if windows
> >will bring your ppp link up any more.
> >
> >Like I said, this solution fixed the problem for me. What I did was put a
> >line into my autoexec.bat file that imports this registry file so that if
> >I make any changes to Control Panel / Network, I don't have to remember to
> >manually import it.
> >Good luck! :-)
> >
> >On Thu, Dec 03, 1998 at 04:08:10PM -0800, 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.
> >
> >--
> > Joel Knight [EMAIL PROTECTED]
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-diald" in
> the body of a message to [EMAIL PROTECTED]
>
-----
Jim Kusznir ([EMAIL PROTECTED])
RidgeNET Tech Support
371-3501
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
