<?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>Testing DirectAccess on Hyper-V?  Use Legacy NICs</title><link>http://blogs.technet.com/b/wincat/archive/2009/05/14/testing-directaccess-on-hyper-v-use-legacy-nics.aspx</link><description>We recently released the DirectAccess Step by Step Guide and many customers are using it to start understanding and testing DirectAccess in their labs, which is great. However, if you're planning to virtualize your lab environment on Hyper-V, you should</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Testing DirectAccess on Hyper-V?  Use Legacy NICs</title><link>http://blogs.technet.com/b/wincat/archive/2009/05/14/testing-directaccess-on-hyper-v-use-legacy-nics.aspx#3376248</link><pubDate>Tue, 21 Dec 2010 02:30:26 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3376248</guid><dc:creator>Thanks for this - it fixed my issue.</dc:creator><description>&lt;p&gt;Maybe an update to the DA guide would help others? It would have helped me save the 4 days troubleshooting this.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3376248" width="1" height="1"&gt;</description></item><item><title>re: Testing DirectAccess on Hyper-V?  Use Legacy NICs</title><link>http://blogs.technet.com/b/wincat/archive/2009/05/14/testing-directaccess-on-hyper-v-use-legacy-nics.aspx#3248301</link><pubDate>Sun, 31 May 2009 17:14:15 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3248301</guid><dc:creator>Crash</dc:creator><description>&lt;p&gt;I'm using legacy nic's and still having the issue with not being able to communicate with DNS. &amp;nbsp;I've disabled the DA GPO's for esting. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;I had dns setup only on my DC and for testing purposes and found that as soon as I enabled DA and forced a policy update that I lost all connectivity with DNS and gpo would not update again due to not being able to find the DC. &amp;nbsp;After that it's a rebuild or reapply a snapshot that was taken prior to policy being applied.&lt;/p&gt;
&lt;p&gt;To get around that issue, I've installed DNS on my DA Server as a secondary zone and use it for all the DNS settings. &amp;nbsp;At this point the the monitoring tab shows that DNS is fine. &amp;nbsp;As soon as I enable the DA server GPO DNS shows as failing in DA monitoring. &amp;nbsp;As soon as I disable GPO and force a policy update DNS shows it it running properly. &amp;nbsp;&lt;/p&gt;
&lt;p&gt;I've narrowed the settings down to the three connection security rules, but at this point I am unsure if I just have a configuration issue or if there is an issue with the way DA configures the actual policies.&lt;/p&gt;
&lt;p&gt;I have yet to start troubleshooting the Win 7 client policy, but the same thing happens on the client. &amp;nbsp;With the exception that as soon as policy is applied you can not ping anything internal by fqdn, but you can ping by netbios. &amp;nbsp;At that points it's revert to a previous snapshot.&lt;/p&gt;
&lt;p&gt;I've rebuilt the Hyper-V lab 3 times now using the guide linked above. &amp;nbsp;I did leave out the inet server since i have static ip's from my isp already. &amp;nbsp;I'm assuming that shouldn't be an issue at this time considering I can't get the internal communication up and running yet.&lt;/p&gt;
&lt;p&gt;Any suggestions for me offhand? &amp;nbsp;I've responded to a similar post on Technet under Server 2008 R2 Networking to see if anyone else is having the same issue. &lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2networking/thread/4ae72bee-0590-4f56-beed-ea6265329f74"&gt;http://social.technet.microsoft.com/Forums/en-US/windowsserver2008r2networking/thread/4ae72bee-0590-4f56-beed-ea6265329f74&lt;/a&gt; &amp;nbsp;&lt;/p&gt;
&lt;p&gt;Thanks for any help you may have to offer&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3248301" width="1" height="1"&gt;</description></item></channel></rss>