Can you post your ruleset?
This is likley occurring because third party cookies are not enabled in the browser.
Keep in mind with cookie authentication, MWG must verify the cookie from the client on every request. If the cookie is not sent, then MWG will try to authenticate.
For this reason Authentication Server (Time IP Based Session) is used instead of Cookie auth. See our guide on deploment methods and recommended auth methods:
Thanks for the reponse, we are using the cookie authentication because the client requirement is that they want staff to bring there own devices such as (iPads, Android tabs and phones) and they want to use the corporate wireless network to access the internet. and also they want authentication set for user, so that there a log track on what the staff has browsed for audit purposes.
Is there any other or better authentication method that can sit with such scenario of bringing your own device to connect to network and also authenticate to the Active Directory.