Windows 10: How do I automatically assign DNS and WINS servers to incoming VPN Clients on WS2k3?

Hello Everyone:I have a pretty bizarre setup in my lab that would more likely than not never exist in the real world. A backend network using 10.x.x.x IP addresses that represents "the internet" the only thing that has IP on this network are "site routers", email servers, etc. No client devices are here except one which will become important later.The backend network is populated by Windows Server 2003 boxes running RRAS, IAS, DNS, and DHCP these represent individual sites within an organization, a home, etc.. Each router has one IP address on "WAN" to represent the internet and han

:)

 

DNS server automatically changes to manual DNS and assigns a DNS server IP by itself

DNS settings in Laptop wifi adaptor gets changed automatically to manual DNS and assigns local DNS server IP by itself

 

Win 10: DNS resolution of remote network via VPN connection not working

Changing the metric worked for me, but my situation was a little different:

DNS resolution with my VPN had been working flawlessly with Win10 (first with Preview, then with RTM, always kept up-to-date) using Dell SonicWALL NetExtender (currently version 7.5.223)

Then this morning DNS resolution with my VPN stopped working suddenly. I hadn't explicitly made any changes or installed any updates or software. Perhaps an automatic update broke things.

Though the VPN still connected fine, and though the interface binding order HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\LanmanServer\Linkage\Bind was properly updated on connection of the VPN (i.e. the VPN's interface was added to the top of the list),
NSLOOKUP would use my LAN's DNS servers rather than the VPN's DNS servers. The VPN client was however showing properly-configured DNS servers.

In my case I was unable to open TCP/IPv4 properties for the "SonicWALL NetExtender" interface: the "Properties" button was displayed as being active, but clicking on it did nothing / did not open a properties dialog.

So instead I went to TCP/IPv4 properties for my Ethernet interface, clicked Advanced, and unchecked "Automatic metric", and assigned an arbitrary metric of 100.

After doing this DNS resolution once again works properly: When the VPN is connected the VPN interface's DNS servers are used. When the VPN is not connected, the Ethernet interface's DNS servers are used.

 

Can't connect to VPN when it automatically assigns IP's


I have a Windows 10 server with an incoming VPN connection created. Right now it specifies a range of IP addresses for the client to use. The alternative is to set it to have your DHCP assign the client's IP address instead. This is what I would like to do, but when I set the connection to ask like this, clients can't connect. On iOS and OS X they both say that they both cannot establish a connection to the VPN server.

My purpose for doing this is to allow all the clients to still browse the internet while connected to the VPN, which normally they cannot do (even when setting to send all traffic). I have to specify the DNS (my router's IP) on each computer, and on iOS this isn't working/possible. Does anyone have a solution to this, but at least more importantly the first issue? Thanks!