MRxSmb EventID 8003

It is not really an issue. The only problem is that you'll have some extra network traffic due to Windows Master Browser elections.

There are some different possible causes. Check the following link and see what applies to your situtation

http://www.eventid.net/display.asp?eventid=8003&eventno=680&source=MRxSmb&phase=1

Solution:

Stage one:

- Add, edit or modify the current registry key on the server you wish to be the Master Browser:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters]
"IsDomainMaster"="TRUE"

- The most common scenario is that your DCs be the Master and Backup browsers. Preferrably the Master Browser being the server with the PDC role.

- Make sure that all other DC's in the domain either have no such entry or "FALSE" as the "IsDomainMaster" value.

Stage two:

1) Find the master browsers. In the Windows 2000 Resource Kit comes a tool called "Browser Monitor". Use this tool to identify which machines are currently the master browser and backup browser.

2) Eliminate the unwanted master browsers: The tool will list all computers that can be elected for master. The blue icon will identify the current Master Browser, the red icons represent possible master or backup browsers.

3) If the blue icon is not the master browser you wanted, then you must remove it from the list. How? For Windows NT/2000/XP machine, simply Disable the Computer Browser service. For Samba servers, you must contact the administrator for the Samba machines (in other words, I don't know how.. hehe).

4) Restart the Computer Browser service on your PDC and start back at step one. Continue to do so until you've eliminated all the possible master browsers. When all the master browsers have been eliminated, the problem should go away.