Maybe something here helps.
https://directaccess.richardhicks.com/2019/08/19/always-on-vpn-and-rras-with-single-nic/
--please don't forget to upvote
and Accept as answer
if the reply is helpful--
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
I've been playing with Windows AOVPN and it seems to work well. The setup consists of there virtual servers all running Win2019, all joined to AD and each with a single vnic. The servers are:
-Server1 = DC/CA server
-Server2 = NPS server
-Server3 = RRAS server
To follow best practice, i give the RRAS vm a second vnic and connected this to our dmz. The vm now has the following network configuration:
NIC1 (Name = LAN) - 10.0.0.10/24 (domain.local)
NIC2 (Name = DMZ) - 192.168.100.10/24 (public)
As per the Microsoft KB article i've removed the GW ip from NIC1 and removed non-essential network protocols from NIC2 (ie: file & print sharing, etc). I then updated our corporate firewall to forward the AOVPN traffic to 192.168.100.
Since making these changes i can no longer connect to the AOVPN from any Windows 10 client. So, i then undid these changes (ie: put the RRAS server back to a single nic) and the AOVPN works once again. I attempted the above steps again and the AOVPN stops working! I can ping and resolve both internal and external DNS. I suspect this is a routing issue but i'm struggling to find any event errors or anything useful in the logs.
Any suggestions or advice would be appreciated.
Maybe something here helps.
https://directaccess.richardhicks.com/2019/08/19/always-on-vpn-and-rras-with-single-nic/
--please don't forget to upvote
and Accept as answer
if the reply is helpful--
Thanks for the advice.
I've just managed to fix this.
Seems it was an issue on the edge firewall.