I need to create a support request for our NPS solution (Radius) but I get the following message:

Anonymous
2023-11-15T17:26:57+00:00

I need to create a support request for our NPS solution (Radius) but I get the following message:

"Nous n’avons pas pu trouver de plan de support éligible associé à votre compte. Veuillez ajouter un plan de support parmi les options ci-dessous."

"We couldn't find an eligible support plan associated with your account. Please add a support plan from the options below."

Can you help me because Our NPS main node has fallen.

Windows for business | Windows Server | Networking | Network connectivity and file sharing

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Anonymous
    2023-11-16T09:26:15+00:00

    Hello BOSCHUNG Vincent,

    We apologize, but as technical engineers, we can only offer tech support pertaining to your particular concerns.

    To troubleshoot this issue, here are a few suggestions:

    1. Check NPS Configuration:
      • Ensure that your Network Policy Server (NPS) is properly configured. Confirm the following:
        • Domain Membership: Determine in which domain the NPS is a member. For multi-domain environments, the NPS can authenticate credentials for user accounts in its own domain and for all domains that trust the local domain of the NPS.
        • RADIUS Ports: Verify the RADIUS ports used by the NPS to receive messages from RADIUS clients. The default ports are UDP 1812 and 1645 for authentication, and 1813 and 1646 for accounting.
        • Event Logging: Decide which types of events you want NPS to record in the Event Log (e.g., rejected or successful authentication requests).
        • Fault Tolerance: Deploy at least two NPS servers for fault tolerance. One serves as the primary RADIUS server, and the other as a backup. Configure RADIUS clients on both servers to ensure continuity.
        • Configuration Script: Consider using a script to copy NPS configuration across servers to save administrative effort and prevent misconfigurations.
    2. Add RADIUS Clients:
      • Make sure your RADIUS clients (network access servers) are correctly configured to communicate with the NPS. Add the IP addresses of your clients as RADIUS clients in the NPS server.
    3. Check Firewall and Access Point Configuration:
      • Verify that your firewall and access point settings allow communication between the NPS and RADIUS clients.
    4. Enable NPS Logs:
      • If the issue persists, enable NPS logs to gain insights. In NPS, right-click on NPS (Local), go to Properties > General Tab, and ensure both successful and rejected authentication requests are checked.

    Remember, NPS provides authentication, authorization, and accounting for RADIUS requests. 

    Plan NPS as a RADIUS server | Microsoft Learn

    Remote RADIUS Server Groups | Microsoft Learn

    I hope this helps you get your NPS main node back up and running!

    Regards,

    Karlie

    0 comments No comments