Forcing a wireless client to re-authenticate

[jyrbn]

One of our clients is connected to one of our SSIDs with a splash-page configured but is showing as "Not Authorized".

We tried using the disconnect client tool to try and re-authenticate the user but he does not go through the splash page. 

Is there a way to force the client to the authentication process again? 

[Brash]

"Not Authorized" means that the user hasn't clicked through the splash page.

Check your settings to verify whether you've got it set to block all traffic until the splash page is acknowledged.

Here is a community post with a screenshot for reference

Client status is "Not authorized", but the connection is established to acc... - The Meraki Communit...

[jyrbn]

The ssid is already set to block all traffic, our problem is that in the end device of the client, it's showing as "connected" already. 

[Brash]

The client will show connected even if they're not authenticated.

That's because connection to the SSID is not the same as authentication through the splash page.

If you have all of the appropriate settings set to block, the client should be able to connect to the SSID but not be able to reach anything until authenticating through the splash page.

[cmr]

Are you in Europe, or another region?  In Europe there is an option to delete client.

[PhilipDAth]

If the client is failing to detect it needs to connect to a splash page, you'll need to access any http (not https) web site to complete the process.

For example, Windows usually uses:

http://www.msftncsi.com/ncsi.txt

But any http request will do.

[prabhulkars]

Would suggest you to configure an SSID with the same configurations and check if the client is getting a splash page when he connects. Try to keep the Splash page frequency to minimum so that you can also try to disconnect the client and connect it again. This will isolate the issue further.