Re: Master Browser List contains phantom domains

From: Doug Sherman [MVP] (dsherman_at_nospam.tampabay.rr.com)
Date: 11/04/04 

Date: Thu, 4 Nov 2004 10:51:02 -0500

Turning off the computer browser service prevents a machine from
participating in browser elections. Disabling this service does not prevent
a NetBios enabled computer from reporting its name, resources and
domain/workgroup membership.

For example, the NT 4.0 server you refer to is not a member of the domain.
Therefore, it is a member of a workgroup - perhaps with a workgroup name
identical to the NetBios name of a now defunct domain. This 'domain' will
appear in the browse list. If there are other workgroup computers connected
to the network, their workgroup name will continue to appear in the browse
list, and this could account for your problem.

Doug Sherman
MCSE Win2k/NT4.0, MCSA, MCP+I, MVP

"Terje Petersen" <TerjePetersen@discussions.microsoft.com> wrote in message
news:A68E3FEA-D380-45B0-9A06-3E9EC5A3D91B@microsoft.com...
> Hi,
>
> We have a domain spread across three sites.
>
> We run win2000/2003 servers and XP workstations. The domain is win2000
> native.
>
> There is one old NT4 server on the network but it is not part of the
domain.
> The "Computer Browser Service" on this server has been stopped.
>
> Over a year ago before we moved to active directory we had some other
> Domains on the network. These were removed over a year ago along with:-
>
> 1. All trust references to these domains.
> 2. All LMHOST references to these domains.
> 3. All WINS references to these domains.
>
> However despite all this these domains still show up in network
neighborhood.
>
> It has been suggested that we shut down every machine on the network
across
> three sites and then bring the entire network up from cold. This would be
> difficult to co-ordinate.
>
> The idea is that this would flush out any phantom entries in the Browse
> Master lists that keep propogating back into the browse list of other
> machines.
>
> Ideally I would like to disable the "Computer Browser Service" on all
> workstations so we only need to worry about co-ordinating a restart of the
> servers.
>
> Is there an easy way to disable this service on all workstations. I am
> thinking that Group Policy or a script might do it. Any guidance would be
> most helpful.
>
> Regards,
> Terje.
>
>
>
>
> --
> ~~~~~~~~~~~
> TERJE PETERSEN
> 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.788 / Virus Database: 533 - Release Date: 11-1-2004

Relevant Pages

  • Re: Master Browser List contains phantom domains
    ... browser service stopped for all workstations and let this run only on ... it is a member of a workgroup - perhaps with a workgroup name ... > to the network, their workgroup name will continue to appear in the browse ... >> Master lists that keep propogating back into the browse list of other ...
    (microsoft.public.win2000.networking)
  • Re: How to hide "workgroup" in network
    ... > Computers Near Me in My Network Places ... > "Removes computers in the user's workgroup and domain from lists of network ... > from lists of network resources, use the No Entire Network in My Network ...
    (microsoft.public.win2000.active_directory)
  • Re: Network file sharing
    ... When you open My Network Places, the computer list you see is obtaining from ... the master browser of your network. ... Net view command shows no lists or shows "System error 6118 has occurred. ... The list of servers for this workgroup is not currently available". ...
    (microsoft.public.windowsxp.general)
  • Re: My Network Places not up to date - Browse Server not working
    ... My Network Places is different to Network Neighbourhood on win9x. ... This is the list of computers in the workgroup, ... something called the NetCrawler which seeks out lists of shares on the ...
    (microsoft.public.windowsxp.network_web)
  • Re: Network Neighborhood
    ... > inability to browse by using Network Neighborhood in Windows 95 or Windows ... > communicated effectively with the other workgroup computers. ... > not have a common networking protocol, a common workgroup, and common user ... the computer that is running Windows ...
    (microsoft.public.win2000.networking)