master browser for the domain

amanz,
       This due to the browser election taking place in your network. Probably your server is trying to force an election in the network after finding that there are no Master Browser.
      Now the Master Browser is the server which collects all the information about the network servers and resources and  distributes to the clients which they can see using their network neighbourhood ( browse list )
      When a client comes up it searches a master browser for a list of backup browsers and then it queries one of the backup browsers for the browse list


         In ur case ur server didn't find a master browser hence believes that he can be a master browser and so forces an election to find any challengers!!!
 Interesting  isn't it...
            Regards,
            Shibu

If you’re seeing this message every 12 minutes, it’s probably because you have UDP forwarding enabled on your routers or VLANs.  This can tie into DHCP Helper addresses, if you’re using them.  Here is the technet article that describes the problem.

Article ID: Q135464

Or

http://support.microsoft.com/support/kb/articles/Q135/4/64.asp?LNG=ENG&SA=ALLKB&FR=0

Is FILESERVER a member of the DOMAIN on the PDC?

I suspect that FILESERVER and PDC are on different physical segments, otherwise you wouldn't get this message as the PDC would win the election hands down.
I expect that you also have a multihomed server.

Look at :

http://support.microsoft.com/support/kb/articles/Q158/4/87.asp

....issue should be resolvable by installing WINS throughout.

Check your subnet masks match on both servers, we had this on a site with single subnet and couldn't reboot so set isdomainmatser off instead of changing the mask.
http://support.microsoft.com/support/kb/articles/Q143/1/53.asp

no good answer.

This question has a deletion request Pending

This question no longer is pending deletion

amanz> no good answer.
Well what do you expect if you do not give us any idea of your topology, there are any number of reasons for this event to be logged, any one of us could fix it if you'd only give us some feedback.

Check the subnet mask of "Fileserver" and ensure that your routers are set not to forward UDP broadcasts, but as I read back through, I see that these suggestions were made, did you try them? Little help here pal.

In TCP/IP networks, there are 2 distinct types of master browers:  the domain master browser and the segment master browser.  The PDC is always supposed to be THE domain master browser and the winner of the election in each segment becomes the segment master browser for it's segment.  The segment master browsers keep a list of all NT, 95, 98, ME + 2000 machines in it's segment and then pass that on to the domain master browser.

If a computer in a particular segment has it's registry value for MAINTAIN BROWSE LIST enabled, it can then be a backup master browser for it's segment if not the segment master browser.  Microsoft tech support claims that this value refers to domain master browser but that doesn't make sense because according to Microsoft, O N L Y the PDC can be the domain master browser.

We recently experienced a problem where other machines on our WAN (including machines on the local LAN where the PDC is located) were becoming the domain master browser.  When that happened, the network neighborhood on a machine would only show the machines in it's subnet (which is the list maintained by the segment master browser.)

When all this was going on, TCP/IP on the network was working perfectly and we could ping any machine that we could not see in the network neighborhood.  By logging into our WINS server and running WINS ADMIN, we could see which machine was showing up as the domain master browser.  We then set it's MAINTAIN BROWSE LIST registry value to FALSE, restarted that machine and restarted the PDC.