Share via

Windows Server 2019 NPS (Network Policy Server) - SOLVED

Pierre N 11 Reputation points
2020-09-17T02:25:59.787+00:00

Because there were too many confusions by some moderators and other people, I read on other different pages with the same given solution to the problem to authenticate through NPS.

On that server for Windows Server 2019, open Command and type the following:

  • sc sidtype IAS unrestricted

After a success message, restart the server.

I was able to authenticate through my phone, but my laptop didn't except through VPN on the second server from this one.

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
3,534 questions

8 answers

Sort by: Newest
Most helpful Newest Oldest
  1. Herman Agida 0 Reputation points
    2023-07-21T12:12:18.8333333+00:00

    This resolved my problem after troubleshooting for 3 weeks. Thanks

    "On Windows Server 2019 with NPS role installed, open an admin command prompt & run the following command:"

    1.sc sidtype IAS unrestricted

    2.Reboot the server

    3.Attempt the connection

    0 comments
  2. Pierre N 11 Reputation points
    2020-09-22T04:29:52.727+00:00

    SSTP is back up. I enabled TLS 1.2 before uninstalling and reinstalling RRAS in Server 2019 VPN. But L2TP has a processing error. L2TP and SSTP works on Server 2016 with no bugs. (One running NPS and other running VPN both on Server 2016)

    Overall, The bugs are in Server 2019 for NPS (Windows 10 computers cannot connect, even Windows 10 Mobile)

    The NPS and VPN will work correctly in Server 2016. There are some defects in Server 2019

  3. Candy Luo 12,676 Reputation points Microsoft Vendor
    2020-09-22T04:23:18.583+00:00

    Hi ,

    From your screenshot, VPN and DC are installed on the same machine? We did not recommend install VPN and DC on the same machine.

    Let's sort out the current problem. Based on my understanding, your issue is that WIFI authentication for windows machine not work with NPS server 2019. Is that right? Please feel free to let me know if my understanding is wrong. If yes, please refer to the following steps:

    1. Carefully review the authentication policy on both the client and server to ensure they match.
    2. When you cannot connect to the WIFI network, what's the error message keep popping?
    3. Please enable firewall logging on the NPS server to log both allowed and dropped packets. Connect to the WIFI network again, and observe the NPS's firewall logs. Check if NPS server's firewall is dropping RADIUS authentication packets.

    Best Regards,

    Candy

    0 comments
  4. Candy Luo 12,676 Reputation points Microsoft Vendor
    2020-09-22T03:05:52.263+00:00

    Did you mean run the command of sc sidtype IAS unrestricted and restart the NPS server still doesn't work?

    It might be that the default Windows firewall rules to allow inbound UDP port 1812 (RADIUS authentication) and inbound UDP port 1813 (RADIUS accounting) on NPS server do not work.

    To do the troubleshooting, you can enable firewall logging on the NPS server to log both allowed and dropped packets. Attempt VPN connection and observe the firewall logs. Then you might see the firewall is dropping packets inbound on UDP port 1812, as the picture below:

    26341-image.png

    Run the command on the NPS server side：

    26329-image.png

    26351-image.png

  5. Pierre N 11 Reputation points
    2020-09-22T02:35:50.547+00:00

    For (Get-NetFirewallRule -DisplayGroup "Network Policy Server" | where DisplayName -like "RADIUS" | Set-NetFirewallRule -Service Any), what do I do for this phrase? Do I go to firewall? I need a breakdown on how to do this. I did the command part already with (sc sidtype IAS unrestricted)

    Also Is the port for 1812 and 1813 on server side or client side? Does TLS need to be enabled?

    Also as an idea, if someone can compare both server setting, they can find out what's really going on with Server 2019

    0 comments