trading10
asked on
Master Browser error in Event Log of Server 2003 (NO DOMAIN - only workgroup)
We have 25 XP Pro workstaions and a Windows Server 2003 that is NOT setup as a domain controller. We have one workgroup.
We are working on using Hamachi VPN to connect an XP Pro desktop that is at another building. With Hamachi VPN, we have been able to map two network drives and run applications that have their data stored on the 2003 Server.
I've been watching the Server 2003 event log, and found the following error:
"The master browser has received a server announcement from the computer LONGVIEW that believes that it is the master browser for the domain on transport NetBT_Tcpip_{2076F820-99DB
"Longview" in this case is the desktop at the new building that is connected to the network with Hamachi VPN.
I don't know exactly what this error message means, but I'm concerned that browsing the network at our primary location could become very slow if their machines are trying to obtain a list of computers across the VPN connection to the Longview desktop.
Changing the Server 2003 to a domain controller is NOT an option.
Am I correct in my concern about browser elections? Is there something I can do to ensure the Server 2003 is the Master Browser?
We are working on using Hamachi VPN to connect an XP Pro desktop that is at another building. With Hamachi VPN, we have been able to map two network drives and run applications that have their data stored on the 2003 Server.
I've been watching the Server 2003 event log, and found the following error:
"The master browser has received a server announcement from the computer LONGVIEW that believes that it is the master browser for the domain on transport NetBT_Tcpip_{2076F820-99DB
"Longview" in this case is the desktop at the new building that is connected to the network with Hamachi VPN.
I don't know exactly what this error message means, but I'm concerned that browsing the network at our primary location could become very slow if their machines are trying to obtain a list of computers across the VPN connection to the Longview desktop.
Changing the Server 2003 to a domain controller is NOT an option.
Am I correct in my concern about browser elections? Is there something I can do to ensure the Server 2003 is the Master Browser?
This hotfix also might be applicable to your situation:
http://support.microsoft.com/kb/843517/en-us
http://support.microsoft.com/kb/843517/en-us
Nice Hotfix, Hypercat:
In your experiece with this hotfix:
So, this takes care of Vista clients trying to overtake the domain master because they have a newer OS?
Will this also take care of Unix boxes that think they are the domain master?
In your experiece with this hotfix:
So, this takes care of Vista clients trying to overtake the domain master because they have a newer OS?
Will this also take care of Unix boxes that think they are the domain master?
Hmmm - good question. The only experience I have is with Windows XP boxes using RRAS. It worked for me with that situation, but I haven't tried it with the other scenarios you're looking at. I would think it would work, though, based on the fact that it is designed to give the member server preference in a master browser election, similar to the way DCs function.
trading10
I would try the hotfix as hypercat recommended, first:
It sounds like this redefines the browser election registry keys for you.
If this doesn't resolve your issue, give my suggestion a shot.
I would try the hotfix as hypercat recommended, first:
It sounds like this redefines the browser election registry keys for you.
If this doesn't resolve your issue, give my suggestion a shot.
ASKER
I just read over the hotfix, and will try installing it tonight after all users have logged off.
I'll let you guys know the outcome, and award points appropriately.
Thanks a lot for the quick responses - I really need to make sure this doesn't become an issue.
I'll let you guys know the outcome, and award points appropriately.
Thanks a lot for the quick responses - I really need to make sure this doesn't become an issue.
ASKER
Hm, there are two files contained in that Hotfix. Not sure what the difference is though. Anyone know? 32bit vs 64bit??
Here are the filenames:
WindowsServer2003-KB843517
WindowsServer2003-KB843517
Install both?? Yikes - filenames could be a little clearer.
Here are the filenames:
WindowsServer2003-KB843517
WindowsServer2003-KB843517
Install both?? Yikes - filenames could be a little clearer.
The "Symbols" file installs some necessary information for diagnostics and troubleshooting. It is not absolutely necessary to install it, but it helps if you experience any problems related to the patch. If you don't install it and an error occurs, you might get one of those weird event log errors that says something like "this computer does not have the necessary information to display the error message."
ASKER
Well, it turns out that the Hotfix won't install.
When you run it, it errors out with Setup has detected that the service pack installed on this system is newer than the Hotfix'.
Opinions??
When you run it, it errors out with Setup has detected that the service pack installed on this system is newer than the Hotfix'.
Opinions??
That means that your server must have SP2 on it and that hotfix is probably included in SP2. One point that I think we didn't get across is that there is no harm in the "forced election" message coming up as long as the workstation doesn't win the election. A workstation on its own with no network connection will automatically be its own master browser, and when it connects to a remote network and becomes a member of that workgroup, it will cause that message to appear. It will only cause problems if the remote workstation does in fact become the master browser for your workgroup. Have you seen any evidence that this is happening?
ASKER
I found an application called Browse Master Monitor that identifies which machine on the network is currently the browse master, and it is showing that a local workstation is browse master right now instead of this member server 2003. Strangely, it also shows the remote system that is connected via VPN as a browse master. I'm confused by this application's results because I think there should be only one browse master on the entire network regardless of whether its local or remote/VPN.
The only way I can think of to change this is to have all users reboot so that the server becomes browse master again. I'm not sure that would necessarily work either. Of course, that is not a convenient way to handle this situation.
When I posted this question here, I was anticipating that there would be a command line method of forcing the Server 2003 to become the browse master again. I have not found any such command line app to do this though.
The only way I can think of to change this is to have all users reboot so that the server becomes browse master again. I'm not sure that would necessarily work either. Of course, that is not a convenient way to handle this situation.
When I posted this question here, I was anticipating that there would be a command line method of forcing the Server 2003 to become the browse master again. I have not found any such command line app to do this though.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
http://www.microsoft.com/resources/documentation/windowsnt/4/server/reskit/en-us/net/chptr3.mspx?mfr=true
This is an NT4 article. There is only a very slight difference between NT4 and 2003 server. That would be the registry keys to define who the domain master browser is:
For NT4 the key is "isdomianmasterbrowser"
For 2003 server the key is "isdomainmaster"
__________________________
What is happening is you have a machine on your network that has won the browser election. So, it is taking over the domain master's role to hold the browse list. What symptoms you will see is you may not have a full ilst of clients in "My Network Places". Then, you may not be able to browse the client or easily map to the computer name.
What you will need to do is disable that client from becoming a domain master browser. You can do this by registry keys.
If you have any questions, please let me know. That article should guide you well.