<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Netsh Shortcuts</title>
	<atom:link href="http://blog.scottlowe.org/2008/02/04/netsh-shortcuts/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.scottlowe.org/2008/02/04/netsh-shortcuts/</link>
	<description>The weblog of an IT pro specializing in virtualization, storage, and servers</description>
	<lastBuildDate>Tue, 07 Feb 2012 13:34:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: DrGonzo</title>
		<link>http://blog.scottlowe.org/2008/02/04/netsh-shortcuts/comment-page-1/#comment-36499</link>
		<dc:creator>DrGonzo</dc:creator>
		<pubDate>Fri, 21 Mar 2008 15:02:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/02/04/netsh-shortcuts/#comment-36499</guid>
		<description>Good post

I&#039;ve also used netsh before to clear up problems with windows firewall and it&#039;s &#039;easily&#039; confused, whether enabled or disabled.

.....

netsh
interface ip
reset all
..
reset all
..
commit
quit

.....

then reboot. ;) This will also clear any static NIC configuration. I&#039;ve used this on countless production machines where windows firewall exceptions have been in existence for a long time but no longer seem to work. I usually disable WF after that. What a piece of crap.</description>
		<content:encoded><![CDATA[<p>Good post</p>
<p>I&#8217;ve also used netsh before to clear up problems with windows firewall and it&#8217;s &#8216;easily&#8217; confused, whether enabled or disabled.</p>
<p>&#8230;..</p>
<p>netsh<br />
interface ip<br />
reset all<br />
..<br />
reset all<br />
..<br />
commit<br />
quit</p>
<p>&#8230;..</p>
<p>then reboot. <img src='http://blog.scottlowe.org/wp-includes/images/smilies/icon_wink.gif' alt=';)' class='wp-smiley' />  This will also clear any static NIC configuration. I&#8217;ve used this on countless production machines where windows firewall exceptions have been in existence for a long time but no longer seem to work. I usually disable WF after that. What a piece of crap.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ecio</title>
		<link>http://blog.scottlowe.org/2008/02/04/netsh-shortcuts/comment-page-1/#comment-35306</link>
		<dc:creator>Ecio</dc:creator>
		<pubDate>Tue, 05 Feb 2008 08:36:20 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/02/04/netsh-shortcuts/#comment-35306</guid>
		<description>Hi Scott
talkin about netsh commands, it happened to me to have this problem: I received 5 laptops from Dell that had all the same problem, they couldnt get any IP address from the DHCP server while tcp/ip was working correctly when using static assigned ip (maybe a corrupt windows image? who knowns.. one month later a received other two identical laptops and they were ok). After spending some (too much) time tryin to figure out what the problem was, i found this useful blog post: http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html
that reported this netsh &quot;cleaning&quot; command:
&quot;netsh winsock reset catalog&quot; (for Win XP SP2)
After a reboot the problems was gone...</description>
		<content:encoded><![CDATA[<p>Hi Scott<br />
talkin about netsh commands, it happened to me to have this problem: I received 5 laptops from Dell that had all the same problem, they couldnt get any IP address from the DHCP server while tcp/ip was working correctly when using static assigned ip (maybe a corrupt windows image? who knowns.. one month later a received other two identical laptops and they were ok). After spending some (too much) time tryin to figure out what the problem was, i found this useful blog post: <a href="http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html" rel="nofollow">http://nitecruzr.blogspot.com/2005/05/problems-with-lsp-winsock-layer-in.html</a><br />
that reported this netsh &#8220;cleaning&#8221; command:<br />
&#8220;netsh winsock reset catalog&#8221; (for Win XP SP2)<br />
After a reboot the problems was gone&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

