A couple of our test users are experiencing an issue with DNS while connected to the Cisco Secure Client. The issue appears to be happening after the workstation is left disconnected from VPN overnight. When they connect the next morning, the VPN connection does not resolve to any clients on the network preventing the mapped network drives from connecting. The workstation can ping the domain controller and file server by ip address, but not by hostname. The workstation can ping public domains like cisco.com while this issue is happening. The user has to restart their workstation and reconnect to VPN to be able to access their mapped network drives.
Meraki vMX appliance in AWS
Version MX 17.10.2
Cisco Secure Client
Version 5.0.01242
