<div>
<div class="content wysiwyg-content">
I have a Cisco ASA that we're using for the SSL Anyconnect VPN on our corporate network. We have an issue that we've had since implementation that hasn't really been a critical problem till recent. <br />
<br />
When users log into the VPN, they are assigned an IP address, DNS servers, and a default domain. Internal network users use the same DNS servers as the VPN users. Frequently, when internal members are trying to reach fileshares on remote users' PCs they use the remote user's PC names and they are unable to browse the share. After examining the issue, it appears DNS is frequently resolving user computers to IP addresses that are not matching the machines. We have a seperate subnet for our VPN users so it's in the right subnet but may be for another user that logged in. <br />
<br />
We use Windows 2008 DNS servers and the addresses are provided via the Cisco DHCP services. Not sure where to even start to resolve this. help!
</div>
</div>


I have a Cisco ASA that we're using for the SSL Anyconnect VPN on our corporate network. We have an issue that we've had since implementation that hasn't really been a critical problem till recent. 

When users log into the VPN, they are assigned an IP address, DNS servers, and a default domain. Internal network users use the same DNS servers as the VPN users. Frequently, when internal members are trying to reach fileshares on remote users' PCs they use the remote user's PC names and they are unable to browse the share. After examining the issue, it appears DNS is frequently resolving user computers to IP addresses that are not matching the machines. We have a seperate subnet for our VPN users so it's in the right subnet but may be for another user that logged in. 

We use Windows 2008 DNS servers and the addresses are provided via the Cisco DHCP services. Not sure where to even start to resolve this. help!

Cisco ASA SSL VPN and DNS issues

I have a Cisco ASA that we&#39;re using for the SSL Anyconnect VPN on our corporate network. We have an issue that we&#39;ve had since implementation that hasn&#39;t really been a critical problem till recent. 

When users log into the VPN, they are assigned an IP address, DNS servers, and a default domain. Internal network users use the same DNS servers as the VPN users. Frequently, when internal members are trying to reach fileshares on remote users&#39; PCs they use the remote user&#39;s PC names and they are unable to browse the share. After examining the issue, it appears DNS is frequently resolving user computers to IP addresses that are not matching the machines. We have a seperate subnet for our VPN users so it&#39;s in the right subnet but may be for another user that logged in. 

We use Windows 2008 DNS servers and the addresses are provided via the Cisco DHCP services. Not sure where to even start to resolve this. help!

The Domain Name System (DNS) is a hierarchical, globally distributed system responsible for associating the name of a computer, service or other resource into an IP address for connecting to the Internet or a private network. Most prominently, it translates domain names to the numerical IP addresses needed for the purpose of computer services and devices worldwide.

The Dynamic Host Configuration Protocol (DHCP) is an auto configuration protocol used on IP networks and an extension of the Bootstrap Protocol. DHCP allows for computers to be configured automatically to communicate with each other over an IP network without the need for manual setup by a network administrator. The implementation of DHCP relies on a DHCP server to hand out network configuration information to DHCP-capable clients that request an IP address (and other information required or useful in communicating with other devices on an IP network). In addition to an IP address, common configuration information served over DHCP includes a default gateway, subnet mask and DNS sever(s).

DHCP

Cisco PIX is a dedicated hardware firewall appliance; the Cisco Adaptive Security Appliance (ASA) is a firewall and anti-malware security appliance that provides unified threat management and protection the PIX does not. Other Cisco devices and systems include routers, switches, storage networking, wireless and the software and hardware for PIX Firewall Manager (PFM), PIX Device Manager (PDM) and Adaptive Security Device Manager (ASDM).