Not really. They should not be using the RAS interface for this.
Browsing goes haywire if a browser has multiple interfaces. It tries to
build browse lists on both interfaces, and there is no way to merge those
lists. So you can't have one browse list for the segment that contains just
the remote client and the RRAS server's LAN IP, and a separate browse list
for the LAN machines and the server's LAN IP.
To browse the LAN, the remote client needs to get the same browse list
as the LAN clients. So the clients need to see the browse list for the LAN
interface. If you are running WINS, this should all work fine. The remote
will get the Domain Master Browser's IP from WINS and get the browse list
using that.
<(E-Mail Removed)> wrote in message
news:047701c3c5c1$dc1ec570$(E-Mail Removed)...
> Will that prevent remote clients from being able to browse
> the network?
>
> >-----Original Message-----
> > Yes. See KB 292822, especially the bit about
> disabling Netbios over
> >TCP/IP on the RAS interface.
> >
> ><(E-Mail Removed)> wrote in message
> >news:151d901c3c40b$2d593050$(E-Mail Removed)...
> >> Hey,
> >>
> >> I have a 2003 Server, the only AD server in my domain.
> I
> >> have setup RRAS as a VPN server using the only network
> >> adapter installed in the server. VPN works great, but
> now
> >> periodically users cannot browse the network. In
> >> researching the problem, I see that one of the PPP/SLIP
> >> adapters (VPN) is registered in WINS as the Master
> >> Browser. Users cannot browse because the IP address of
> >> the PPP/SLIP adapter is not accessible, therefore the
> >> browse master is not available. An election is forced,
> >> but naturally the DC wins the election and continues as
> >> the browse master. Is there a way prevent the PPP/SLIP
> >> adapters from registering in WINS, or for the Browse
> >> Master to an adapter?
> >>
> >
> >
> >.
> >
|