This is due to misconfiguration of systems or switches.
The master browser has received a server announcement from the computer that believes that it is the master browser for the domain on transport. The master browser is stopping or an election is being forced.
This problem can be caused by a server or client thinking it has to be the master browser. This is delivered by the source MrxSmb.
This can be changed by a registry setting.
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesBrowserParametersMaintainServerList" to NO. You can also change the "IsDomainMaster" entry on the domain controllers and changing the key to TRUE. This gives an extra boost for the election process and helps ensure the domain controllers retain the master browser status. The previous key from above can be set to Yes on the DCs.
You can also stop the browser service on the system causing the problem.
This error can also be caused when routers or switches are misconfigured and propagate UDP port 137 and 138 broadcasts. You might find a large numbers of event ids 8003 appear in the event log.
Disclaimer:The information provided in this document is intended for your information only. Lubby makes no claims to the validity of this information. Use of this information is at own risk!
About the Author
Author: Wim Peeters - Keskon GmbH & Co. KG
Wim Peeters is electronics engineer with an additional master in IT and over 30 years of experience, including time spent in support, development, consulting, training and database administration. Wim has worked with SQL Server since version 6.5. He has developed in C/C++, Java and C# on Windows and Linux. He writes knowledge base articles to solve IT problems and publishes them on the Lubby Knowledge Platform.