Re: can't browse network accessed via VPN

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

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

  • Next message: Richard G. Harper: "Re: Disk device"
    Date: Sat, 11 Dec 2004 11:06:43 +1100
    
    

       That about sums it up. Without a domain and without WINS you have to fall
    back to lmhosts files and no browsing. This applies to a routed network too,
    not just remote users.

    "Gary Roach" <jgroach@NOSPAMcogeco.ca> wrote in message
    news:eiF3siu3EHA.3596@TK2MSFTNGP12.phx.gbl...
    > what you're telling me is consistent with what i've experienced. i've been
    > doing tests on a test LAN on which i've got a windows server 2003 server.
    > this is why i tried to use WINS - because i had the ability to easily
    > install it. ultimately, the LAN i'll be connecting to is workgroup of XP
    > Pro machines with no WINS server (unless the router happens to have that
    > capability - i don't know yet). in this environment i won't be able to
    > resolve netbios names at all for the dial-up clients unless i can somehow
    > maintain hosts or lmhosts files on the vpn client machines. the only way
    > to do it automatically would be to enable global broadcasts to the vpn
    > clients. i tried adding the 255.255.255.255 route to the routing table but
    > "route" gave me an error saying this address is invalid.
    >
    > "Bill Grant" <not.available@online> wrote in message
    > news:eRHtTun3EHA.1400@TK2MSFTNGP11.phx.gbl...
    >> 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.
    >>>>
    >>>>
    >>>
    >>>
    >>
    >>
    >
    >


  • Next message: Richard G. Harper: "Re: Disk device"

    Relevant Pages

    • Re: cant browse network accessed via VPN
      ... > doing tests on a test LAN on which i've got a windows server 2003 server. ... > resolve netbios names at all for the dial-up clients unless i can somehow ... > maintain hosts or lmhosts files on the vpn client machines. ... Only a PDC can merge browse lists ...
      (microsoft.public.windowsxp.network_web)
    • Re: cant browse network accessed via VPN
      ... > doing tests on a test LAN on which i've got a windows server 2003 server. ... > resolve netbios names at all for the dial-up clients unless i can somehow ... > maintain hosts or lmhosts files on the vpn client machines. ... Only a PDC can merge browse lists ...
      (microsoft.public.windows.server.networking)
    • Re: Computer Browsing Service - anyone want to contribute for a good conversation?
      ... Many of your VLANs will not have a server ... > this have to do with clients netbios over tcp settings? ... >> WINS does not store or replicate browse lists. ... The most common cause of master browser failures is multihomed ...
      (microsoft.public.windows.server.networking)
    • Re: Computer Browsing Service - anyone want to contribute for a good conversation?
      ... I have about 140 clients. ... My dc/dns/wins server 1 is on a .60 subnet. ... second essential is a method for the Domain Master Browser to find the ... WINS does not store or replicate browse lists. ...
      (microsoft.public.windows.server.networking)
    • Re: cant browse network accessed via VPN
      ... doing tests on a test LAN on which i've got a windows server 2003 server. ... do it automatically would be to enable global broadcasts to the vpn clients. ... Only a PDC can merge browse lists ...
      (microsoft.public.win2000.networking)