ip address allocation through a vpn

hi, i have a question regarding ip addresses when logged onto the network via our vpn.  should the clients be allocated addresses within our dhcp pool or outside of it?  our dhcp pool is 192.168.1.50 to 192.168.1.180 but when a client logs on through the vpn they have been given ips of 192.168.1.203 and above.  is this right or have we got a setting wrong? using windows server 2003, and xp clients.   thanks in advance
julesnAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Brian PiercePhotographerCommented:
If you set up a Windows based VPN you can elect to have IP adresses allocated from DHCP or have a seperate range of IP adresses set up on the VPN. Both options have something to commend them. The big advantage with setting up a seperate address range on the VPN server is that you can easily identify the VPN connections.
0
Rob WilliamsCommented:
That range would have been set under "static address pool" in the routing and remote access console. You can locate by right clicking on the server name in RRAS and choosing properties and then going to the IP tab. Nothing wrong with that configuration but if you would rather, you can choose DHCP on the above 'tab' and then in the RRAS console choose DHCP relay agent and point to your DHCP server. They will then receive IP's in the same scope, and with most of the scope options.
Note: when RRAS assigns an IP from the DHCP scope it will reserve a block of 10 addresses when the first users connects, and 10 more when the 11th connects (actually when the 10th connects as the very first IP is assigned to the RRAS server). Point being, make sure you have enough addresses allocated in DHCP so you don't run out for you local users, if you choose to use the relay agent.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
julesnAuthor Commented:
thanks KCTS and RobWill for the advice.  i have looked in routing and remote access console and on the ip tab the option 'this server can assign ip addresses by using:' - dhcp is checked.  i can't find the dhcp relay agent choice anywhere, so i don't know if it's set up correctly.  sorry, i'm new to all this!  thanks again.
0
Rob WilliamsCommented:
Perhaps the DHCP relay agent is already set up.
It can be located by the opening RRAS console | expand the server name | Expand IP routing | right click on DHCP relay and choose properties | if configured the DHCP server address should be displayed

If DHCP relay is not enabled, then either the "static address pool" suggested earlier hands out an IP, or if DHCP is checked, and DHCP relay is not configured, it should hand out a 169.254.x.x APIPA address.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.