Should you still wish to assign a static IP to the VPN client, there are a couple of ways you can do so. Use only one method:
{remember office and home need to be different subnets}
1) This option, according to Microsoft, requires the domain functional level be Windows 2000 native or better, On the demo server I tried, the option wasn't available until I raised the functional level to Windows 2003 (option is definitely not available with 2000 mixed mode). Do not raise the functional level just for this. If you wish to do so read Microsoft's documentation as to what raising the functional level will affect, it can block access of older computer systems. If the option is available; you can open the user's profile in Active Directory Users and Computers and on the Dial-in tab there is an option (2nd from the bottom) to "Assign a Static IP address". Enable, and insert an IP address within the DHCP server's subnet
2) Open the Routing and Remote Access Service console, expand the server name options in the left window, click on "Remote Access Policies", in the right hand window right click on "Connections to Microsoft Routing and Remote Access Server" and choose properties, click "Edit Profile", on the "IP" tab check "Client may request an IP address", "OK" and exist. On the VPN client under TCP/IP properties assign an appropriate IP in the same subnet as the VPN server's subnet
|
