Hello,
we updated from above Version and now we do not have Access via l2tp vpn using 2012r2 radius service
Is there a Workaround?
This thread was automatically locked due to age.
same Problem
to get a fix solution i created on utm a new ip pool which i excluded on our windows dhcp range and give some ips using a "27" Subnetmask in vpn pool configuration.
hope it will be soon fixed
server2016 dhcp and dns
radius 2012r2
Hi, Dave, and welcome to the UTM Community!
In the UTM, it's not best practice to assign IPs in the range of your LANs to L2TP/IPsec clients as it's easy to create routing problems with that configuration. I suggest that you use the standard "VPN Pool (L2TP)" object instead of DHCP from your 2012r2 server.
Cheers - Bob
Hello Bob,
yes to get a quick functionally vpn running I created a new VPN Pool Network which has nearly same range like our lan to get Connection to all Services and Servers.
Our DHCP Connection configured in Remote L2TP IPSEC does not work since Firmware update which also gets this ip range.
I tried to open a sophos case for this new problem but we have no premium Support.
Hello Bob,
yes to get a quick functionally vpn running I created a new VPN Pool Network which has nearly same range like our lan to get Connection to all Services and Servers.
Our DHCP Connection configured in Remote L2TP IPSEC does not work since Firmware update which also gets this ip range.
I tried to open a sophos case for this new problem but we have no premium Support.