Issue: Drive Mapping Over Split Tunnel VPN
Although this issue pops up from time to time (cannot map drives over vpn), we got a lot of complaints after upgrading from v184.108.40.206 to v220.127.116.11 (apm client v7185 to v7198). After uninstalling the v7198 client and then installing v7185 affected users can generally map their drives afterward. Although I'm testing the v7213 apm client as a replacement, I'd like to look at ways to reduce if not eliminate this wonky dns behavior altogether.
What F5 tech support's seen in the client vpn diag file and which I've seen in a client Wireshark capture (looking at TCP 139 & 445 and UDP 137), is the client's trying to use its local DNS rather than that supplied by VPN to resolve the hostname for drive mapping. Of course, it's going to fail.
Has anyone else had this issue? Some end users have trouble while others don't which makes me wonder if there's something on the client side that needs to be corrected.
- The metric for the vpn interface is "1" whereas the local ethernet connection is "25."