VLANS and NT

[Guest_imported]

I have multiple VLANS which are configured at switch level and dhcp ranges for each VLAN. My PDC is being bombarded with requests from Workstations claiming to be the master browser. Microsoft says that this is becuase they are on same subnet. Is there anyway I can get rid of these requests without having to get rid of VLANS ?

 

[wybnormal]

Those nasty master browser election wars... they mostly stem from MS providing a legacy support structure.

VLAN1---------|--|
VLAN2---------|SW|
VLAN3---------|--|-----------( network )

Each vlan has a different "range" or "subnet"?

VLAN 1 = 192.178.1.x
VLAN 2 = 192.178.2.x and so ?

The master browser wars start because the client can not get it's updated list from who it thinks is the MB. So it forces an election which is broadcast based. I find MS's answer disturbing since their software was originally designed for flat networks so it should be better if they are on the same subnet. But the VLANs should want different ip subnets in order to function correctly.

<snipped from Cisco's white paper>
Microsoft developed the LAN Services Browser to enable the user to browse a list of all computers available on the network. Each Windows Networking client registered its NetBIOS name periodically by sending broadcasts.

Every computer also had to send broadcasts to elect a browse master for the network. The browse master (and several backup browse masters) maintained the list of computers and their addresses. When a user browsed the network, the client sent a broadcast request and one of the browse masters responded.

<<snip>>

The actual white paper:

http://www.cisco.com/warp/public/473/winnt_dg.htm

There are a few ways to kill this.. accesslists on the router between the VLANs.. some reg hacks on the NT/98 side and so on. But more info is needed

MikeS


&quot;Diplomacy; the art of saying 'nice doggie' till you can find a rock&quot; Wynn Catlin

 

[Guest_imported]

Mike,

Yes each VLAN is different...

192.168.1.x
192.168.2.x

I assumed that each NT 4 spa 6.0 machine would contact the domain controller as the master browser. I suppose this isnt the case ???

What info do you need ?

Thanks