Always-on VPN Device Tunnel - Help!

[mcrompton01]

Hi,

 

We've been working on Always-On VPN over the summer at one of our sites. We've got the user tunnel nailed down and are happy with it overall, it works, you can browse shares and load school based programs, all good. However we have not had much luck with the device tunnel element, were running Server 2016 as our AlwaysOn and Windows 10 1803 for clients.

 

No matter what we do we cannot get this part to work so the user is always logged on with Cashed Credentials and for some reason the user home drive fails to map (this might have been resolved now as we also use Offline Files as a backup. We've been following this guide and hope someone might be able to help us with the XML https://directaccess.richardhicks.com/2017/12/11/always-on-vpn-windows-10-device-tunnel-step-by-step-configuration-using-powershell/ just to check what we've got and done.

 

These are not our real IP addresses the bits in {} are the values we've entered.

 

  
   
vpn.{OurDomain.whatever}  
IKEv2  
  
 Certificate  
  
SplitTunnel  

true  
    
   
{10.200.0.1 - Site 1 Range}  
{19 - Site 2 Length}  
   
   
{10.100.0.1 - Site 2 IP Range}  
{19 - Site 2 Length}  
   

   
{10.200.0.1,10.100.0.1}  
 

 true 
 
true

true

 

 

Any help or pointers at this point in the holiday would be great. We don't have the option of going to Direct Access as we've had the ports open for Always On VPN and our IP has a maximum time od 20 working days to implement....

 

Thank you to anyone who helps with this, I'm getting rather worried now....

 

Mark

[Intelatech]

Hi Mark

 

Sorry I don’t have a solution but this is interesting. We have implemented Direct Access at our schools and we are coming across the same issue.