Cannot connect to the Internet

A

Arlis Brown

The problem I'm attemping to address is associated with
Q317025 "... Cannot connect to the Internet after you
connect to a VPN server". The root of the problem lies in
how a default gateway address is allocated to a VPN
client. If you disable the use of "the default gateway
on the remote network", you can surf the Internet via
your local ISP while the VPN session is active. However,
in order to access the resources on your internal
corporate Intranet, you need to add static routes. This
is all fine and dandy, however, the static routes are
based on the IP address allocated to the VPN connection
by DHCP or a static pool on the VPN server. Herein lies
the problem... the IP address allocated is different
every time a VPN connection is made.

I currently have a W2K VPN server setup to relay DHCP
requests but also noted you can setup static IP address
pools. Under both configurations, I have tried without
success to figure out how it is possible to "reserve" an
IP address for a particular VPN client.

Does anybody know if Windows 2003 has address this issue?

Thank you in advance for any input on this issue!

Arlis Brown, Network Manager
Eye Associates of NM, Ltd.
 
B

Bill Grant

With Server 2003 I would look at using CMAK to configure the client's
connection properties (including the routing).
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top