Home > General Administration > Tools and Troubleshooting > Error: The Meraki Cloud is having difficulty connecting to your RADIUS server

Error: The Meraki Cloud is having difficulty connecting to your RADIUS server

Table of contents
No headers

When Sign-on Splash-page is used with a RADIUS server, Dashboard must be able to communicate with the RADIUS server. Dashboard, which acts as the RADIUS client, sends authentication requests (RADIUS Access Requests) to the public IP address of the configured RADIUS server. 

The source IP addresses used by Dashboard may change over time. As a precaution, Dashboard periodically tests the configured RADIUS server to verify accessibility. Specifically, Dashboard sends an Access Request message with 'meraki-ping' as the username and 'ping-test' as the password. If the RADIUS server replies with an Access-Accept or Access-Reject, Dashboard knows the server is reachable.

In the event that Dashboard does not receive a response after 6 attempts (one every 20 seconds), it will assume the RADIUS server is unreachable and an email will be sent to the Dashboard administrator. The email will contain the IP address of the server that failed, all of the IP addresses that may attempt to contact the RADIUS server, and a link to the appropriate Configure > Access control page where they are listed.

If you received this email, please verify the following:

  1. If the RADIUS server is protected by a firewall, ensure that Dashboard is able to access the server through the firewall using the IP addresses and port number specified in the email. A current list of IP addresses and the port number can be found in Dashboard on the Wireless > Configure > Access control page for the SSID under the Splash page section.
  2. Dashboard's IPs must be configured as RADIUS clients on the RADIUS server using the same shared secret configured in Dashboard.
  3. Ensure there are no additional restrictions on the RADIUS server that would prevent it from responding to Dashboard. As the test Access-Request will not contain all attributes (such as Calling-Station-ID), see below for an example message.

8b3f1282-7edd-4108-9424-f4425537251f

You must to post a comment.
Last modified
16:58, 5 Apr 2016

Tags

Classifications

This page has no classifications.

Explore Meraki

You can find out more about Cisco Meraki on our main site, including information on products, contacting sales and finding a vendor.

Explore Meraki

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

Ask the Community

In the Meraki Community, you can keep track of the latest announcements, find answers provided by fellow Meraki users and ask questions of your own.

Visit the Community