Home > Wireless LAN > Splash Page > Troubleshooting Users' Network Access with Splash Page Enabled

Troubleshooting Users' Network Access with Splash Page Enabled

Table of contents
No headers

The Splash page is a feature that requires a user to click through or sign-on to a web page delivered by the Meraki or customer hosted web server in order to gain full network access. By clicking through or signing on to a splash the the user will authenticate their device against Dashboard and the and access point.

There are two common situations that can arise that may deny network access to a user when the splash page is enabled. The first is when Captive portal strength is configured to "Block all access until sign-on is complete". The second when a web browser is not configured to accept cookies.

The default port used for unencrypted web access is TCP port 80, which is HTTP traffic. When a users browser, and redirect the browser to Dashboard to be authenticated. This authentication creates an ACL on the AP and Dashboard. If "Block all access until sign-on is complete" is configured on the wireless network and the user has never been authenticated by the AP they are associated to, they will be denied network access until they open their web browser and open a web page using HTTP TCP port 80. Being unauthenticated will result in no access to anything except HTTP or a blank web page when roaming to an AP that is unaware of a previous unexpired authentication.

Successful authentication places a cookie in the users web browser. If a users web browser does not allow cookies, authentication will not succeed. This will result in a user seeing a blank page when using their web browser.

To mitigate the loss of network access, an ACL will be shared with the five closest AP after a user authenticates. These are the five closest APs based on Dashboard map placement.

If user is reporting a blank web pages or blocked network access, check the following:
- Is the web browser configured to not accept cookies?
- Is the web browser configured to use an HTTPS TCP port 443 URL as their home page?
- Is the user attempting to access a web page using HTTPS or some other transport?
- Has the user opened their web browser and visited a website using HTTP TCP port 80?

You must to post a comment.
Last modified
13:54, 31 Oct 2016


This page has no custom tags.


This page has no classifications.

Article ID

ID: 1949

Contact Support

Most questions can be answered by reviewing our documentation, but if you need more help, Cisco Meraki Support is ready to work with you.

Open a Case