Master Browser List accros subnets

Is there a way to isolate the Master Brower list within each subnet with only
one domain? Example:

70 different subnets all log into mydomain.local. When browsing network
neighborhood from any subnet, you can see all computers from all subnets
instead of computers from that subnet only. The only thing I can find to
eliminate this is to disable the browser service or to have seperate domains
for each location (subnet). Any ideas?? Could this be restricted at the
router?

Thanks
Doug

"Doug" <(E-Mail Removed)> wrote in message
news:0D5DCF3D-D66D-4B95-9F7F-(E-Mail Removed)...
> Is there a way to isolate the Master Brower list within each subnet with
only
> one domain? Example:

There is no relationship to the Browse Lists and subnet,..except that each
subnet has a Master Browser which then passes its data to the Domain Master
Browser. The List ultimately comes from the Domain Master Browser wich is
only concerned with Domain,..not subnets.

> 70 different subnets all log into mydomain.local.

Subnet don't log into Domains, computers do,..what subnet they are in is
irrelevant.

>The only thing I can find to eliminate this is to disable the browser
service

No you don't. It will simply cause an "election" which will produce a new
master brwoser to replace it from another machine.

> or to have seperate domains for each location (subnet).

That is the only way I know to do it. The "boundary" of a Browse List is the
Domain. Having 5 Domains means you have 5 Domain Master Browsers thereby
giving 5 separate Lists.

>Any ideas?? Could this be restricted at the router?

No. Routers create subnets. Subnets are irrelevant. Routers can kill
Network Browsing by preventing the subnet's Master Browsers from contacting
the Domain Master Browser, but what good would that do?
--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

BTW - I don't recommend creating multiple Domains just to keep the Browse
Lists small. I only meant that it would work. Modern Active Directory
Domains were meant to follow the model of using a minimal number of Domains
or even just one large Domain.

I believe MS envisions a future where there isn't even a Browse Lists at
all, this was an old Netbios-Based NT4.0 technology that may eventually be
eliminated.

It doesn't make sense to increase the complexity and make manageability more
difficult over something that is so trivial as how many machines show in a
Browse List. Many Admins don't want user to be able to browse the network
at all. You can use Shortcuts with UNC paths that users can use to navigate
to specific machines and never have to open "Network Places".

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

Phil,

Thanks for your advice. I didn't mean that the subnet logs into the domain.
What I meant to say was, user's in each subnet log into one domain. I agree
with everything you said and that is why I am posting for some other
possibilities. It takes for ever for 10000+ workstations to show up in
network neighborhood. We want to access them either through
\\computername\sharename (through explorer, etc) or try and limit the browser
list to each individual subnet.

Thanks for your feedback.
Doug

"Phillip Windell" wrote:

> BTW - I don't recommend creating multiple Domains just to keep the Browse
> Lists small. I only meant that it would work. Modern Active Directory
> Domains were meant to follow the model of using a minimal number of Domains
> or even just one large Domain.
>
> I believe MS envisions a future where there isn't even a Browse Lists at
> all, this was an old Netbios-Based NT4.0 technology that may eventually be
> eliminated.
>
> It doesn't make sense to increase the complexity and make manageability more
> difficult over something that is so trivial as how many machines show in a
> Browse List. Many Admins don't want user to be able to browse the network
> at all. You can use Shortcuts with UNC paths that users can use to navigate
> to specific machines and never have to open "Network Places".
>
> --
>
> Phillip Windell [MCP, MVP, CCNA]
> www.wandtv.com
>
>
>

"Doug" <(E-Mail Removed)> wrote in message
news:A70FEE06-0AFC-42DA-AB6F-(E-Mail Removed)...
> Thanks for your advice. I didn't mean that the subnet logs into the
domain.
> What I meant to say was, user's in each subnet log into one domain. I
agree
> with everything you said and that is why I am posting for some other
> possibilities. It takes for ever for 10000+ workstations to show up in
> network neighborhood. We want to access them either through
> \\computername\sharename (through explorer, etc) or try and limit the
browser
> list to each individual subnet.

OK, I see. Well, I don't think you can limit it by subnet that way.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

"Phillip Windell" <@.> wrote in message news:
> > Thanks for your advice. I didn't mean that the subnet logs into the
> domain.
> > What I meant to say was, user's in each subnet log into one domain. I
> agree
> > with everything you said and that is why I am posting for some other
> > possibilities. It takes for ever for 10000+ workstations to show up in
> > network neighborhood. We want to access them either through
> > \\computername\sharename (through explorer, etc) or try and limit the
> browser
> > list to each individual subnet.
>
> OK, I see. Well, I don't think you can limit it by subnet that way.
>

You can acheive this by having the domain master browser acting
as the router on each subnet.

"Michael Giorgio - MS MVP" <(E-Mail Removed)> wrote in
message news:(E-Mail Removed)...
>
> "Phillip Windell" <@.> wrote in message news:
> > > Thanks for your advice. I didn't mean that the subnet logs into the
> > domain.
> > > What I meant to say was, user's in each subnet log into one domain. I
> > agree
> > > with everything you said and that is why I am posting for some other
> > > possibilities. It takes for ever for 10000+ workstations to show up in
> > > network neighborhood. We want to access them either through
> > > \\computername\sharename (through explorer, etc) or try and limit the
> > browser
> > > list to each individual subnet.
> >
> > OK, I see. Well, I don't think you can limit it by subnet that way.
> >
>
> You can acheive this by having the domain master browser acting
> as the router on each subnet.

You mean a "Multi-Homed Master Browser"? I thought those were a disaster
waiting to happen.

191611 - Symptoms of Multihomed Browsers
http://support.microsoft.com/default...b;EN-US;191611

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com

"Phillip Windell" <@.> wrote in message news:
> "Michael Giorgio - MS MVP" <(E-Mail Removed)> wrote in
> message news:> >
> > "Phillip Windell" <@.> wrote in message news:
> > > > Thanks for your advice. I didn't mean that the subnet logs into the
> > > domain.
> > > > What I meant to say was, user's in each subnet log into one domain.
I
> > > agree
> > > > with everything you said and that is why I am posting for some other
> > > > possibilities. It takes for ever for 10000+ workstations to show up
in
> > > > network neighborhood. We want to access them either through
> > > > \\computername\sharename (through explorer, etc) or try and limit
the
> > > browser
> > > > list to each individual subnet.
> > >
> > > OK, I see. Well, I don't think you can limit it by subnet that way.
> > >
> >
> > You can acheive this by having the domain master browser acting
> > as the router on each subnet.
>
> You mean a "Multi-Homed Master Browser"? I thought those were a disaster
> waiting to happen.
>
> 191611 - Symptoms of Multihomed Browsers
> http://support.microsoft.com/default...b;EN-US;191611
>
Only to someone who wants to browse all subnets. <g>

"Michael Giorgio - MS MVP" <(E-Mail Removed)> wrote in
message news:(E-Mail Removed)...
> > > You can acheive this by having the domain master browser acting
> > > as the router on each subnet.
> >
> > You mean a "Multi-Homed Master Browser"? I thought those were a
disaster
> > waiting to happen.
> >
> > 191611 - Symptoms of Multihomed Browsers
> > http://support.microsoft.com/default...b;EN-US;191611
> >
> Only to someone who wants to browse all subnets. <g>

Ah! I see...

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com