If you suspect the Mi-Token RADIUS plugin is not working properly, here are some troubleshooting steps:


  1. Verify that the RADIUS client IP address and shared secret are correctly configured in NPS.
  2. Check that the Mi-Token AD LDS service is running on the server. You can check this in the Windows Services console.
  3. Confirm the NPS service itself is running.
  4. In the NPS management console, check the Mi-Token RADIUS snap-in's Status node. You should see regular "heartbeat" events there indicating the plugin is operational.
  5. Review the Windows Event logs (Application, System and Mi-Token) for any error messages related to the RADIUS plugin.
  6. Use the Microsoft ldp.exe tool to connect to the Mi-Token AD LDS instance LDAP port and verify it is responding properly.
  7. Check the RADIUS plugin's registry settings to ensure they refer to the correct AD LDS instance and port.
  8. If the authentication request is coming from a separate device, ensure any firewalls between the device and the Mi-Token server are allowing the RADIUS traffic.


If none of these steps identify the problem, gather the relevant logs and configuration data and open a support case with Mi-Token for further troubleshooting.