Troubleshooting

Server does not start

First, check error log file for any possible errors. To learn more about, it see the Logging article. If log file does not exist at all or has no recent entries with current date and time, check Windows Event Viewer for ClearBox Server errors.

To open it, select "Start" menu, "Programs", "Administrative Tools", "Event Viewer". Select "Application Log" item and locate the latest entry with "Type" equal to "Error" and "Source" column equal to "ClearBox Server". Double-click an entry to see an error message.

If an error is found, see Errors list for the explanation of the error and a possible solution. If it does not help, look here for further recommendations.

Both log file and Event Viewer can be accesses quickly from Server Manager. Open Server Manager, connect to the server (even if it's stopped), and click Event Viewer or Error Logs buttons on the Service Management tab.

Most Frequent Errors

There's number of errors made most frequently. Check out if your problem is described here:

• Shared secrets are not configured properly (you may read more about them here). Make sure that you have defined secrets on both server side and client side (read more). Symptoms: you see errors #434, #456, #498, #499, #500 (make sure the secrets are equal), errors #415, #520 (you should create an entry for this client since it's missing) in the errors log.
• UDP ports are already used by some other applications (mostly possible by another RADIUS server or by the 'Routing and Remote Access' Windows service). Either stop that applications or configure the server to use different port numbers (1712/1713 instead of 1812/1813, for instance). Symptoms: you see error #477, #478, #480 in the errors log with additional information "address in use".
• You didn't complete the installation of the server properly. Make sure you've done this. Symptoms: you see error #417, #472, #473 in the errors log.

Using Client Tool

This tool can be used to check if ClearBox Server is running and operates normally. It can emulate any RADIUS/TACACS-enabled NAS with any vendor-specific attributes included in Access-Request and Accounting requests.

See Client Tool Help for more details.