<div>
<br />
OK lets do this:<br />
<br />
Connect using the IP and the FQDN:<br />
<br />
And check the the status of the connection:<br />
show vpn-sessiondb svc<br />
(the idea is to check the group-policy and the tunnel-group selected)<br />
<br />
is the name of the ASA as the FQDN?<br />
<br />
Also try to do this:<br />
&quot;revert webvpn all&quot;<br />
<br />
<br />

</div>



OK lets do this:

Connect using the IP and the FQDN:

And check the the status of the connection:
show vpn-sessiondb svc
(the idea is to check the group-policy and the tunnel-group selected)

is the name of the ASA as the FQDN?

Also try to do this:
"revert webvpn all"




<div>
<div class="content wysiwyg-content">
We have our ASA using the Anyconnect VPN and it seems to be working fine. If you navigate to the IP address of our ASA's Outside interface, we get the correct login screen. It asks for the Username, Password and to choose a Group. I have it setup to use our Radius server for authentication. I can type in my Active Directory credentials and it logs me in and checks for the Anyconnect client on my PC.<br />
<br />
We moved forward with registering a FQDN for this EXACT same IP address, but when we try and user this FQDN, the ASA brings up a different webpage. This webpage only has a Username and Password field. There is no option to select a VPN Group. If I try and use my AD credentials, it fails authentication.<br />
<br />
I confirmed that the FQDN is using the correct IP by pinging it.<br />
<br />
Has anyone seen this before?
</div>
</div>


We have our ASA using the Anyconnect VPN and it seems to be working fine. If you navigate to the IP address of our ASA's Outside interface, we get the correct login screen. It asks for the Username, Password and to choose a Group. I have it setup to use our Radius server for authentication. I can type in my Active Directory credentials and it logs me in and checks for the Anyconnect client on my PC.

We moved forward with registering a FQDN for this EXACT same IP address, but when we try and user this FQDN, the ASA brings up a different webpage. This webpage only has a Username and Password field. There is no option to select a VPN Group. If I try and use my AD credentials, it fails authentication.

I confirmed that the FQDN is using the correct IP by pinging it.

Has anyone seen this before?

Cisco ASA SSL VPN produces 2 webpages

A virtual private network (VPN) is a network that uses a public telecommunication infrastructure, such as the Internet, to provide remote offices or travelling users access to a central organizational network securely. VPNs encapsulate data transfers using secure cryptographic methods and other security mechanisms to ensure that only authorized users can access the network and that the data cannot be intercepted.

Hardware-based firewalls provide more sophisticated protection for inbound and outbound traffic than the simple Windows software firewall or the basic NAT firewalls found in routers. These devices implement techniques such as stateful packet inspection, deep packet inspection, and content filtering; and may include built-in antivirus and anti-malware protection.

Hardware Firewalls

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).