RAD-Series RADIUS Server Product Support

1. Request from unknown client error message in the logfile?

The error cause depends on how long those error messages last after starting up the RAD-Series RADIUS Server. It might not be an error. The RAD-Series RADIUS Server has its own mechanism for DNS queries in order to never block the main RAD-Series Server process. Upon start up of the RAD-Series RADIUS Server, those DNS entries appear in the clients file, but are not yet in the server's local buffer, so this message may appear in the logfile. It should disappear in a few minutes. If not, then it's a real error.

The first thing to check is the DNS for the clients file entries. It may be that they don't have an entry in the DNS database. The RAD-Series RADIUS Server needs to run on a machine with an IP address and forward and reverse DNS entries.

2. The RADIUS Server log shows “Authentication OK” but the wireless session does not pass data.

The session will fail even after the user is authenticated if the Access Point does not receive the necessary attributes to establish the session.  This is seen most often in cases where the protocol supports dynamic key distribution, but the correct vendors have not been selected when configuring the Access Device in the RAD-Series Server.  If a protocol supporting dynamic key distribution is being used, then add Microsoft to the list of vendors for the Access Device.

3. RADIUS Server fails to start with “Address already in use” error message.

The RAD-Series RADIUS Server uses two UDP ports for communication.  By default these ports are 1812 and 1813.  If these ports are already assigned to another process then the server will not start.  It will report either a “bind error” or an “address already in use” error.  Either these ports must be released, or the RAD-Series Server must use different ports.  The RAD-Series RADIUS Server can be configured to use different ports on the Start Options Screen.  If the RAD-Series Server is configured to use different ports, then the Access Points must also be re-configured to communicate with the RAD-Series Server on the new ports.

4. RADIUS Server Manager fails to start.

If the Server Manager fails to start, it may be that one of the ports it uses for web access (8080 by default) or control (8007 and 8009) is already in use.  The RAD-Series RADIUS Server can be configured to use different ports by editing server.xml (found in /opt/tomcat/conf for Unix systems and
c:\Program Files\InterlinkNetworks\ServerManager\conf for Windows 2000 systems).

5. RADIUS Server Reporting Problems

Technical support for RAD-Series RADIUS Server includes the Evaluation Server is available during the 30-day warranty period and during the life of the maintenance plan. For problems and questions not covered in the documentation, please contact our technical support team.