Quantcast
Channel: Network Access Protection forum
Viewing all articles
Browse latest Browse all 1875

NAP clients are evaluated as non NAP-capable

$
0
0

Hi all,

our setup consists of a AD domain, Remote Desktop Gateway server, NPS/NAP server and a few Windows 7 clients.

The RDG and NPS are set up and running with all Connection Request & Network policies and everything is well, except for NAP health checks. Whatever I do on client it is evaluated as non NAP-capable.

I start NAP Agent (napagent) service, enable Remote Desktop Gateway quarantine client in NAP Client config MMC (napclcfg.msc) and add my RDG URL https://rdg.company.com to Trusted Gateways list to no avail, the client Windows 7 machine ends up as "non NAP-capable".

netsh nap client show state command's output is fine too, everything looks ok as it should be according to NAP Quick Fixes: https://msdn.microsoft.com/en-us/library/dd348494(v=ws.10).aspx

In event viewer of client machine I see NAP events from which I can guess that everything's ok from client's perspective too, client 79621 is successfully initialized and SystemHealthAgent seems to scan and (supposedly) succesfully build a SoH.

Still, obviously NAP server does not get a SoH from a client and thus classifies it as non NAP-capable for some weird reason.

Since I haven't found any further means to investigate and troubleshoot it, I would be grateful for any ideas and/or suggestions.

Thanks a lot,


Viewing all articles
Browse latest Browse all 1875

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>