Re: Why are my PCs trying to broadcast on port 137 and 138?
From: Karl Levinson [x y] mvp (levinson_k@excite.com)
Date: 11/21/02
- Next message: PDQ: "Re: blocked Email"
- Previous message: Greg: "index.dat"
- In reply to: Pip: "Re: Why are my PCs trying to broadcast on port 137 and 138?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Karl Levinson [x y] mvp" <levinson_k@excite.com> Date: Thu, 21 Nov 2002 11:28:52 -0500
I believe you can control in the registry whether your computers negotiate
to try to become the master browser, or you could try disabling the Computer
Browser service.
Yes, Netbios is talky, though WINS is available as an attempt to reduce the
broadcast noise. The constant negotiations are necessary in order to keep
the network working in case the browse master is rebooted or becomes
unavailable.
"Pip" <nntp@somewhere.com> wrote in message
news:OuCBX2RkCHA.716@tkmsftngp11...
> OK downloaded a sniffer and found it is browser announcements. Just wish
it
> wasn't so talkative and noisy.
>
> Domain/Workgroup Announcement , Domain controller, NT workstation, domain
> Enum
> and
> Host announcement, workstation, server, domain controller, print queue
> server, nt workstation, master browser
>
>
> "Pip" <nntp@somewhere.com> wrote in message
> news:ujCdmpJkCHA.1328@tkmsftngp09...
> > Hi. I'm trying to stop this from happening. I have wins running on NT
> 4.0
> > Server sp 6a + postfixes.
> > Client is XP Pro (no domain logon) just using NT Server for DNS, WINS,
no
> > DHCP, some filesharing (again not NT domain, just password prompted).
> >
> > I've switched to Node type 0x2 on both PCs (WINS only, no broadcasts).
> > At the time I see these broadcasts, there is no apparent activity and I
am
> > not actively doing anything at the time these happen.
> > Lately - I've also seen the Server trying to connect port 138 to a
> > nonexistent IP 192.168.1.15 (it the >
> [172.20.1.55:138]->[172.20.1.255:138] bcast dc0 l=192
> >
> > Nov 20 06:10:04 FILTER: Received information UDP
> > [172.20.1.55:138]->[172.20.1.255:138] bcast dc0 l=192
> >
> > And also one to a nonexistent IP address.
> >
> > Nov 20 06:07:29 FILTER: OBF (13) block - warning UDP
> > [172.20.1.15:138]->[192.168.1.15:138] dc0 l=247
> >
> > Nov 20 06:07:29 FILTER: Received information UDP
> > [172.20.1.15:138]->[192.168.1.15:138] dc0 l=247
> >
> > Thanks for any hints/tips you can offer.
> >
> >
>
>
- Next message: PDQ: "Re: blocked Email"
- Previous message: Greg: "index.dat"
- In reply to: Pip: "Re: Why are my PCs trying to broadcast on port 137 and 138?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
