NPS Proxy : Error: Log 6273 / Username=Mac-Adress of the Win10 PC instead of the NomPC

Emeric Martin 1 Reputation point
2021-07-21T12:53:28.887+00:00

Hello,

I am currently working to set up a Windows Server 2019 Standard NPS-Radius topology:

  • 2 Srv Proxy-NPS-Radius
  • 2 Srv NPS-Radius
  • Radius client (HP Aruba switch) - 802.1x & MAC
  • Win10 PC

Scenario 1:

  • Test connection via proxy-NPS-Radius1 (Connection OK with the 2 NPS-Radius).

Scenario 2:

  • Export Conf NPS : Proxy-NPS-Radius1
  • Import NPS Conf: Proxy-NPS-Radius2
  • Connection test via Proxy-NPS-Radius2 (Error: Log 6273 / Username=Mac-Adress of the Win10 PC instead of the NomPC116697-incident-radius2.png).

Can you help me with this problem?

Thanks in advance.

Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,581 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Candy Luo 12,686 Reputation points Microsoft Vendor
    2021-07-22T02:18:36.427+00:00

    Hi ,

    Based on my understanding, you have two NPS proxy server, one NPS proxy server (Proxy-NPS-Radius1)works fine. If you export the configuration from Proxy-NPS-Radius1 and import the configuration to Proxy-NPS-Radius2, connection will fail and the problem is that Username=Mac-Address of the Win10 PC instead of the computer name. Is that right? Please feel free to let me know if I have any misunderstanding.

    Please manually configure the same configurations as Proxy-NPS-Radius1 on Proxy-NPS-Radius2 and then see if the issue still occurs. There might be some problems when you export and import the configuration, try to test the manually configuration.

    Best Regards,
    Candy

    --------------------------------------------------------------

    If the Answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments