<?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: FTP SSL/TLS Negotiation Failed</title>
	<atom:link href="http://blog.tech4him.com/2009/09/ftp-ssltls-negotiation-failed/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.tech4him.com/2009/09/ftp-ssltls-negotiation-failed/</link>
	<description>A Christian technology chaos wrangler and his thoughts</description>
	<lastBuildDate>Wed, 08 Sep 2010 22:38:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tom</title>
		<link>http://blog.tech4him.com/2009/09/ftp-ssltls-negotiation-failed/comment-page-1/#comment-120</link>
		<dc:creator>Tom</dc:creator>
		<pubDate>Fri, 08 Jan 2010 23:06:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.tech4him.com/?p=745#comment-120</guid>
		<description>As a follow-up to this post. I received zero replies in the Gene6FTP Server forums. However, I did some detective work and found that FileZilla is defaulting to a connection timeout of 20 seconds. For a reason I don&#039;t know, the MLSD response was taking 22-25 seconds at times. 

Workaround - Changed the FileZilla connection timeout setting to 60 seconds and the problem has been worked around. Sniffing packets did not yield and further negotiation going on between client and server during these 22-25 seconds. Thinking something on the server side, but no clue as to what it is at this point.

Anyhow, just wanted to update anyone who needs it with a possible work around.

Blessings,

Tom</description>
		<content:encoded><![CDATA[<p>As a follow-up to this post. I received zero replies in the Gene6FTP Server forums. However, I did some detective work and found that FileZilla is defaulting to a connection timeout of 20 seconds. For a reason I don&#8217;t know, the MLSD response was taking 22-25 seconds at times. </p>
<p>Workaround &#8211; Changed the FileZilla connection timeout setting to 60 seconds and the problem has been worked around. Sniffing packets did not yield and further negotiation going on between client and server during these 22-25 seconds. Thinking something on the server side, but no clue as to what it is at this point.</p>
<p>Anyhow, just wanted to update anyone who needs it with a possible work around.</p>
<p>Blessings,</p>
<p>Tom</p>
]]></content:encoded>
	</item>
</channel>
</rss>
