hello all, i seem to have an issue that i can't figure out. i have a client that has been running an NT network for the past several years and recently decided it was time to move to 2000. previous setup included NT Server (as a pdc mainly for file and print sharing), NT Workstations, and a couple of 98 & ME Workstations. everything was working fine but the server is about to lose a hard drive. so the new setup is to move the pdc and file and print sharing to the new 2000 box. there is one NT workstation that is causing problems. on the NT server i would frequently get the following message: Event ID: 8003, Source: Rdr, "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." not a big deal right? just a forced election and the pdc always wins. well when i tried moving this particular NT workstation to the new pdc (with a different domain name to avoid setup of a domain tree since the NT server is getting scrapped anyway) i get the following error message on the workstation: "The domain controller for this domain cannot be located" and in the event log: Event ID: 7023, Source: Service Control Manager, "The service terminated with the following error: not enough server storage space..." Event ID: 7001, Source: Service Control Manager, "The computer browser service depends on the service which failed to start because of the following error: not enough server storage space..." wierd, right? and i get the same message on the 2000 server after trying to connect to the new domain: Event ID: 8003, Source: MRxSMB, "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." and i know that the NT workstation can see the new 2000 server because i can browse the network from either the workstation or server and see both computers listed. i can share files between them (using the ip address, but not the computer name) and all the other NT workstations had no problems connecting with the exact same setup. what i have tried so far: completely removing and reinstalling the newtork card and all network services in the NT workstation and reinstalling service pack 6a. i can disconnect and reconnect to the old domain fine, but just can't get connected to the new domain. any ideas... anybody... ???

Try trusting the old NT server.

since you are scrapping the nt server there is no point in a trust to solve a workstation wanting to grab master browser. I would suggest you remove any file and print sharing or disable it in the NT wkstation. Check the registry on the workstation and find the key "isdomainmaster" and that it is set to "false". There are more then one entry so make sure you search thru. Does the rdr error only occur when the wkst is booted/rebooted? If it happens when the station is just sitting there then replace the nic. Intermittent nic and/or switch/hub port failures will cause elections.

I've had similiar problems with Windows XP Professional PC's that want to be the master browser. I discovered a simple regestry hace over at EventID.com that seems to fix the problem In order to stop this error from occuring, use Regedit and set the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters\MaintainServerList from Auto or YES to FALSE This will prevent the computer from attempting to become a Domain Master Browser and compete with Domain Controllers. If the server is a domain controller it is advisable to leave it with the default settings. Also, it seems that Cisco routers can contribute to this problem. Look and see if you have a NT 4.0 domain controller is hosting DHCP and a Cisco router that has IP helper statements that point back to the DHCP server. The default IP helper setings cause master browser elections. Hope this helps!