The browser service is still basically the same as it was in NT4 SP5 . To
see what it is doing, you still use the browstat utility (from the support
tools).
You can prevent a workstation from trying to become a master browser by
stopping the browser service on it. Just leave it running on the PDC
emulator and one or two other machines for backup browsers.
<(E-Mail Removed)> wrote in message
news:285b01c48e60$5ecbddc0$(E-Mail Removed)...
> Bill, what you say is correct,
> But the machine is already up and running (without going
> down again) for several weeks and we're still getting
> these MRxSmb errors. It's like the Domain Controller
> doesn't get the job done that it's the DMB.
>
> So the rash should stop after a few re-elections ?!
> I use the white paper: MS Windows NT Browser, Technical
> Notes in Technet.
>
> Greetings and thanks for the response!
>
> >-----Original Message-----
> > Your DC is automatically your domain master browser.
> If it goes down,
> >there will indeed be a rash of browser elections, because
> no machine can see
> >the DMB.
> >
> ><(E-Mail Removed)> wrote in message
> >news:12a601c48c05$10ea9270$(E-Mail Removed)...
> >> Experiencing a lot of RDR errors in the early days with
> >> NT4, I was happy to install windows2003 DC's, praying I
> >> wouldn't have re-elections anymore....
> >>
> >> I didn't pray enough ?
> >>
> >> The system log of our Windows2003 SE Domain controller
> is
> >> flooded with events:
> >>
> >> 040825 07:58:01 MRxSmb Error
> >> None 8003 NA W2K3DC01
> >> The master browser has received a s
> >> erver announcement from the computer PC00662 that
> believes
> >> that it is the master browser for the domain on transpor
> >> t NetBT_Tcpip_{D0F30D40-507C-41F1-B. The master browser
> is
> >> stopping or an election is being forced.
> >>
> >> I've found a lot on the internet, but no real solutions
> >> than changing router configs (no ip forwarding netbios)
> to
> >> changing all computers (we have a LOT of client
> computers)
> >> registry so they don't masterbrowser themselves,
> changing
> >> networkcables, ....
> >>
> >> The strangest of all is that I'm experiencing these
> errors
> >> after our Domain Controller (also WINS, DNS and DHCP
> >> server) was down for a 10 minutes maintenance.
> >>
> >> Never had these erros before! (Domain controller is
> >> already running since may 2003).
> >>
> >> I've read a lot of broadcast (almost wrote myself a
> >> thesis ;o), kow about election protocol, why it happens,
> >> switched networks, ... but the starngest of all: even
> >> servers in a remote, firewalled network (als
> domainmembers
> >> with remote DC's) are demanding re-elections !
> >>
> >> I'm puzzeld and hopeless.
> >> Is disabling the <<damn>> browsing on all of our clients
> >> and servers the only solution? Anyone did something like
> >> that in an International, BIG corperate netork?
> >>
> >> Greetings! .David.
> >>
> >>
> >
> >
> >.
> >
|