02-09-2011 08:31 AM
Hi,
we upgraded to 3.1.7 on Monday, afterwhich our iphones and android devices failed to get through, it appeared they didn't even close as there was no evidence on the logs.
Today I rolled back to 3.1.6 and the captive portal worked again.
Anyone else had this, anyone aware of a bug or a change in how CP works?
thanks
Darren
02-09-2011 09:43 AM
I know there has been changes, or rather bug-fixes in 3.1.7 regarding Captive Portal.
In 3.1.6 Captive Portal users (and NTLM authed users) could suddenly become "unknown" as soon as group membership was refreshed regardless of the CP user being a member of the group or not.
I'd suggest you open a case and sort out any issues you are experiencing.
02-09-2011 11:28 AM
To my knowledge, we have not heard any customers call in to PA Support for issues related to CP upon an upgrade to 3.1.7. This might be isolated to your setup and I too would suggest calling into PA Support for further root cause analysis.
-Renato
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!
