September 21st, 2003, 10:30 AM
|
#6 (permalink)
|
| Did you try Google yet?
Join Date: Feb 2003 Location: Buckhannon, WV
Posts: 3,468
| Quote: |
If the server on the remote side is a W2K DC and also acting as a DHCP server, it will assign an IP address to the client VPN machine automatically depending on how you have RAS configured.
| Agreed
Quote: |
And when you VPN from the client, even though the private ip is say 192.168.1.23, the remote VPN server sees the public IP assigned by the client ISP.
|
True, if I am reading it right
Quote: |
And when you configure the client you tell it to use the public ip of the server ISP.
|
Correct as well
Ok, let me whip up a quick diagram to explain. I will edit with a pic.
Ok, pictures. You should be able to read the text
Without VPN
With VPN
The problem isnt with the Client seeing the VPN server. Which is what I think you were thinking. The problem is routing, since you now have overlapping address space in your virtual network.
All the quotes were just a way for me to break it up into thoughts/statements.
Last edited by Siliconjunkie : September 21st, 2003 at 11:02 AM.
|
|  |