Reserving IP addresses for VPN clients

[bbarrett5084]

We have a particular application running on our network that requires reserved IP addresses for all computers that connect. The application will not function properly unless the same computer runs the application using the same IP address every time. This works fine on our LAN, by configuring Reservations on our DHCP server, however I need to provide access to this application to remote users who establish a VPN connection to our ISA 2004 server.

I can't figure out how to reserve IP addresses for VPN clients. When using static IP pool, the addresses are given out first come, first serve. I can't enable DHCP on the ISA server because of our network configuration. If I set the ISA server to use Internal DHCP for connecting clients, my internal DHCP server assigns addresses, but I can't seem to turn these RAS type leases into reservations.

Any suggestions would be very helpful. If anyone knows how to assign particular IPs by login instead of computer that would work too.

 

[carlosmcse]

You can specify a static ip address for the user account if you're using AD.

 

[bbarrett5084]

Thanks for the suggestion. Where would I go to configure this?

 

[clayndwoods]

You can also configure ISa and the client to use static Ip addressing, as well as defined DNS and WINS.

Open the client and select Properties, select the networking tab, and the rest should seem very familiar to you. Highlight TCP/IP and select the properties to manually configure the client.

Actually, you CAN use the ISA for DHCP while existing on the network with another DHCP server, if both are configured properly. However, you don't HAVE to use ISA as the DHCP server, but after configuring VPN in ISA you have to go into Routing and Remote Access configuration (In Administrative Tools), expand the trees, right click the DHCP Relay Agent and configure it, so the network DHCP server replies get relayed to the VPN interface.

It take two IP addresses for each access, one for the PPP client on the remote computer and one for assignment to the internal interface. The internal interface becomes the routing gateway for the remote machine.