Browse lists are not really associated with DHCP on DNS and only
indirectly with WINS. They are built by the computer browser service and
rely on Netbios names and LAN broadcasts.
Once you split your network with IP routers, you block broadcasts
between subnets. Each segment builds its own browse list. You will only get
a nework-wide browse list if
1. You have at least one DC. Only a DC can merge browse lists.
2. You have some way for the browse masters to communicate across the
router. WINS should do this for you as long as all machines in both subnets
register with the same WINS server.
The standard tool for troubleshooting browser problems is browstat from
the system tools. There is a troubleshooting guide in KB 188305 .
"VIDRO" <(E-Mail Removed)> wrote in message
news:E1995994-0228-4352-8A0C-(E-Mail Removed)...
> Naming /browsing problem.
>
> This would appear to be a simple problem but my brain is just not able to
> think threw it to get the correct solution.
>
> I have a DNS server and a WINs server on subnet 192.168.1.x
> I have DHCP server on subnet 192.168.20.x that references the DNS and WINs
> server on subnet 192.168.1.x
>
> The users on subnet 192.168.20.x can see through the browser the machines
> on
> subnet 192.168.1.x BUT the users on subnet 192.168.1.x CANNOT see the
> users
> on 192.168.20.x,
> What do I need to do to get both sides to see each other on the brows
> list?
> I would like to do this with having to drop a LMHOST file on a bunch of
> computers.
>
>
> Clients on both subnets can "ping" each other and the "net view" command
> has
> positive results.
>
|
Similar Threads
Linear Mode
