You are responding to an old post. Please open a new post, or better reach out to your Aruba partner or Aruba Support as I have not seen a 'generic' fix for the issue. There probably is something in your environment, client, configuration that prevents the pop up to appear.
------------------------------
Herman Robers
------------------------
If you have urgent issues, always contact your Aruba partner, distributor, or Aruba TAC Support. Check
https://www.arubanetworks.com/support-services/contact-support/ for how to contact Aruba TAC. Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
In case your problem is solved, please invest the time to post a follow-up with the information on how you solved it. Others can benefit from that.
------------------------------
Original Message:
Sent: Aug 30, 2021 10:42 PM
From: Varun Sharma
Subject: Captive portal pop up - windows 10
Hi Rich,
I am also facing the same issue. I have win 10 machine which is allowed a limited access i.e DHCP , DNS and captive portal redirect but auto pop up doesn't work.
Please share your experience how you fixed the issue. Did you make any change on the network or client device to get auto pop up
------------------------------
Varun Sharma
Original Message:
Sent: Dec 10, 2019 05:13 PM
From: Richard Marriner
Subject: Captive portal pop up - windows 10
Did you ever find a fix for this? I'm having the exact same issue! Captive portal works in pretty much every other device we have, but I haven't been able to get Windows 10 to automatically display the captive portal. When I do a wireshark capture, I can see Windows make the http request to www.msftconnecttest.com, and I would think it would be blocked and receive the captive portal then, but it doesn't because when I follow the session it actually returns a valid response "Microsoft Connect Test".
To me, it's almost like the connect test fires off before the AP can apply the ACL to the session, thus allowing the traffic for a split second so Windows thinks there is no captive portal.