09-05-2019 05:35 AM - edited 09-05-2019 05:45 AM
On our network, there are certain IP addresses that, while accessible by users locally, are not accessible to users when they are connected via VPN. These IP address are part of the same sub-net, 192.168.0.x/24, which is included in the split-tunnel ACL. We recently replaced Domain Controllers, including the DNS service, but DNS resolution is not an issue for these IPs internally. ASA and VPN DNS settings were updated with the new DNS IP addresses.
Is it possible that these IPs are being excluded by a WAN-specific AC, which does not effect the LAN side of the network?
Our configuration is an ASA 5512-X, Software Version 9.2(2)4, Device Manager Version 7.3(1)101, AnyConnect 4.6.03049.
Solved! Go to Solution.
09-05-2019 06:02 AM
RJI,
Thanks for your reply. You got me thinking, so I checked the NIC configuration on one of the servers that is hosting some of the IPs. It turns out that, on one of the NICs, the Default Gateway had not been set. Once I made that change for the NIC, things started working as desired. Lesson learned.
09-05-2019 05:50 AM
09-05-2019 06:02 AM
RJI,
Thanks for your reply. You got me thinking, so I checked the NIC configuration on one of the servers that is hosting some of the IPs. It turns out that, on one of the NICs, the Default Gateway had not been set. Once I made that change for the NIC, things started working as desired. Lesson learned.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide