Hi, Thank you for the quick response!!
The security risk was not my issue i knew how to deal with and I knew the risks involved. However, the terminology of searching Google "Windows VPN split tunneling" lead me to what I needed and solve my issues.
First I came across this long article:
http://www.isaserver.org/tutorials/VPN_Client_Security_Issues.html
It explains how to deal with split tunneling and it explains it very detailed.
The problem I was having is with I needed VPN to be able to access another server with a different subnet of that server. The tutorial explains how to deal with in the following paragraph but i did not understand:
"Configure Routing Infrastructure to Support Off-Subnet Addresses
If you do configure the ISA/VPN server to assign off subnet addresses, you must make sure that your routing infrastructure is set so that the off subnet network ID is reachable for all internal network clients (or at least those you wish the VPN clients to connect to). This means adding routing table entries on your network routers that point to the internal interface of the ISA/VPN server for the off subnet network ID. You can add these manually, or have a routing protocol such as RIP or OSPF do the heavy lifting."
I did not know what needed to be done or how to do it. I tried playing around with the routing table but the was no success so I must have missed something. So I carried on searching google.
I then came across another forum ( http://www.winvistatips.com/dns-and-split-tunneling-vpn-t723755.html ) who wanted a similar and suggested adding another static ip address to the NIC of the server you want to access to use the same subnet of the VPN. And then adding a host record in the DNS server to point to the VPN Subnet. You can add the ip to any NIC on the internal LAN that you want to be able to access through the VPN .
After wards you can use Remote Access Policies to control the security from the VPN clients as mentioned in the tutorial above.
THANK YOU FOR YOUR TIME! AND RESPONDING!!
