Re: Can't browse the network over VPN?!

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


Date: Wed, 20 Oct 2004 09:15:21 +1000


    You have basically the same problem with VPN as has always existed with
browsing across routers. The browse lists are built by LAN broadcasts, so
you need something extra to cross routers or WAN links.

    As the other posters have said, WINS is usually the key. If you are
running WINS on the LAN, WINS will have an entry for the Domain Master
Browser. If the client has the correct WINS address, it should be able to
browse the LAN. It will get the IP address of the DMB from WINS, then get
the browse list using that IP address.

    This all depends on the remote client knowing what the domain name is.
To get the DMB address from WINS, it looks for the <domainname 1B> entry in
WINS.

"Robert L [MS-MVP]" <noreply@hotmail.com> wrote in message
news:eCeHDbetEHA.2536@TK2MSFTNGP11.phx.gbl...
> quoted from http://www.ChicagoTech.net
> Unable to browse through PPTP/VPN connection
> Symptoms: 1. If the WINS server is on the same computer as the PPTP/VPN
> server, and you attempt to connect to a computer using a PPTP/VPN client,
> you may experience following problem: 1) The NetBIOS name of the computer
> to which you are attempting to connect is not resolved. 2) You may receive
> an error message similar to the following error message: "System error 53
> has occurred. The network path was not found" when using net view or
> opening Network Knighthood.
> 2. If the WINS server is not on the same computer as the PPTP server and
> you attempt to connect to a computer using a PPTP client, you may be able
> to connect to computers on your local area network (LAN), but you may be
> unable to connect to network shares or resources on the PPTP server.
> Resolutions: Inability to browse often means the client can't resolve
> NetBIOS names.
> 1. If this is a workgroup network, enable NetBIOS over TCP/IP on the
> server and clients.
> 2. If this is domain network and the WINS server is on the same computer
> as the PPTP/VPN server, move the WINS server to a different computer.
> 3. Add the NetBEUI protocol for your PPTP tunnel instead of, or in
> addition to, TCP/IP.
> 4. By default, most routers and firewalls prevent the transmission of
> NetBIOS names unless you enable UDP ports 137 and 138 and TCP port 139.
> Try to enable UDP ports 137 and 138 and TCP port 139 across all routers
> and firewalls between the PPTP/VPN client and PPTP/VPN server.
> 5. Make sure the client has correct DNS, WINS and Master Browser settings.
> 6. Make sure the default gateway points to the remote network rather than
> to the ISP.
> 7. Some ISP might block ports required for NetBIOS name broadcasts.
> 8. If WINS address is not distributed upon connection to VPN, LMHOSTS
> should be configured to enable Domain to be located.
> 9. If you try these techniques and the client still can't browse, try to
> use UNC to connect to the remote resources by ip, for example, use the net
> use h: \\serverip\sharename command.
>
> --
> For more and other information, go to http://www.ChicagoTech.net
>
>
> Don't send e-mail or reply to me except you need consulting services.
> Posting on MS newsgroup will benefit all readers and you may get more
> help.
>
>
> Robert Lin, MS-MVP, MCSE & CNE
>
> Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
> http://www.ChicagoTech.net
> This posting is provided "AS IS" with no warranties.
>
> "Eric Unger" <eunger@hotmail.com> wrote in message
> news:557d3fad.0410190046.638f7986@posting.google.com...
>> Hello-
>>
>> We are having problems with our VPN in our office which runs Windows
>> Server 2003. Our expert consultant claims that "with Windows 2003, you
>> can't browse the network over VPN.", and indeed we cannot right now.
>>
>> I was wondering if anyone could shed some light on this topic; I have
>> looked quite extensively on the internet but nowhere can I find any
>> information on this presumed limitation.
>>
>> Thank you very much in advance for your help.
>>
>> Eric
>
>



Relevant Pages

  • RE: Printing from Win9x clients stops
    ... Open Server Management. ... then right-click the name of the computer running Windows Small Business ... >From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • RE: Printing from Win9x clients stops
    ... The printers with 9x drivers on the server appeared automatically in the ... > then right-click the name of the computer running Windows Small Business ... > From the client computer: ... The Select Network Component Type ...
    (microsoft.public.windows.server.sbs)
  • Re: Daily Server Report (Critical Errors, Event ID: 537)
    ... Does this issue happen on client workstation or server? ... Does your server and all clients' workstation work well now? ... issue in your Network? ...
    (microsoft.public.windows.server.sbs)
  • Re: Small business thinking about backing up data, having a server and 2-3 users - is SBS200
    ... is networked to the Master with a crossover network cable. ... Master on the Master PC and Client on the Slave pc. ... Since this machine is a server is should handle the requests ok ... Most real firewall appliances have HTTP and SMTP proxy services that allow ...
    (microsoft.public.windows.server.sbs)
  • RE: Private addresses on public network
    ... anybody accesses those computers from an external network," -- even when the ... JavaScript delivered to the client that causes the client to retrieve ... the attacker, the request results in another JavaScript response that tells ... Moving beyond a single server ...
    (Security-Basics)