Can't browse the network over VPN?!

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

Hi Eric,

I don't know if this is the problem, but when I first put up our Cisco VPN I
had to manually put in the WINS server on the client TCP/IP settings.

Good luck,
Dave DeCoursey


"Eric Unger" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> 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

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" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> 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

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]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> 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" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) om...
>> 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
>
>

Did you take a look at....

KB232703 How to use DHCP to provide Routing and Remote Access Clients with Additional DHCP Options.
KB292822 Name resolution and connectivity issues on a Routing and Remote Access Server that also runs DNS or WINS
KB217766 Strategies to use if VPN clients cannot access resources on a VPN server that has one network adapter
http://www.microsoft.com/technet/pro.../vpndeplr.mspx


Kyle Lang, MCSE/CCNA/CCEA

"This posting is provided "AS-IS" with no warranties, and confers no rights"
--------------------
> From: (E-Mail Removed) (Eric Unger)
> Newsgroups: microsoft.public.windows.server.networking
> Subject: Can't browse the network over VPN?!
> Date: 19 Oct 2004 01:46:09 -0700
> Organization: http://groups.google.com
> Lines: 13
> Message-ID: <(E-Mail Removed) >
> NNTP-Posting-Host: 82.229.244.150
> Content-Type: text/plain; charset=ISO-8859-1
> Content-Transfer-Encoding: 8bit
> X-Trace: posting.google.com 1098175570 683 127.0.0.1 (19 Oct 2004 08:46:10 GMT)
> X-Complaints-To: groups-(E-Mail Removed)
> NNTP-Posting-Date: Tue, 19 Oct 2004 08:46:10 +0000 (UTC)
> Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed 00.sul.t-online.de!t-online.de!tiscali!newsfeed1.ip.tiscali.net!
proxad.net!postnews1.google.com!not-for-mail
> Xref: cpmsftngxa06.phx.gbl microsoft.public.windows.server.networking:19002
> X-Tomcat-NG: microsoft.public.windows.server.networking
>
> 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
>

So are looking through all these helpful hints, do you still have the problem ?


Kyle Lang, MCSE/CCNA/CCEA

"This posting is provided "AS-IS" with no warranties, and confers no rights"
--------------------
> From: (E-Mail Removed) (Eric Unger)
> Newsgroups: microsoft.public.windows.server.networking
> Subject: Can't browse the network over VPN?!
> Date: 19 Oct 2004 01:46:09 -0700
> Organization: http://groups.google.com
> Lines: 13
> Message-ID: <(E-Mail Removed) >
> NNTP-Posting-Host: 82.229.244.150
> Content-Type: text/plain; charset=ISO-8859-1
> Content-Transfer-Encoding: 8bit
> X-Trace: posting.google.com 1098175570 683 127.0.0.1 (19 Oct 2004 08:46:10 GMT)
> X-Complaints-To: groups-(E-Mail Removed)
> NNTP-Posting-Date: Tue, 19 Oct 2004 08:46:10 +0000 (UTC)
> Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!newsfeed 00.sul.t-online.de!t-online.de!tiscali!newsfeed1.ip.tiscali.net!
proxad.net!postnews1.google.com!not-for-mail
> Xref: cpmsftngxa06.phx.gbl microsoft.public.windows.server.networking:19002
> X-Tomcat-NG: microsoft.public.windows.server.networking
>
> 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
>