<?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: My PuTTY SSH Tunnel Guide</title>
	<atom:link href="http://blog.zztopping.com/2009/04/17/my-putty-ssh-tunnel-guide/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.zztopping.com/2009/04/17/my-putty-ssh-tunnel-guide/</link>
	<description>A Blog by a Non-Blogger</description>
	<lastBuildDate>Wed, 13 Jul 2011 12:18:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: c</title>
		<link>http://blog.zztopping.com/2009/04/17/my-putty-ssh-tunnel-guide/comment-page-1/#comment-8811</link>
		<dc:creator>c</dc:creator>
		<pubDate>Sun, 18 Jul 2010 07:10:50 +0000</pubDate>
		<guid isPermaLink="false">http://blog.zztopping.com/?p=59#comment-8811</guid>
		<description>nice post i am using freenas a the sshserver and the port fording is even easer on the router put the ssh port on andport ford on the client i used my cellphone to tesy it out</description>
		<content:encoded><![CDATA[<p>nice post i am using freenas a the sshserver and the port fording is even easer on the router put the ssh port on andport ford on the client i used my cellphone to tesy it out</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hkppl</title>
		<link>http://blog.zztopping.com/2009/04/17/my-putty-ssh-tunnel-guide/comment-page-1/#comment-8155</link>
		<dc:creator>hkppl</dc:creator>
		<pubDate>Tue, 25 May 2010 10:04:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.zztopping.com/?p=59#comment-8155</guid>
		<description>Okay...thanks to theultramage&#039;s insight and a bit of experimentation, I may have stumbled upon a workaround: Try this (but create a system restore point, do a backup, and cross your fingers first!):

1) Go to &quot;Device Manager&quot; select View and enable &quot;show hidden devices.&quot;
2) Expand &quot;Non-Plug and Play Drivers&quot; and set &quot;Message-oriented TCP/IP and TCP/IPv6 Protocol (SMB session)&quot; to start on demand.
3) Reboot
4) Bind port 445 with your application.  I used Putty and bound my local loopback addresses on ports 139 and 445 to the tunneled IP addresses&#039; ports 139 and 445 on the remote network.
5) Start the &quot;Message-oriented TCP/IP and TCP/IPv6 Protocol (SMB session)&quot; driver.
6) Browse the remote shares like you used to do before KB942624.
6) Celebrate! We just found a way around the Port forwarding 445 for SMB and SSH problem!


I tried this on two different Vista machines: One with the KB942624 patch applied and the other with SP1 integrated in.  It worked on both.  No blue screens or any other quirks that I could see.

Only problem is that you must bind the port before starting SMB.sys each time you start Windows.  You can&#039;t stop the device once it&#039;s started (or at least I couldn&#039;t).

Again, I didn&#039;t come up with this approach on my own.  Theultramage&#039;s post pointed me in the right direction.</description>
		<content:encoded><![CDATA[<p>Okay&#8230;thanks to theultramage&#8217;s insight and a bit of experimentation, I may have stumbled upon a workaround: Try this (but create a system restore point, do a backup, and cross your fingers first!):</p>
<p>1) Go to &#8220;Device Manager&#8221; select View and enable &#8220;show hidden devices.&#8221;<br />
2) Expand &#8220;Non-Plug and Play Drivers&#8221; and set &#8220;Message-oriented TCP/IP and TCP/IPv6 Protocol (SMB session)&#8221; to start on demand.<br />
3) Reboot<br />
4) Bind port 445 with your application.  I used Putty and bound my local loopback addresses on ports 139 and 445 to the tunneled IP addresses&#8217; ports 139 and 445 on the remote network.<br />
5) Start the &#8220;Message-oriented TCP/IP and TCP/IPv6 Protocol (SMB session)&#8221; driver.<br />
6) Browse the remote shares like you used to do before KB942624.<br />
6) Celebrate! We just found a way around the Port forwarding 445 for SMB and SSH problem!</p>
<p>I tried this on two different Vista machines: One with the KB942624 patch applied and the other with SP1 integrated in.  It worked on both.  No blue screens or any other quirks that I could see.</p>
<p>Only problem is that you must bind the port before starting SMB.sys each time you start Windows.  You can&#8217;t stop the device once it&#8217;s started (or at least I couldn&#8217;t).</p>
<p>Again, I didn&#8217;t come up with this approach on my own.  Theultramage&#8217;s post pointed me in the right direction.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: hkppl</title>
		<link>http://blog.zztopping.com/2009/04/17/my-putty-ssh-tunnel-guide/comment-page-1/#comment-8154</link>
		<dc:creator>hkppl</dc:creator>
		<pubDate>Tue, 25 May 2010 10:04:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.zztopping.com/?p=59#comment-8154</guid>
		<description>Hi, I found your page when i searched the information of SSH tunnel. The following mentioned how to set ssh tunnel for SMB (i.e. shared folder in Windows) . 
Hope it&#039;s useful for u.
http://social.technet.microsoft.com/forums/en-US/itprovistanetworking/thread/d30d3c98-58c5-47f6-b5a5-f5620882020d/</description>
		<content:encoded><![CDATA[<p>Hi, I found your page when i searched the information of SSH tunnel. The following mentioned how to set ssh tunnel for SMB (i.e. shared folder in Windows) .<br />
Hope it&#8217;s useful for u.<br />
<a href="http://social.technet.microsoft.com/forums/en-US/itprovistanetworking/thread/d30d3c98-58c5-47f6-b5a5-f5620882020d/" rel="nofollow">http://social.technet.microsoft.com/forums/en-US/itprovistanetworking/thread/d30d3c98-58c5-47f6-b5a5-f5620882020d/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

