search

richardhicks / aovpn

PowerShell scripts and sample ProfileXML files for configuring Windows 10 Always On VPN
MIT License
158 stars 83 forks source link

After enabling IPv6 on server, internal connections no longer work #16

Closed HomeJeroen closed 2 years ago

HomeJeroen commented 2 years ago

We recentely had to "disable" IPv6 on our AOVPN-server as we received the wrong prefix from our ISP. Now this has been resolved we have enabled IPv6 again on the server. Clients are able to connect (both through Device Tunnel and User Tunnel). They show up as clients in the RRAS - however over IPv6 they are not able to reach anything on the network.

We have enabled IPv6 routing: Screenshot 2022-06-22 140147

We have the correct routing set on the internal NIC for IPv6, from the AOVPN server we can reach the internal network.

When we use the IPv4 address of our NAS, we can reach it through vpn, but using the IPv6 address, it doesn't work. I am really at a loss why IPv6 routing is not working. If you can help, that would be great. Or point us to the direction we have to look.

HomeJeroen commented 2 years ago

We solved it. The DNS records of the AOVPN server were somehow deleted from our domain controllers. When we added both IPv4 and IPv6 records back, everything started working again.t