Posts: 51
Joined: 21.Mar.2001
From: Edmonton, AB, CA
Status: offline
This question came up on another forum and it peaked my interest.
The default remote access policy created by ISA for incoming VPN connections in RRAS creates a profile that has 40-bit, 56-bit and 128-bit encryption enabled. Is there anyway to force ISA's policy (which doesn't appear to be modifiable within RRAS without the changes being reverted back to the default by ISA) to only accept 128-bit MPPE encryption for PPTP connections?
The ISA firewall's default policy will always revert, but you can change the order of policy evaluation and have your own customer RRAS policy evaluated before the ISA policy.
Posts: 51
Joined: 21.Mar.2001
From: Edmonton, AB, CA
Status: offline
Hi Tom,
I tried exactly that, creating my own policy with the settings I wanted, and moving it above the default ISA policy that was created so it is first, and it does work. But as soon as the server is restarted, or the services restarted, or a change to the VPN settings via ISA Management is done and applied it always moves the default ISA policy back to #1, above any custom made policy, allowing 40-bit and 56-bit PPTP connections again.
[ December 15, 2004, 03:46 PM: Message edited by: Jack in the Box ]
I'll check it out on another box, but when I restarted the RRAS service within the ISA firewall console, the order of the Remote Access Policies didn't change.
Posts: 51
Joined: 21.Mar.2001
From: Edmonton, AB, CA
Status: offline
Hi Tom.
You're right, restarting the remote access service has no affect on the policy order. But if you restart the firewall service, or modify your VPN properties with in ISA Management and apply them, or reboot the server it resets the policy order and places the ISA Default first and along with it re-enables 40-bit and 56-bit VPN support.