"Not a master browser" warning
in [Windows Servers]
|
From: Jason on 7 Dec 2009 13:54 We have a Windows network with both Windows 2000 & 2003 servers, clients are XP with some Macs that authenticate logons within AD. Recently our "System" log file became full with the same error & warning messages over & over, they are: The warning message is: "The browser has received a server announcement indicating that the computer W2KSERVER2 is a master browser, but this computer is not a master browser." The error message is: "A duplicate name has been detected on the TCP network. The IP address of the machine that sent the message is in the data. Use nbtstat -n in a command window to see which name is in the Conflict state." I'm figuring that the 2 messages relate to the same problem, which is that we have 2 computers with the same name on our network. The "nbtstat -n" command doesn't give me much info & if I try 'net view' I get the error "System error 6118 has occurred. The list of servers for this workgroup is not currently available". Can anyone give any advice on how to troubleshoot this error?
From: Lanwench [MVP - Exchange] on 7 Dec 2009 17:06 Jason <SpamSpamSpam(a)SpanishInquisition.co.uk> wrote: > We have a Windows network with both Windows 2000 & 2003 servers, > clients are XP with some Macs that authenticate logons within AD. > Recently our "System" log file became full with the same error & > warning messages over & over, they are: > > The warning message is: > "The browser has received a server announcement indicating that the > computer W2KSERVER2 is a master browser, but this computer is not a > master browser." > > The error message is: > "A duplicate name has been detected on the TCP network. The IP > address of the machine that sent the message is in the data. Use > nbtstat -n in a command window to see which name is in the Conflict > state." > > I'm figuring that the 2 messages relate to the same problem, which is > that we have 2 computers with the same name on our network. The > "nbtstat -n" command doesn't give me much info & if I try 'net view' > I get the error "System error 6118 has occurred. The list of servers > for this workgroup is not currently available". > > Can anyone give any advice on how to troubleshoot this error? Got WINS? If you're not going to use WINS you should disable NetBT on all interfaces and disable/stop the computer browser service on all servers. If you're going to use WINS (I generally do, even nowadays) set your DHCP server to hand out the WINS address, the node type (0x8 for hybrid) and *still* stop/disable the computer browser service on all machines except the WINS box.
From: Dave Patrick on 7 Dec 2009 18:01 This article may help you sort it. http://support.microsoft.com/kb/315259 -- Regards, Dave Patrick ....Please no email replies - reply in newsgroup. Microsoft Certified Professional Microsoft MVP [Windows] http://www.microsoft.com/protect "Jason" wrote: > We have a Windows network with both Windows 2000 & 2003 servers, clients > are XP with some Macs that authenticate logons within AD. Recently our > "System" log file became full with the same error & warning messages over > & > over, they are: > > The warning message is: > "The browser has received a server announcement indicating that the > computer W2KSERVER2 is a master browser, but this computer is not a master > browser." > > The error message is: > "A duplicate name has been detected on the TCP network. The IP address of > the machine that sent the message is in the data. Use nbtstat -n in a > command window to see which name is in the Conflict state." > > I'm figuring that the 2 messages relate to the same problem, which is that > we have 2 computers with the same name on our network. The "nbtstat -n" > command doesn't give me much info & if I try 'net view' I get the error > "System error 6118 has occurred. The list of servers for this workgroup is > not currently available". > > Can anyone give any advice on how to troubleshoot this error?
|
Pages: 1 Prev: EventLog Error with ID=1 from source=Virtual Disk Service Next: no internet - |