First, MrxSmb Event (8003), then no TCP!

I have a windows 2000 server that all of a sudden, started getting 8003 events in the event log:

MrxSmb:
The master browser has received a server announcement from the computer F921JK that believes that it is the master browser for the domain on transport NetBT_Tcpip_{3755D572-E43. The master browser is stopping or an election is being forced.

This event is nothing new or horrible, but what is horrible is shortly after this even is logged, the TCP stack on the server goes down. No pings, no traffic, nothing... and worse... no event log entries as to why. I attempted to diagnose any cable, hub, nic, etc.. issues.. but for two weeks now its consistent behavior... every couple days, the server "goes down" and nobody can work... I check the event log from the console and sure enough, a 8003 event just occured. A reboot fixes the problem temporarily.

Any ideas? I've seen others with this problem out in cyberspace, but I can't find any answers.

Thanks!
A
ishmellAsked:
Who is Participating?
 
garyyConnect With a Mentor Commented:
I have had similar problems before and had to re-install the TCP/IP stack.
Maybe save this as a last resort if it's your server though.

Cheers
Gary
0
 
garyyCommented:
Disable browsing on the machine F921JK by changing

•     HKLM\SYSTEM\CurrentControlSet\Services\Browser\Parameters\MaintainServerList to No

This will stop the machine from maintaining a browse list and will stop it from forcing elections

Alternatively, set HKLM\SYSTEM\CurrentControlSet\Services\Browser\Parameters\IsDomainMaster to True for one machine (preferably a server) on each network segment.

Also make sure your routers do not forward UDP broadcasts as this is how the browser passes elections, which is what you are picking up

Hope this helps
Thanks
Gary
0
 
ishmellAuthor Commented:
I could do those things, but my concern is for the TCP stack. I'm not saying I can't browse the network... I'm saying the actual TCP stack no longer functions... which is much more severe. The difference is major in that, the browser alone only effects a single service, but a total loss of network connectivity completely cuts all network access of any kind to the server. My bet is that this is some kind of major issue and not simply a configuration problem... but I'm fishing anyways... maybe someone has come across this as a legit bug in MS software and can direct me to a patch.

I'll try the registry setting on the server though. Setting it per-machine is impractical because its not just F921JK causing elections... any number of the 80 workstations at this location could cause it to happen.

Routers are not forwarding any UDP/TCP to the internal LAN... and even if they were, this would again only effect the browsing service, not the network stack itself.

Thanks a lot for your input,
Amal.
0
 
Zaheer IqbalTechnical Assurance & ImplementationCommented:
0
 
ishmellAuthor Commented:
Thanks Gary... even though it's obvious, re-installing the TCP stack is something I've not done yet ;) I'll give it a try next time I'm on site and let you know how it goes.

Amal ;)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.