Vlans and nieghborhood

[jerry Bogren]

I have a split network. Part is on vlan1 the other on
vlan2. DNS is functional between vlans, that is I can ping
or use nslookup to resolve a DNS name and it is properly
resolved. It also works for aliases that is serverx
instead the FQN serverx.domain

symptoms: Network nieghborhood doesn't show computers on
the other vlan (either way) including domain
members/domain folder, UNC pathing between the vlans
doesn't work, and searching for a computer doesn't work.
Netbios is blocked at the Vlan border so no netbios.

Any Ideas on why unc and nieghborhood don't work?

 

[Marc Reynolds [MSFT]]

If you do not have a domain, you will not be able to browse across subnets.
If you have a domain (or domains) you will need Wins to browse across
subnets. NetBIOS should NOT be blocked as browsing is a NetBIOS function.
--

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[jerry bogren]

If you enable Netbios across the border:

What about Browser master conflicts and the
fimilar "browser elections"? Even the MS tech docs dealing
with Cisco IPhelper indicate these should be off.

I was under the impression that in W2k/w2k3 DNS was
suppose to surplant WINS and WINS was no longer needed?
Or does the subnet(Vlan)setup still require WINS.

Do I need to configure WINS?

 

[Marc Reynolds [MSFT]]

NetBIOS broadcasts should be blocked, NetBIOS unicast traffic should be
allowed.
Browsing is NetBIOS based, if you want to browse you need NetBIOS. If you
need to browse across subnets you need WINS.


--

Thanks,
Marc Reynolds
Microsoft Technical Support

This posting is provided "AS IS" with no warranties, and confers no rights.