VPN SSL - DNS
When a Windows client establishes a VPN SSL connection to ATP500/800, via Secuextender, usually it takes the DNS server IP configured on the ATP. But not always. When it does not, and it keeps the DNS server IP received from the home route, the client is unable to access remote LAN resources by name. I couldn't find a pattern, it seems it happens randomly.
In these days of COVID19 a lot of persons work from home, so we had the chance to observe many cases as above.
Did anybody else see this problem ? Any suggestion how to fix it ?
many thanks
Paolo
All Replies
-
On windows 10, if you are using split tunnel instead of forwarding all traffic into the tunnel.
The DNS query priority is based on the metric of interface.
Here the MS-DOS mode command to show the metric value of all interfaces.
c:/> netsh interface ipv4 show interfaces
In my example,
The VPN interface is "Ethernet 2" with metric 55, and the local wireless interface is "Wi-Fi" with metric 40. Local wire interface is "Ethernet" with metric 5.
So that I need to change the VPN interface metric small than "5" to get higher priority.
http://woshub.com/dns-resolution-via-vpn-not-working-windows/
1 -
many thanks, I will check it out
regards
0
Categories
- 8.5K All Categories
- 1.6K Nebula
- 71 Nebula Ideas
- 57 Nebula Status and Incidents
- 4.5K Security
- 226 Security Ideas
- 983 Switch
- 46 Switch Ideas
- 878 WirelessLAN
- 22 WLAN Ideas
- 5.2K Consumer Product
- 157 Service & License
- 280 News and Release
- 59 Security Advisories
- 13 Education Center
- 580 FAQ
- 263 Nebula FAQ
- 160 Security FAQ
- 76 Switch FAQ
- 74 WirelessLAN FAQ
- 7 Consumer Product FAQ
- 34 Documents
- 34 Nebula Monthly Express
- 69 About Community
- 46 Security Highlight