Technical Tip: Captive Portal Registration Failed to detect a Change in the network Settings after Registration

[Hawada1]

Description	This article describes how to resolve redirection of BYOD/Guest user after being registered to a network.
Scope	FortiNAC
Solution	When  the following error is seen 'Failed to detect a Change in Your network Settings, Retrying...' after the guest device was successfully authenticated/registered to the network via the registration portal. Try checking the below settings: 1) Is the following URL accessible from the production VLAN 'http://www.google.com/images/srpr/logo11w.png' 2) Are there any firewall rules that prevent 'HTTP' from being accessed in the Isolation or production network? 3) Resolution for 'Failed to detect a change in your network settings' error after redirection to production VLAN: Modify to the script entered in Portal - > Portal Configuration - > Registration - > Success: Change var detectionTimeoutSeconds = 15, TO var detectionTimeoutSeconds = 160, 4) Save the config and Retest. Note: The above settings, will not be applied in case the device was in the remediation portal. As a work around for remediated Guest devices one can modify the captive portal page to tell the user to close the browser and reopen it after the timer expires.