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]
PGP Key: hkp:[EMAIL PROTECTED]
KeyID 2048/38C24864
Fingerprint 6D7D 1E4F 728B ACDA 6557 F3EC 85BB BA7C 38C2 4864
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
> -----Original Message-----
> From: Brian M. Collins [SMTP:[EMAIL PROTECTED]]
> Sent: 14 December 1998 03:41
> To: [EMAIL PROTECTED]
> Subject: [Fwd: diald working too well!]
>
> Pardon the quote marks, I am forwarding this from my "sent" folder. I
> had sent this out the the folks at my local LUG and got oodles of
> responses, none of which were very substantial. Thought I might try
> here.
>
> diald is version 0.16 (I think.. whatever came stock w/SuSE)
>
> Thanks!
>
> (message follows)
>
> "Brian M. Collins" wrote:
> >
> > Last night I installed diald and masquerading on my SuSE 5.3 box.
> > Everything was going just dandy (dialing, routing, ipforwarding, etc)
> > until I realized that diald was constantly picking up and dialing. Now,
> > being a fairly bright boy, I used tcpdump to observe what might be
> > hitting the link and causing the dial. A snippet of the suspect trace
> > is shown below:
> >
> > >
> > > 08:37:28.350816 192.168.2.1.netbios-ns > 192.168.2.255.netbios-ns:
> > > >>> NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST
> > > TrnID=0x189
> > > OpCode=0
> > > NmFlags=0x11
> > > Rcode=0
> > > QueryCount=1
> > > AnswerCount=0
> > > AuthorityCount=0
> > > AddressRecCount=0
> > > QuestionRecords:
> > > Name=BALTO NameType=0x00 (Workstation)
> > > QuestionType=
> > >
> > > 08:37:29.120816 8:0:9:de:ff:3 null > 8:0:9:de:6d:aa sap 45 rr (r=38,C)
> len=73
> > > 08:37:29.260816 ns2.ix.netcom.com.domain > 192.168.2.1.netbios-ns: 393
> NXDomain* 0/1/0
> > (102) (DF)
> > > 08:37:30.620816 8:0:9:de:ff:3 null > 8:0:9:de:6d:aa sap 45 rr (r=38,C)
> len=73
> > > 08:37:30.760816 ns1.ix.netcom.com.domain > 192.168.2.1.netbios-ns: 393
> NXDomain* 0/1/0
> > (102) (DF)
> > > 08:37:47.150816 8:0:9:de:ff:3 null > 8:0:9:de:6d:aa sap 45 I
> (s=0,r=33,C) len=62
> > > 08:37:47.150816 8:0:9:de:ff:3 null > 8:0:9:de:6d:aa sap 45 I
> (s=0,r=33,C) len=62
> > > 08:37:47.290816 ns2.ix.netcom.com.domain > 192.168.2.1.2876: 385
> NXDomain* 0/1/0 (102)
> > (DF)
> > > 08:37:47.310816 ns2.ix.netcom.com.domain > 192.168.2.1.2877: 385
> NXDomain* 0/1/0 (102)
> > (DF)
> > > 08:37:47.310816 8:0:9:de:ff:3 null > 8:0:9:de:6d:aa sap 45 rr (r=25,P)
> len=47
> > > 08:37:47.310816 8:0:9:de:ff:3 null > 8:0:9:de:6d:aa sap 45 rr (r=25,P)
> len=47
> > > 08:37:47.450816 ns2.ix.netcom.com.domain > 192.168.2.1.2878: 386
> NXDomain* 0/1/0 (96)
> > (DF)
> > > 08:37:47.470816 ns2.ix.netcom.com.domain > 192.168.2.1.2879: 386
> NXDomain* 0/1/0 (96)
> > (DF)
> > > 08:37:47.470816 192.168.2.1.netbios-ns >
> stonyman.collinsnet.com.netbios-ns:
> > > >>> NBT UDP PACKET(137): QUERY; REQUEST; UNICAST
> > > TrnID=0x18A
> > > OpCode=0
> > > NmFlags=0x10
> > > Rcode=0
> > > QueryCount=1
> > > AnswerCount=0
> > > AuthorityCount=0
> > > AddressRecCount=0
> > > QuestionRecords:
> > > Name=BALTO NameType=0x00 (Workstation)
> > > QuestionType=
> >
> > A little background info:
> > - 192.168.2.1 is a Win95 box and it is the only machine on the segment
> > with my Linux machine
> > - BALTO is an NT machine that is no longer on the segment
> > - stonyman.collinsnet.com is my Linux box
> > - netcom is my isp
> >
> > Nowthen, I am using the default (stock) /etc/diald.conf file which
> contains the
> > following lines re:netbios
> >
> > > # Don't bring up on domain name requests between two running nameds.
> > > ignore udp udp.dest=udp.domain,udp.source=udp.domain
> > > # Bring up the network whenever we make a domain request from
> someplace
> > > # other than named.
> > > accept udp 30 udp.dest=udp.domain
> > > accept udp 30 udp.source=udp.domain
> > > # Do the same for netbios-ns broadcasts
> > > # NOTE: your /etc/services file may not define the netbios-ns service
> > > # in which case you should comment out the next three lines.
> > > ignore udp udp.source=udp.netbios-ns,udp.dest=udp.netbios-ns
> > > ignore udp udp.dest=udp.netbios-ns
> > > ignore udp udp.source=udp.netbios-ns
> >
> > Since the above tcpdump trace shows this message over and over again,
> > and since taking the Win95 box off of the segment makes diald behave as
> > one would expect, I am led to believe that there is something going on
> > with netbios broadcasts that is triggering diald to pickup - but I may
> > be wrong.... that happened once too <grin>
> >
> > Any and all help on this will be really, really, appreciated!
> >
> > Thanks!
> >
> > --
> > Brian M. Collins Collins Network
> Engineering
> > [EMAIL PROTECTED] www.collinsnet.com
> > 831-419-0410 fax: 831-338-4171
>
> --
> Brian M. Collins Collins Network Engineering
> [EMAIL PROTECTED] www.collinsnet.com
> 831-419-0410 fax: 831-338-4171 <<
> Message: diald working too well! >>
-
To unsubscribe from this list: send the line "unsubscribe linux-diald" in
the body of a message to [EMAIL PROTECTED]
