Re: Virtual LAN Problem
- From: "Bill Grant" <not.available@online>
- Date: Tue, 17 Jan 2006 12:52:29 +1100
Browsing across subnets will not work without WINS, as Phillip has
already pointed out. Network Neighborhood is driven by the computer browser
service. The computer browser service uses Netbios names and broadcasts to
build browse lists. Broadcasts do not normally cross routers on WAN links
(and shouldn't either).
To get browsing working across routers you need WINS. The browser
service needs WINS to allow browse masters to find other browse masters
across routers. They use WINS to convert names to IP addresses so they can
contact them without broadcasting.
You would only need one WINS server on your network and ALL machines
should be set up as WINS clients so that they register with WINS.
If just installing a WINS server and making all machines WINS clients
doesn't get browsing working, you will need to start troubleshooting the
browser service. See KB 188305 . But give it an hour or two before you
panic. It takes a while to get started.
kysiow wrote:
> Hi!;
>
> If I want to browse all the different V-LAN PC from network
> neighborhood. What should I do?
>
> Thanks & Regards
>
> "Phillip Windell" wrote:
>
>> Network Neighborhood does not work across subnets with a WINS
>> Server. That is the purpose of a WINS Server.
>>
>> --
>> Phillip Windell [MCP, MVP, CCNA]
>> www.wandtv.com
>>
>>
>> "kysiow" <kysiow@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
>> news:47990F69-D995-477D-A71F-5567CC5EDE13@xxxxxxxxxxxxxxxx
>>> Hi!;
>>>
>>> My company have setup 2 Virtual LAN. The purpose to setup 2 virtual
>>> LAN due to PC amount of my company too many (more than 254 units).
>>> So we need to separate the network to 2 virtual LAN. However we
>>> still want let 2 different virtual LAN PC can direct communicate
>>> each and other. We bought the 3Com SuperStack 3226 layer 3
>>> management switch to do the job. The switch can create virtual LAN
>>> and does the ip routing among different Virtual LAN. However one
>>> problem I faced out is I can not browse one of the V-LAN groups PC
>>> from network neighborhood or my network places. For instance I have
>>> 2 group of V-LAN. One group using 192.168.7.xxx and another group
>>> using 192.168.8.xxx. However what I wondering is the users of
>>> 192.168.8.xxx can browse all the diffrent V-LAN PC in the network
>>> using network neighborhood or my network places. However for users
>>> of 192.168.7.xxx only can view the PC that belongs to same V-LAN
>>> group. However the 192.168.7.xxx users can ping and search the user
>>> that belongs to 192.168.8.xxx with using dns name or ip. But they
>>> can't browse the PC for that belongs to 192.168.8.xxx. I have
>>> checked the 3 Com management system configurations setting. I
>>> didn't find any mistake. I have setup DNS and Wings properly on my
>>> server, so it should be no problem. However I still faced out this
>>> wondering problem. So any one got the idea to solve this kind of
>>> problem.
>>>
>>> Thanks & Regards
.
- Follow-Ups:
- Re: Virtual LAN Problem
- From: Bill Grant
- Re: Virtual LAN Problem
- Prev by Date: Re: routing problem
- Next by Date: Re: Virtual LAN Problem
- Previous by thread: Netdiag.exe hangs
- Next by thread: Re: Virtual LAN Problem
- Index(es):
Relevant Pages
|
