Thanks for the information but I am not sure that it is the solution. My original scope is none routable IP addresses (172.1.x.x, subnet 255.255.255.255) for our companies everyday users. The scope that I created is routable (63.148.x.x, subnet 255.255.255.240). The reason for the new scope is so these specific machines can obtain a public IP address to connect to thier VPN server, this server I do not have control over (different company). So, even if I define the machine name and MAC number in the new scope, the machine does not find and use the specified IP address when obtaining an IP address from my LAN
Thanks,
Mar
----- Marc Reynolds [MSFT] wrote: ----
See 232703 How to Use DHCP to Provide Routing and Remote Access Clients wit
http://support.microsoft.com/?id=23270
--
Thanks
Marc Reynold
Microsoft Technical Suppor
This posting is provided "AS IS" with no warranties, and confers no rights
Mark said:
I have a DHCP server that now has 2 scopes on it. One pre existing scop
is the one that the server is actively giving address out from. The ne
scope was created for clients to use for VPN using public IP address'. If
define an address from the new scope on the client it will attach using tha
IP address, if I have DHCP do it, it uses an IP address from the origina
scope. Problem is, these VPN clients are from another company and the user
do not have privledges to assign the address and the client natively use
DHCP. I have added the client computers manually to the active leases o
the new scope hoping that it would attach, but it still will get an addres
from the other scope