![]() Most topics I've seen so far suggest making sure the VPN adapter has "Register this connection in DNS" enabled in its IP settings, which it does. What we want is for the VPN adapters IP to register in DNS, so 10.0.0.101 in the example above. This IP is obviously no use to us and can't be contacted over the VPN anyway, so when we want to administer / connect to their machine over the VPN using machine name, we can't. IP registered in our DNS servers: 192.168.1.10 They connect to the VPN, and the SSTP adapter gets IP: 10.0.0.101 When a user is on the VPN, the IP address of their client-side LAN adapter is registered in our internal AD DNS servers. The problem comes with the DNS record that's being registered in our internal DNS servers. ![]() They can do DNS lookups of internal resources, split tunneling is fine, etc. ![]() Windows 10 clients, Sonicwall Mobile Connect app installed from Store, then VPN connection to our Soincwall firewall configured using Start > Settings > Network & Internet > VPN.Įssentially this is setting up an SSLVPN connection and creates an SSTP WAN Miniport adapter.įrom the client side, everything works. Bit of an annoyance I've been pondering the last few days:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |