<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: DHCP versus Static IP</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/dhcp-versus-static-ip/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/dhcp-versus-static-ip/</link>
	<description></description>
	<pubDate>Fri, 19 Mar 2010 13:14:55 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Syphun</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/dhcp-versus-static-ip/#comment-69516</link>
		<dc:creator>Syphun</dc:creator>
		<pubDate>Mon, 26 Oct 2009 19:56:09 +0000</pubDate>
		<guid isPermaLink="false">#comment-69516</guid>
		<description>I so much agree with mrdenny, the basic fact remains that DHCP is the one and only way to create less work for the network admin and as well secure your network if you know the right things to do with your GPO on the server.
Static IP will only create more trouble. . . .STAY OFF IT if you can.. . . and i know you can. . .</description>
		<content:encoded><![CDATA[<p>I so much agree with mrdenny, the basic fact remains that DHCP is the one and only way to create less work for the network admin and as well secure your network if you know the right things to do with your GPO on the server.<br />
Static IP will only create more trouble. . . .STAY OFF IT if you can.. . . and i know you can. . .</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mrdenny</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/dhcp-versus-static-ip/#comment-69434</link>
		<dc:creator>mrdenny</dc:creator>
		<pubDate>Fri, 23 Oct 2009 18:53:50 +0000</pubDate>
		<guid isPermaLink="false">#comment-69434</guid>
		<description>If you have wireless networks, those network should be secured using a key through WPA or WEP key so that if random people walk up to your WiFi network with a laptop they can't connect to the network, and therefor can't get an IP address.

If a corporate environment you can deploy the keys and SSID to the computer via GPO so that all company laptops can connect to the wireless without having to give the users the key.</description>
		<content:encoded><![CDATA[<p>If you have wireless networks, those network should be secured using a key through WPA or WEP key so that if random people walk up to your WiFi network with a laptop they can&#8217;t connect to the network, and therefor can&#8217;t get an IP address.</p>
<p>If a corporate environment you can deploy the keys and SSID to the computer via GPO so that all company laptops can connect to the wireless without having to give the users the key.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jayaram</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/dhcp-versus-static-ip/#comment-69362</link>
		<dc:creator>Jayaram</dc:creator>
		<pubDate>Thu, 22 Oct 2009 16:07:59 +0000</pubDate>
		<guid isPermaLink="false">#comment-69362</guid>
		<description>Mrdenny,

1.  A wireless device that gets within range of your wireless network equipment may be able to acquire an IP address from your router. this is for more security purpose.


 2.  For small networks like a home network, you can add some extra protection by turning off the DHCP, or automatic IP addressing, feature of the router and manually assigning static IP addresses. 

 At the end the above is for more security purpose.</description>
		<content:encoded><![CDATA[<p>Mrdenny,</p>
<p>1.  A wireless device that gets within range of your wireless network equipment may be able to acquire an IP address from your router. this is for more security purpose.</p>
<p> 2.  For small networks like a home network, you can add some extra protection by turning off the DHCP, or automatic IP addressing, feature of the router and manually assigning static IP addresses. </p>
<p> At the end the above is for more security purpose.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mshen</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/dhcp-versus-static-ip/#comment-69236</link>
		<dc:creator>Mshen</dc:creator>
		<pubDate>Mon, 19 Oct 2009 23:24:39 +0000</pubDate>
		<guid isPermaLink="false">#comment-69236</guid>
		<description>Static addresses isn't the best way to do it; there is too much administrative overhead and little added security.  Look into Network Access Control (NAC), Switchport security on the switch, or MAC Access-lists on the switch.</description>
		<content:encoded><![CDATA[<p>Static addresses isn&#8217;t the best way to do it; there is too much administrative overhead and little added security.  Look into Network Access Control (NAC), Switchport security on the switch, or MAC Access-lists on the switch.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sonotsky</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/dhcp-versus-static-ip/#comment-69209</link>
		<dc:creator>Sonotsky</dc:creator>
		<pubDate>Mon, 19 Oct 2009 13:13:33 +0000</pubDate>
		<guid isPermaLink="false">#comment-69209</guid>
		<description>Agreed with all responses to date.

If by "security", management wants to know which IP is causing certain traffic (and by extension, which workstation), then reserved addresses in dhcp works well.  Yes, it's possible for the user to change their MAC to attempt to obtain a different IP, but if the user has that much access to their workstation, then I think the network is the wrong place to be looking to improve security...</description>
		<content:encoded><![CDATA[<p>Agreed with all responses to date.</p>
<p>If by &#8220;security&#8221;, management wants to know which IP is causing certain traffic (and by extension, which workstation), then reserved addresses in dhcp works well.  Yes, it&#8217;s possible for the user to change their MAC to attempt to obtain a different IP, but if the user has that much access to their workstation, then I think the network is the wrong place to be looking to improve security&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KevinBeaver</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/dhcp-versus-static-ip/#comment-69204</link>
		<dc:creator>KevinBeaver</dc:creator>
		<pubDate>Mon, 19 Oct 2009 12:37:11 +0000</pubDate>
		<guid isPermaLink="false">#comment-69204</guid>
		<description>I can't think of much value this would add from a security perspective. If anything it'll just create more work on the network administration side and end up increasing business risks.</description>
		<content:encoded><![CDATA[<p>I can&#8217;t think of much value this would add from a security perspective. If anything it&#8217;ll just create more work on the network administration side and end up increasing business risks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Yasirirfan</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/dhcp-versus-static-ip/#comment-69183</link>
		<dc:creator>Yasirirfan</dc:creator>
		<pubDate>Sun, 18 Oct 2009 04:44:08 +0000</pubDate>
		<guid isPermaLink="false">#comment-69183</guid>
		<description>Yeah I agree with Mrdenny,  DHCP is the best way to manage the IP address assignement, if you are using Static IP address then you have to document them so that no duplication occurs. As far as Management devices such as Servers, Switches , routers and access points are concerned  static IPs are recommended.</description>
		<content:encoded><![CDATA[<p>Yeah I agree with Mrdenny,  DHCP is the best way to manage the IP address assignement, if you are using Static IP address then you have to document them so that no duplication occurs. As far as Management devices such as Servers, Switches , routers and access points are concerned  static IPs are recommended.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- dynamic -->