<?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: Fixing WinSock and TCP/IP Meltdowns</title>
	<atom:link href="http://gopaultech.com/blog/2007/01/fixing-winsock-and-tcpip-meltdowns/feed/" rel="self" type="application/rss+xml" />
	<link>http://gopaultech.com/blog/2007/01/fixing-winsock-and-tcpip-meltdowns/</link>
	<description>::Technology is Power::</description>
	<lastBuildDate>Wed, 01 Sep 2010 15:29:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Windows Networking Troubleshooting &#183; PaulTech</title>
		<link>http://gopaultech.com/blog/2007/01/fixing-winsock-and-tcpip-meltdowns/comment-page-1/#comment-527</link>
		<dc:creator>Windows Networking Troubleshooting &#183; PaulTech</dc:creator>
		<pubDate>Thu, 25 Jan 2007 13:07:02 +0000</pubDate>
		<guid isPermaLink="false">http://gopaultech.com/blog/2007/01/19/fixing-winsock-and-tcpip-meltdowns/#comment-527</guid>
		<description>[...] Sometimes your tcpip stack or winsock is royally hosed.  Yes, that&#8217;s a technical term.  You can find some helps on my recent tcpip and winsock troubleshooting post.  Give that a whirl.  Now, make sure your computers are in the same workgroup.  You can find this by going to &#8220;Start,&#8221; &#8220;Control Panel,&#8221; and &#8220;System.&#8221;  You will see a &#8220;computer name&#8221; tab - click it.  This will show your workgroup.  If it&#8217;s not in the right workgroup, you can push the &#8220;Change&#8221; button and enter a new one.  And now, let&#8217;s roll up our hands and do some harder looking. [...]</description>
		<content:encoded><![CDATA[<p>[...] Sometimes your tcpip stack or winsock is royally hosed.  Yes, that&#8217;s a technical term.  You can find some helps on my recent tcpip and winsock troubleshooting post.  Give that a whirl.  Now, make sure your computers are in the same workgroup.  You can find this by going to &#8220;Start,&#8221; &#8220;Control Panel,&#8221; and &#8220;System.&#8221;  You will see a &#8220;computer name&#8221; tab &#8211; click it.  This will show your workgroup.  If it&#8217;s not in the right workgroup, you can push the &#8220;Change&#8221; button and enter a new one.  And now, let&#8217;s roll up our hands and do some harder looking. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cameron</title>
		<link>http://gopaultech.com/blog/2007/01/fixing-winsock-and-tcpip-meltdowns/comment-page-1/#comment-528</link>
		<dc:creator>Cameron</dc:creator>
		<pubDate>Fri, 19 Jan 2007 14:18:41 +0000</pubDate>
		<guid isPermaLink="false">http://gopaultech.com/blog/2007/01/19/fixing-winsock-and-tcpip-meltdowns/#comment-528</guid>
		<description>This site is chock full of handy tips. Good job!</description>
		<content:encoded><![CDATA[<p>This site is chock full of handy tips. Good job!</p>
]]></content:encoded>
	</item>
</channel>
</rss>
