<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Providing 802.1x Enforcement for Network Access Protection</title><link>http://blogs.msdn.com/b/wndp/archive/2006/05/10/winhec-blog-nap-2.aspx</link><description>We’re living in a highly connected world, where a large number of diverse devices gain access to the corporate environment using diverse technologies like wireless, wired 802.1x, virtual private networks (VPN), and more. Though this diversity is a great</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>Providing 802.1x Enforcement for Network Access Protection</title><link>http://blogs.msdn.com/b/wndp/archive/2006/05/10/winhec-blog-nap-2.aspx#595578</link><pubDate>Thu, 11 May 2006 22:16:53 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:595578</guid><dc:creator>Network Access Protection (NAP)</dc:creator><description>Post from the NAP Development Manager, Mudit Goel, on our sister blog (wndp):&lt;br&gt;&lt;a rel="nofollow" target="_new" href="http://blogs.msdn.com/wndp/archive/2006/05/10/Winhec_blog_nap_2.aspx"&gt;http://blogs.msdn.com/wndp/archive/2006/05/10/Winhec_blog_nap_2.aspx&lt;/a&gt;...&lt;img src="http://blogs.msdn.com/aggbug.aspx?PostID=595578" width="1" height="1"&gt;</description></item></channel></rss>