Re: can't browse network accessed via VPN

From: Bill Grant (not.available_at_online)
Date: 12/10/04


Date: Fri, 10 Dec 2004 16:42:38 +1100


  You can sometimes get an (incomplete) browse list when you first connect,
but that is a fluke. When the browser settles down, it tells you (correctly)
that it can't find the browse master.

    The remote clients will not appear in the LAN browse list. Browse lists
are built by broadcasts, and these don't normally cross routers or WAN
links.

    If you were using a site-to-site VPN, browsing would be possible because
you would have a segment master browser at the remote site. But here again
it only works with a domain. Only a PDC can merge browse lists to give you a
network-wide list.

"Gary Roach" <jgroach@NOSPAMcogeco.ca> wrote in message
news:OYyc%23Nk3EHA.2288@TK2MSFTNGP11.phx.gbl...
> it's a workgroup i'm trying to browse. interesting that since i posted, a
> windows 98 VPN client produced a browse list. it included XP clients from
> the local LAN and the server that runs the WINS server but not the XP
> remote client that's also connected via a VPN. the XP client still gives
> an error when i try to browse, but i can connect to shares on the LAN
> using UNC with netbios names.
>
> "Michael Giorgio - MS MVP" <Michael.Giorgio@NoSpam.mayerson.com> wrote in
> message news:OYG9cDg3EHA.3820@TK2MSFTNGP11.phx.gbl...
>> If you don't have a domain in either location you will not be
>> able to get this to work. You cannot browse remote workgroups
>> without the presence of a DMB or domain master browser. The
>> PDC or PDC emulator (W2k or higher) by default is always the
>> DMB which is responsible for querying remote segments to get
>> their local browse list.
>>
>> Having said all that if you have a domain in place attempt to map
>> to a share from the remote location to the W2k3 server and vice
>> versa. If the drive map fails post the exact error.
>>
>> "Gary Roach" <jgroach@NOSPAMcogeco.ca> wrote in message news:
>>> I'm connecting to a network over a VPN. the VPN is hosted by a machine
>>> running server 2003. it's also running a WINS server. the machine is a
>>> stand-alone server. on the vpn client machine, i get the WINS address
>> of the
>>> WINS server correctly and i can ping internal machines using netbios
>> names.
>>> however, i cannot browse the network using the vpn client. when i
>> click
>>> "view workgroup computers", i get the error:
>>>
>>> workgroup is not accessible. you might not have permissions to use
>> this
>>> network resource.
>>
>>
>
>



Relevant Pages

  • Re: cant browse network accessed via VPN
    ... you would have a segment master browser at the remote site. ... Only a PDC can merge browse lists to give you a ... > remote client that's also connected via a VPN. ...
    (microsoft.public.windows.server.networking)
  • Re: cant browse network accessed via VPN
    ... you would have a segment master browser at the remote site. ... Only a PDC can merge browse lists to give you a ... > remote client that's also connected via a VPN. ...
    (microsoft.public.windowsxp.network_web)
  • Re: to WINS or not to WINS
    ... browser service can contact the Domain master browser the browser service ... > The basic problem is that the lists you see in NN are built by ... > The situation is different for a dialup client. ... > the right domain name and can find the domain master browser. ...
    (microsoft.public.win2000.ras_routing)
  • Re: to WINS or not to WINS
    ... browser service can contact the Domain master browser the browser service ... > The basic problem is that the lists you see in NN are built by ... > The situation is different for a dialup client. ... > the right domain name and can find the domain master browser. ...
    (microsoft.public.win2000.networking)
  • Re: PDC and Browsing with Cisco VPN
    ... browser by doing a name server request for. ... The remote user will query its local SMB or segment ... The PDC by default will act as the SMB for it's given ... >> lists, then uses WINS and a Netbios port to merge them. ...
    (microsoft.public.windows.server.networking)