You need to prevent the WAN interface from registering in DNS and/or
WINS. You also need to prevent the "virtual" IP from registering if the
server is a remote access server. Your server should only be known by its
LAN IP.
See KB 292822 for a discussion of the browsing/DNS problems that arise
if a DC server has multiple interfaces.
Browsing across a WAN link is pretty tricky. The browse masters need to
be able to communicate using the special Netbios names for master browsers.
(The segment master browser does not have to be a server. At the main
office, the DC is automatically the domain master browser). See KB 117633
and 150800. It should work OK if machines in both sites are registering with
WINS.
"User" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> We have a small office with a Win2K server-DNS,DHCP,Wins. In the office
we
> have winxp PC's. We've been experiencing problems browsing the network
from
> the workstations. From the server we can browse the network and see all
the
> pc's fine.. On a PC I can the net view and teh result is: there are no
> entries.. If I type net view \\pc1 I can see the shared resources on
> that pc.. or any other on the net..
>
> The other part of this is:
> we have a remote office with no server- that is connected via wan- 'h/w
> firewalls at each location' We have the same results browsing across the
> wan link. I've noticed that the WAN ppp adapter (on the server) registers
> its ip address in DNS as a host record, in addition to the local net ip.
Is
> this correct? or should the wan tcp/ip option to register this in dns be
> cleared?
>
>
|