<?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: How To Display Which Processes Are Using What Ports</title>
	<atom:link href="http://devnulled.com/content/2008/02/how-to-display-which-processes-are-using-what-ports/feed/" rel="self" type="application/rss+xml" />
	<link>http://devnulled.com/content/2008/02/how-to-display-which-processes-are-using-what-ports/</link>
	<description>devnulled provides news, tips, resources, and articles about various topics that software developers and engineers enjoy.</description>
	<pubDate>Sun, 23 Nov 2008 16:20:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=abc</generator>
		<item>
		<title>By: freebsd vps</title>
		<link>http://devnulled.com/content/2008/02/how-to-display-which-processes-are-using-what-ports/#comment-393462</link>
		<dc:creator>freebsd vps</dc:creator>
		<pubDate>Tue, 26 Feb 2008 17:15:13 +0000</pubDate>
		<guid isPermaLink="false">http://devnulled.com/content/2008/02/how-to-display-which-processes-are-using-what-ports/#comment-393462</guid>
		<description>Nice tip.  I use 'netstat -anp &#124; grep LISTEN' on Linux which usually runs faster than lsof.  But it doesn't work the same on FreeBSD.</description>
		<content:encoded><![CDATA[<p>Nice tip.  I use &#8216;netstat -anp | grep LISTEN&#8217; on Linux which usually runs faster than lsof.  But it doesn&#8217;t work the same on FreeBSD.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bubbagimp</title>
		<link>http://devnulled.com/content/2008/02/how-to-display-which-processes-are-using-what-ports/#comment-393277</link>
		<dc:creator>Bubbagimp</dc:creator>
		<pubDate>Tue, 26 Feb 2008 12:31:52 +0000</pubDate>
		<guid isPermaLink="false">http://devnulled.com/content/2008/02/how-to-display-which-processes-are-using-what-ports/#comment-393277</guid>
		<description>Whoops, just to clarify -b shows the program that opened the port.  The option -o shows the PID.</description>
		<content:encoded><![CDATA[<p>Whoops, just to clarify -b shows the program that opened the port.  The option -o shows the PID.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bubbagimp</title>
		<link>http://devnulled.com/content/2008/02/how-to-display-which-processes-are-using-what-ports/#comment-393274</link>
		<dc:creator>Bubbagimp</dc:creator>
		<pubDate>Tue, 26 Feb 2008 12:29:03 +0000</pubDate>
		<guid isPermaLink="false">http://devnulled.com/content/2008/02/how-to-display-which-processes-are-using-what-ports/#comment-393274</guid>
		<description>In Vista and XP SP2 you can run "netstat -b" and it will show the process associated with the port.

In Vista the tricky part is, it requires an elevated command line window.  The easiest way to do this I found is to type "cmd" in the search portion of the start menu and hit ctrl-shift-enter to elevate the process.  Click continue to confirm the action.  You have to do this even if your account is set to Administrator.

Have I mentioned I hate Vista?</description>
		<content:encoded><![CDATA[<p>In Vista and XP SP2 you can run &#8220;netstat -b&#8221; and it will show the process associated with the port.</p>
<p>In Vista the tricky part is, it requires an elevated command line window.  The easiest way to do this I found is to type &#8220;cmd&#8221; in the search portion of the start menu and hit ctrl-shift-enter to elevate the process.  Click continue to confirm the action.  You have to do this even if your account is set to Administrator.</p>
<p>Have I mentioned I hate Vista?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
