Robert Larson

My feedback

  1. 123 votes
    Sign in
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    32 comments  ·  Networking » Firewall  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    Robert Larson commented  · 

    October 30, 2019 and this issue still exists. I too wasted many (MANY) hours trying to solve this before I finally just had the bright idea of turning the Windows firewall off. Voila, fixed. Then I turned it on, made my 1812,1813 rule and all was well.

    I tried the "sc sidtype IAS unrestricted" fix mentioned below and I can report that that command didn't fix things for me. Anyone have a more permanent fix? Is Microsoft going to patch this?

    What's really weird also is that I deployed 5 NPS servers for this project globally. It worked fine on two of them. And failed on 2 of them. The fifth one hasn't been tested just yet. So it works 50% of the time? That's really strange. All were identical clean builds of Windows 2019. The only major difference is that on the sites that work the hypervisor used is Hyper-V and where it doesn't work it was ESXi. But I can't imagine that has anything to do with this problem. Could it?

Feedback and Knowledge Base