03-15-2023 09:17 PM
Hi Team,
Cheers.
Our customer environment is using Cisco ISE 3.1 Patch 3 and WLC 5520 8.10.171 with Client connecting to SSID that used Guest-Portal (Authentication using Azure-AD).
in the last weeks,
when client connect to SSID (normal for the first time, the guest portal redirect showed up), and then hibernate the Windows device, and tomorrow come to work again,
it shows on Error 400 Bad Request (picture attached) when connecting to SSID.
FYI, when client restart the Windows, the client can connect normally.
what causing this? is anyone experiencing this type of issue?
Thanks
*in another customer, they also experiencing this issue, while using ISE 2.4
Solved! Go to Solution.
03-16-2023 04:57 AM
Hibernation causes this. When the machine "wakes up" from hibernation, it tries to use the RADIUS Session ID that was in use prior to the hibernation. During the time the machine is in hibernation, ISE does not receive traffic from the session and terminates it. This is as designed and is working properly.
03-16-2023 04:57 AM
Hibernation causes this. When the machine "wakes up" from hibernation, it tries to use the RADIUS Session ID that was in use prior to the hibernation. During the time the machine is in hibernation, ISE does not receive traffic from the session and terminates it. This is as designed and is working properly.
03-17-2023 03:14 AM
Hi Sir,
thanks for the response.
So in which case, it caused by Windows machine that when "wake up" from the hibernate mode, and try to connect to SSID, the session in the browser and ISE is "not match" and then it shows Error Code 400 ?
And the work around is "not hibernate" the windows and shutdown/restart the Windows?
Thanks
03-17-2023 05:46 AM
That is correct, though not technically a workaround.
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