VPN and Internet Access windows 2003 Server

I have a windows 2003 server, I have configured it accept VPN
connections from my XP clients. The clients connect fine, however they
cannot use the internet. Is there a way to enable internet access via
our internal network connection without modifying the remote clients
computer.

I was thinking I could add a route or something on the server
itself..any thought appreciated!

That depends on how you LAN provides for Internet access in the first place.
That is what determines the method.

As far as the general bahavor you are experiencing,..it is normal behavor by
design. When the VPN goes "active" the client becomes part of the LAN and is
not supposed to "see" the internet on its own any longer until the VPN is
brought down. This is a protection mechanism to secure the LAN that you are
VPNing into. This can be overcome via "Split-tunneling" which is nothing
more than disableing the "Use Gateway on Remote Network" option in the
TCP/IP settings of the Connectiod.

--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"Jeff" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> I have a windows 2003 server, I have configured it accept VPN
> connections from my XP clients. The clients connect fine, however they
> cannot use the internet. Is there a way to enable internet access via
> our internal network connection without modifying the remote clients
> computer.
>
> I was thinking I could add a route or something on the server
> itself..any thought appreciated!
>

Split tunneling is a serious security risk. Don't do it. Instead, try this
cool trick.

http://support.microsoft.com/default...b;en-us;310888

Steve Riley
(E-Mail Removed)



> That depends on how you LAN provides for Internet access in the first
> place. That is what determines the method.
>
> As far as the general bahavor you are experiencing,..it is normal
> behavor by design. When the VPN goes "active" the client becomes part
> of the LAN and is not supposed to "see" the internet on its own any
> longer until the VPN is brought down. This is a protection mechanism
> to secure the LAN that you are VPNing into. This can be overcome via
> "Split-tunneling" which is nothing more than disableing the "Use
> Gateway on Remote Network" option in the TCP/IP settings of the
> Connectiod.
>
> "Jeff" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) ups.com...
>> I have a windows 2003 server, I have configured it accept VPN
>> connections from my XP clients. The clients connect fine, however
>> they cannot use the internet. Is there a way to enable internet
>> access via our internal network connection without modifying the
>> remote clients computer.
>>
>> I was thinking I could add a route or something on the server
>> itself..any thought appreciated!
>>

Hmmm....RRAS NAT "reflecting" VPN clients back out onto the Internet when
they need it. Interesting. I'll think I'll save this one.

--
Todd J Heron, MCSE
Windows Server 2003/2000/NT
----------------------------------------------------------------------------
This posting is provided "as is" with no warranties and confers no rights

Woe, were getting off track. I am using a vpn connection to our lan, and
then using remote desktop connections to control a server. We just added two
03 Enterprise editions and I cannot ping or use remote desktop connections
for these servers over vpn, but I am fine with my other 2000 / 2003 servers.
I figure there must be something blocking the access. I can remote these
boxes when I am on the local lan, just not over vpn.



"Steve Riley [MSFT]" wrote:

> Split tunneling is a serious security risk. Don't do it. Instead, try this
> cool trick.
>
> http://support.microsoft.com/default...b;en-us;310888
>
> Steve Riley
> (E-Mail Removed)
>
>
>
> > That depends on how you LAN provides for Internet access in the first
> > place. That is what determines the method.
> >
> > As far as the general bahavor you are experiencing,..it is normal
> > behavor by design. When the VPN goes "active" the client becomes part
> > of the LAN and is not supposed to "see" the internet on its own any
> > longer until the VPN is brought down. This is a protection mechanism
> > to secure the LAN that you are VPNing into. This can be overcome via
> > "Split-tunneling" which is nothing more than disableing the "Use
> > Gateway on Remote Network" option in the TCP/IP settings of the
> > Connectiod.
> >
> > "Jeff" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed) ups.com...
> >> I have a windows 2003 server, I have configured it accept VPN
> >> connections from my XP clients. The clients connect fine, however
> >> they cannot use the internet. Is there a way to enable internet
> >> access via our internal network connection without modifying the
> >> remote clients computer.
> >>
> >> I was thinking I could add a route or something on the server
> >> itself..any thought appreciated!
> >>
>
>
>

My mistake, I have a question here and posted to the wrong one.

"wayne@q4" wrote:

> Woe, were getting off track. I am using a vpn connection to our lan, and
> then using remote desktop connections to control a server. We just added two
> 03 Enterprise editions and I cannot ping or use remote desktop connections
> for these servers over vpn, but I am fine with my other 2000 / 2003 servers.
> I figure there must be something blocking the access. I can remote these
> boxes when I am on the local lan, just not over vpn.
>
>
>
> "Steve Riley [MSFT]" wrote:
>
> > Split tunneling is a serious security risk. Don't do it. Instead, try this
> > cool trick.
> >
> > http://support.microsoft.com/default...b;en-us;310888
> >
> > Steve Riley
> > (E-Mail Removed)
> >
> >
> >
> > > That depends on how you LAN provides for Internet access in the first
> > > place. That is what determines the method.
> > >
> > > As far as the general bahavor you are experiencing,..it is normal
> > > behavor by design. When the VPN goes "active" the client becomes part
> > > of the LAN and is not supposed to "see" the internet on its own any
> > > longer until the VPN is brought down. This is a protection mechanism
> > > to secure the LAN that you are VPNing into. This can be overcome via
> > > "Split-tunneling" which is nothing more than disableing the "Use
> > > Gateway on Remote Network" option in the TCP/IP settings of the
> > > Connectiod.
> > >
> > > "Jeff" <(E-Mail Removed)> wrote in message
> > > news:(E-Mail Removed) ups.com...
> > >> I have a windows 2003 server, I have configured it accept VPN
> > >> connections from my XP clients. The clients connect fine, however
> > >> they cannot use the internet. Is there a way to enable internet
> > >> access via our internal network connection without modifying the
> > >> remote clients computer.
> > >>
> > >> I was thinking I could add a route or something on the server
> > >> itself..any thought appreciated!
> > >>
> >
> >
> >