SONICWALL SSL VPN CLIENT WINDOWS 10 WINDOWS 10
SONICWALL SSL VPN CLIENT WINDOWS 10 PLUS

SONICWALL SSL VPN CLIENT WINDOWS 10 PLUS

Plus if our internal DNS changes we'd have to lay hands on each travelling machine. I guess I could try hard setting our DNS servers on the MobileConnect adapter after adding the VPN connection and seeing if this makes any difference, but once we start down the road of applying client-side settings it sort of defeats the object of MobileConnect being lighter and quicker to configure.

This despite the fact that DNS lookups work fine from the client and are routed to our internal DNS. When using the MobileConnect method, they are blank. The only difference I have seen so far is, when the VPN is connection and I run an IPconfig /all, the NetExtender adapter has the IPs of our internal DNS servers (as set in the Sonciwall firewall's config) listed. The adapter appears in network control panel as 'Sonicwall NetExtender Adapter' type as opposed to a WAN miniport adapter when using MobileConnect, but when you dig into its advanced properties the options are much the same, and the settings that would seem relevent are set the same by default. The latest version from their website (v9.0.274) seems to work ok on my machine in a quick test, and the adapter's IP appears in our internal DNS servers. Well wouldn't you know it, NetExtender registers the right IP. Running ipconfig /registerdns while the VPN is running still gets the LAN adapters IP registered. One article suggests turning that setting off for the machine's LAN adapter, but we can't as it affects DNS when they're connected internally on our LAN. 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.

SONICWALL SSL VPN CLIENT WINDOWS 10 WINDOWS 10

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:

Sonicwall ssl vpn client windows 10