Forum Discussion

Copper Contributor

Nov 06, 2019

NTRadPing gets rejected by Win2016 NPS

Hi all, I am trying to fathom NPS (RADIUS) in Windows Server 2016, but all efforts are failing. I have peeled back to just a basic client (Win10) to server connection on the same LAN and using NT...

networking

Windows Server

DeeRex

Copper Contributor

May 20, 2020

jay26cee Try changing your condition from "Access Client IPv4 Address" to "Client IPv4 Address"

Also make sure you enable logging under Accounting and create your log files in a format you can manage. Because you are being rejected by NPS, it doesn't create an Event Log entry, but it will record in the NPS accounting logs.

When creating your Network Policy, start at the widest breadth - only one condition. Make sure it works, then add another. Same for any constraints. Get it working at the lowest level, then build additional complexity.

*Source*

I'm running two NPS on Server 2016 with two network policies, including one that is only client IP (used for health monitor) and one that is a bit more extensive. The client IP one had the same issue until I changed the condition.

jay26cee
Copper Contributor
May 20, 2020
DeeRex Thanks. Will have to look into this in the near future - got a lot going on right now.

Will update once done.
- mmendozaf
  Copper Contributor
  Jun 08, 2020
  jay26cee I'm in the same error ? Did you manage to solve it ?
  - jay26cee
    Copper Contributor
    Jun 08, 2020
    mmendozaf - unfortunately, I have not been able to revisit this yet. Have a look at what DeeRex wrote and see what you can do? I might only get a change to look into this in a couple of weeks. But, I will definitely post any updates on here.