![]() A good starting point when you’re planning to deploy RADIUS in your organization is RFC 6158, Radius Design Guidelines, published in March 2011. It was defined in by RFCs 20, which have since been made obsolete by new standards. RADIUS has been around since the early 1990s and is an IETF standard. It can also function as a RADIUS server or a RADIUS proxy, as we mentioned in Part 1 of this series. In Windows Server 2012, the Network Policy Service (NPS) can do more than just Network Access Protection (NAP). In Part 3, we’re going to discuss the process of setting up RADIUS servers. In Part 2, we shared some tips on actually deploying NAP on Windows Server 2012. In Part 1 of this series, we took a look at how the Network Policy and Access Services in Windows 2012, and particularly Network Access Protection (NAP) can help to protect your network when VPN clients connect to it by validating health requirements that you institute as part of a health enforcement plan. Understanding and Configuring Network Policy and Access Services in Server 2012 (Part 2).Understanding and Configuring Network Policy and Access Services in Server 2012 (Part 1).If you would like to read the orther parts in this article series please go to: If you would like to be notified of when Deb Shinder releases the next part in this article series please sign up to our Real-Time Article Update newsletter. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |