Windows 10: Public IP Addresses / Ranges of Microsoft Windows Update Services for VPN Split Tunnelling

Hi, We are looking for public IP Addresses / Ranges of Microsoft Windows Update Services for VPN Split Tunnelling. Requirement is specifically for Split Tunnleing for devices using Cisco ASA VPN. Configuring the Split Tunnel for Windows Updates will allow VPN users to download the updates directly from Microsoft site and will save some corporate bandwidth.


Below are the URLs we are looking Public IPs or ranges for:

• https://*.prod.do.dsp.mp.microsoft.com
• http://emdl.ws.microsoft.com
• http://*.dl.delivery.mp.microsoft.com
• http://*.windowsupdate.com
• https://*.delivery.mp.microsoft.com
• https://*.update.microsoft.com
• https://tsfe.trafficshaping.dsp.mp.microsoft.com

Note: Cisco ASA has limitation and cannot configure wildcard URLs.

:)

 

Windows 10 VPN and Split Tunneling for users, not administrators

Hello everyone

In Windows 10 when connecting to VPN it is very well documented that Split Tunneling is on be default. I don't mind this as an administrator but asking my users to have to either run some powershell commands or change advanced networking settings is not
really acceptable.

I would like my users to be able to connect to the VPN and once connected they should be able to use the UNC path to get to the file server on the network. right now, they get redirected to a public IP address via our external DNS information. Using \\[ipAddress-of-server]
works as expected.

How can I set up my VPN connections to use the internal DNS when connected to VPN.

Also, is it possible to create either a shortcut or mapped drive on connection that gets deleted upon disconnection?

Thank you for any help

 

what is my public IP range

Im creating a VPN and the tutorial point that I cant use 0.0.0.0/0 for my RDP protocol (3389) because causes a security vulnerability.

I use the 0.0.0.0/0 for HTTP (80) and HTTPS (443), but for RDP I'd use my Public IP Range.

how I find my public IP range? Im using the W10

 

VPN keeps returning the real IP address instead of the VPN address

According to their web site, PureVPN does use IKEv2, as well, so don't give up on that just yet. IKEv2 is more secure than PPTP by a long shot.

Regarding the real IP vs VPN IP issue... that is exactly what split tunneling does. It send most traffic through the underlying connection and only uses the VPN when the destination is only available through VPN. Turn off split tunneling and it should address
that issue.

For connecting via IKEv2, try using Automatic instead of specifying it explicitly. The reason for doing so I outlined in this thread

http://answers.microsoft.com/en-us/windows/forum/windows_10-networking/why-doesnt-the-vpn-work-on-windows-10-mobile/607d23f9-eff0-44f6-9308-bbd250569966.

Hope this helped.