Force remote network DNS server to be prefered by VPN client
Posted: Thu Dec 10, 2015 10:23 pm
Hi.
I've set up SoftEther VPN in my network and I'll say it's good to finally get rid of PPTP; I've been living in fear for a while wondering when my network would be breached! However, with L2TP, I haven't figured out how to make the remote DNS take precedence over the clients DNS server hence the client is unable to resolve remote server names. I've tried with and without SecureNAT to no avail!
The clients are using the native L2TP client in Windows 10 on their Surface Pro 3/Surface Book devices and are reluctant to install the SoftEther VPN client (BYOD is allowed here). With the SoftEther VPN client, however, it appears to work as intended. Before I force the SoftEther VPN client down the throats of these problematic users, I just wanted to find out if there's anyone out there that has solved this issue with the native L2TP client in Windows 10.
Cheers,
ak.
I've set up SoftEther VPN in my network and I'll say it's good to finally get rid of PPTP; I've been living in fear for a while wondering when my network would be breached! However, with L2TP, I haven't figured out how to make the remote DNS take precedence over the clients DNS server hence the client is unable to resolve remote server names. I've tried with and without SecureNAT to no avail!
The clients are using the native L2TP client in Windows 10 on their Surface Pro 3/Surface Book devices and are reluctant to install the SoftEther VPN client (BYOD is allowed here). With the SoftEther VPN client, however, it appears to work as intended. Before I force the SoftEther VPN client down the throats of these problematic users, I just wanted to find out if there's anyone out there that has solved this issue with the native L2TP client in Windows 10.
Cheers,
ak.