PlazaProp
asked on
Can I restrict (windows 2003/8) PPTP VPN access based on computer name (and/or IP address)
We are testing setting up a Windows 2008 box for incoming VPN connections. I can make a successful connection from a remote machine and access network resources. I restrict by user and time of day.
Is it possible to restrict by computer name also, using PPTP?
How about the incoming client public IP address?
Our VPN server has a single NIC and running Network Policy Server (NPS) locally. Firewall is passing the tcp port.
Remote computers are mostly XP Pro. Some Win7 may come in to play soon.
None of the remote machines are planned to be part of the domain. One of the two test machines is a domain workstation and the other is not. Not sure if we plan to make them part of the domain or not as I have not been able to successfully execute log on scripts, which would be the major benefit for us. (but that is another issue)
Is it possible to restrict by computer name also, using PPTP?
How about the incoming client public IP address?
Our VPN server has a single NIC and running Network Policy Server (NPS) locally. Firewall is passing the tcp port.
Remote computers are mostly XP Pro. Some Win7 may come in to play soon.
None of the remote machines are planned to be part of the domain. One of the two test machines is a domain workstation and the other is not. Not sure if we plan to make them part of the domain or not as I have not been able to successfully execute log on scripts, which would be the major benefit for us. (but that is another issue)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
TACACS and RADIUS servers can use Multiple means of authentication prior to getting an IP through the VPN. It' s probably your best bet. TACACS can use AD for authentication. So, you can split AAA on a TACACS server. However RADIUS servers hold Authentication, Authorization, and Access (AAA) on the one server.
A second option is:
Also, MAC address filtering on the switches will prevent them from getting anywhere within the network, if the MAC address isn't enabled on the switches. But, that is VERY admin intensive unless you only have a few machines. So, on your router, a MAC address filter ACL through the VPN connection will limit only the machines with those MAC addresses through your VPN tunnel.
A second option is:
Also, MAC address filtering on the switches will prevent them from getting anywhere within the network, if the MAC address isn't enabled on the switches. But, that is VERY admin intensive unless you only have a few machines. So, on your router, a MAC address filter ACL through the VPN connection will limit only the machines with those MAC addresses through your VPN tunnel.
MAC address filtering will not work, as VPN connections do not maintain the original MAC addresses. MAC addresses are a feature of local networks only.
IP filtering can be done on several levels. One is the IP Filter list in the NICs TCP/IP properties. But I guess it is much easier to filter on the edge device (which forwards the VPN traffic).
IP filtering can be done on several levels. One is the IP Filter list in the NICs TCP/IP properties. But I guess it is much easier to filter on the edge device (which forwards the VPN traffic).
ASKER
MAC address filtering would be nice for road warriors that could have changing IP addresses. For our initial roll out the clients all have static IP so filtering by IP would work. I have verified that I can do this on our firewall. Thanks for the tip.
ASKER
I am not sure if I can restrict the port by IP address on our firewall but I am investigating.