<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.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>Network Location Awareness (NLA) and how it relates to Windows Firewall Profiles</title><link>http://blogs.technet.com/b/networking/archive/2010/09/08/network-location-awareness-nla-and-how-it-relates-to-windows-firewall-profiles.aspx</link><description>I am writing this blog post because we get a lot of questions regarding how NLA determines a network profile and how it relates to Firewall Profiles as the two are often confused. What is NLA? First let’s start with what NLA does. For each network interface</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Network Location Awareness (NLA) and how it relates to Windows Firewall Profiles</title><link>http://blogs.technet.com/b/networking/archive/2010/09/08/network-location-awareness-nla-and-how-it-relates-to-windows-firewall-profiles.aspx#3497689</link><pubDate>Sun, 13 May 2012 19:15:35 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3497689</guid><dc:creator>JuanAnD</dc:creator><description>&lt;p&gt;Great article! Could you edit with some details about Windows 8?&lt;/p&gt;
&lt;p&gt;Thanks!&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3497689" width="1" height="1"&gt;</description></item><item><title>re: Network Location Awareness (NLA) and how it relates to Windows Firewall Profiles</title><link>http://blogs.technet.com/b/networking/archive/2010/09/08/network-location-awareness-nla-and-how-it-relates-to-windows-firewall-profiles.aspx#3374160</link><pubDate>Thu, 09 Dec 2010 17:21:44 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3374160</guid><dc:creator>dmstrouse</dc:creator><description>&lt;p&gt;Could you explain how NLA is affected by IPSec? &amp;nbsp;&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3374160" width="1" height="1"&gt;</description></item><item><title>re: Network Location Awareness (NLA) and how it relates to Windows Firewall Profiles</title><link>http://blogs.technet.com/b/networking/archive/2010/09/08/network-location-awareness-nla-and-how-it-relates-to-windows-firewall-profiles.aspx#3361368</link><pubDate>Tue, 12 Oct 2010 08:19:09 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3361368</guid><dc:creator>Argon.pro</dc:creator><description>&lt;p&gt;Dear Enterprise Networking Team,&lt;/p&gt;
&lt;p&gt;I want to test DirectAccess in virtual environment, so i&amp;#39;ve installed to WS2008R2 virtual machine, wich serves as ipv4/v6 router from test to production network additional NIC, and configuret it with random non-private ip addresses&lt;/p&gt;
&lt;p&gt;88.10.0.1&lt;/p&gt;
&lt;p&gt;88.10.0.2&lt;/p&gt;
&lt;p&gt;no default router, no dns.&lt;/p&gt;
&lt;p&gt;Windows detects this NIC as Domain, so i cannot enable DirectAccess. This NIC connected to &amp;nbsp;virtual network dedicated for win7 test clients only.&lt;/p&gt;
&lt;p&gt;What should i do o make this NIC detected as Public?&lt;/p&gt;
&lt;p&gt;Kind regrds,&lt;/p&gt;
&lt;p&gt;Igor Romanovsky&lt;/p&gt;
&lt;p&gt;MCITP: EA, EMA, VA; MCSA&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3361368" width="1" height="1"&gt;</description></item></channel></rss>