11-19-2018 04:50 AM
Hi All,
I'm running Anyconnect client 4.6 on windows 10. I have always on configured, but cannot get the client to detected captive portal and allow remediation.
I've disabled the IE proxy, and set anyconnect to ignore proxy anyway. The captive portal exists, as soon as I connect to the network there's a couple of seconds of network access and IE pops up with the captive portal, but this is I believe just windows 10 doing it's thing, anyconnect detects the untrusted network and tries to initiate the vpn, which fails, and then closes network access.
Any ideas why windows can detect it but it appears Anyconnect cannot?
If I set it to fail open I still have access, but that's not what's required.
Grateful for any input.
Solved! Go to Solution.
11-19-2018 07:11 AM
If anyone is interested, I found out what the issue was.
Bit of an obvious one really. I was using FQDN's and there was no available DNS, so the client wasn't even initiating the connection to pick up the captive portal. I'd been using a test client with a modified host file previously so overlooked it.
11-19-2018 07:11 AM
If anyone is interested, I found out what the issue was.
Bit of an obvious one really. I was using FQDN's and there was no available DNS, so the client wasn't even initiating the connection to pick up the captive portal. I'd been using a test client with a modified host file previously so overlooked it.
11-19-2018 09:30 AM
Hi,
The DNS server access/permission is the first requirement for captive portal.
Regards,
Deepak Kumar
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