<?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>Home Hyper-V Networking Gotchas</title><link>http://blogs.technet.com/tristank/archive/2009/01/13/home-hyper-v-networking-gotchas.aspx</link><description>Before the holidays, I bought myself an early present: a new quad-core box with 4GB RAM, which I was going to use for a home Hyper-V lab, so that I could run a bunch of 64-bit VMs as well as the 32-bit staples I’ve been using for years (SBS 2003, and</description><dc:language>en-AU</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Home Hyper-V Networking Gotchas</title><link>http://blogs.technet.com/tristank/archive/2009/01/13/home-hyper-v-networking-gotchas.aspx#3185004</link><pubDate>Sat, 17 Jan 2009 13:00:42 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3185004</guid><dc:creator>dmuscett</dc:creator><description>&lt;p&gt;I had not spotted that registry hack, months ago when I built my hyperV home setup.... therefore I have DHCP installed on the ISA Server virtual machine I always keep turned on, only bound to the &amp;quot;internal&amp;quot; NIC... the HyperV host has two NICs, but effectively communicated to the Internet THRU the virtualized ISA on the one that is &amp;quot;internal&amp;quot;... the other one is used for the ISA to go to the router, but the host does not use it.&lt;/p&gt;
</description></item><item><title>re: Home Hyper-V Networking Gotchas</title><link>http://blogs.technet.com/tristank/archive/2009/01/13/home-hyper-v-networking-gotchas.aspx#3185139</link><pubDate>Sun, 18 Jan 2009 01:51:32 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3185139</guid><dc:creator>tristank</dc:creator><description>&lt;p&gt;Gotcha, good solution. My ISA Server is an optional web proxy, I just point Auto Detect clients at it through WPAD (I have an Xbox 360 on the network, so I don't want any port filtering to happen at the ISA box for that).&lt;/p&gt;
&lt;p&gt;That said... I'm thinking I might put Forefront TMG on the host for general filtering and firewalling (or just WS2008 R2), and use the virtualized adapters to provide a dedicated &amp;quot;passthrough&amp;quot; router for the Xbox.&lt;/p&gt;
</description></item><item><title>re: Home Hyper-V Networking Gotchas</title><link>http://blogs.technet.com/tristank/archive/2009/01/13/home-hyper-v-networking-gotchas.aspx#3185210</link><pubDate>Sun, 18 Jan 2009 12:07:39 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3185210</guid><dc:creator>dmuscett</dc:creator><description>&lt;p&gt;I also use WPAD, and I have an old XBox, and a Nintendo Wii, and a bunch of other devices that might need to go out unfiltered and/or unauthenticated: I just give them always the same IP Address thru RESERVATIONS in DHCP, and I let those IP out. All the rest in the dynamic IP range (=my kids and my wife's PCs) are allowed to go out for a few protocols, and have authenticated/filtered HTTP access (kids only have a whitelist of &amp;quot;allowed&amp;quot; sites... :-))&lt;/p&gt;
&lt;p&gt;I am using virtual adapters for a sort of &amp;quot;DMZ&amp;quot;, where I keep TEST machines that are in separate domains and don't have anything to do with &amp;quot;production&amp;quot; :-) ... so I can still send them out for WindowsUpdate, but they don't send crap (even just browser elections or any enumeration of stuff) out to my real internal net.&lt;/p&gt;
</description></item><item><title>re: Home Hyper-V Networking Gotchas</title><link>http://blogs.technet.com/tristank/archive/2009/01/13/home-hyper-v-networking-gotchas.aspx#3185217</link><pubDate>Sun, 18 Jan 2009 13:04:17 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3185217</guid><dc:creator>tristank</dc:creator><description>&lt;p&gt;Yup - I found the ISA NAT implementation didn't mix with the 360 too well last time I tried it... I might give it another whirl with TMG.&lt;/p&gt;
&lt;p&gt;I love being able to set up purely internal virtual networks where my virtual hosts congregate; I wonder if I could use that to perform a sneaky passthrough for the ISA host (connect the parent to a virtual network, and have ISA downstream of a virtual RRAS box (kinda what I did in the past, though more complicated))... best of both worlds... :)&lt;/p&gt;
</description></item><item><title>re: Home Hyper-V Networking Gotchas</title><link>http://blogs.technet.com/tristank/archive/2009/01/13/home-hyper-v-networking-gotchas.aspx#3190888</link><pubDate>Fri, 23 Jan 2009 22:01:31 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3190888</guid><dc:creator>Rick</dc:creator><description>&lt;p&gt;I just bought a Q8300 as it was on the Intel list posted as having VT.. &lt;a rel="nofollow" target="_new" href="http://www.intel.com/products/processor_number/chart/core2quad.htm"&gt;http://www.intel.com/products/processor_number/chart/core2quad.htm&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;It did not work, and it appears from the following that it does not have VT! &lt;a rel="nofollow" target="_new" href="http://ark.intel.com/cpu.aspx?groupId=39107"&gt;http://ark.intel.com/cpu.aspx?groupId=39107&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;What a waste of money.. I only bought it to setup a hyper-v test machine!&lt;/p&gt;</description></item></channel></rss>