<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0" xmlns:s="http://www.techrepublic.com/search" xmlns:dc="http://purl.org/dc/elements/1.1/"  xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
    <title><![CDATA[Discussion on Disable guest DHCP with Hyper-V DHCP Guard ]]></title>
    <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-393812]]></link>
    <atom:link rel="hub" type="application/rss+xml" href="http://pubsubhubbub.appspot.com/" />
    <atom:link rel="self" type="application/rss+xml" href="http://www.techrepublic.com/forum/discussions/102-393812/rss" />

    <description><![CDATA[]]></description>
    <language>en-us</language>
    <lastBuildDate>2013-05-18T21:13:37-07:00</lastBuildDate>
             

    <item>
        <title><![CDATA[Re: Disable guest DHCP with Hyper-V DHCP Guard]]></title>
        <link><![CDATA[http://www.techrepublic.com/forum/discussions/102-393812-3691088]]></link>
        <description><![CDATA[Seems like an interesting feature of the Hyper-V platform.  In addition to stopping a rogue DHCP server from causing havoc on a network environment, you also want to detect and correct the configuration issue.  You could also use a solution such as the Mancala Network Controller ( http://www.mancalanetworks.com ) which continuously monitors the network for rogue devices including DHCP servers. It provides immediate quarantine capabilities and identifies the rogue DHCP server's location whether it be a physical or virtual host. -rory]]></description>
        <guid><![CDATA[http://www.techrepublic.com/forum/discussions/102-393812-3691088]]></guid>
        <dc:creator><![CDATA[rory.higgins]]></dc:creator>
        <pubDate>Mon, 06 Aug 2012 07:46:25 -0700</pubDate>
    </item>
    </channel>
</rss>

