The browse list is built by the computer browser service. It builds the
browse list using LAN broadcasts. Most routers block these broadcasts, so
you won't see machines in a different subnet.
Browsing across routers requires two things. The first is at least one
DC. Only a domain controller has the software necessary to build a network
wide browse list. The second requirement is a way to resolve browser special
names to IP addresses (so that they can find other browsers across routers).
For all practical purposes that means a WINS server. (It is theoretically
possible to do it with LMHOSTS entries).
"Mike" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
>I have a server running windows 2003 server (standard), this server
> runs my Veritas Backup Exec. I can't see my pc's, that are in a
> different subnet in BE. I called Veritas and that noticed that Windows
> can't browse to these pc's either. What networking function (??)
> populates the browse in windows when you are trying to map a drive. I
> don't know much about networking, this subnet was setup by our
> networking group.
>
> Thanks for any help
> Mike
>
|