<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Publishing FTP with UAG</title><link>http://blogs.technet.com/b/ben/archive/2011/12/29/publishing-ftp-with-uag.aspx</link><description>Those with a sharp eyesight may have noticed that the FTP template that was available with IAG is not available in UAG. Publishing FTP is not in high demand, but if you need to do it, it is possible using simple tunneling. Here are the steps: 1. Create</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: Publishing FTP with UAG</title><link>http://blogs.technet.com/b/ben/archive/2011/12/29/publishing-ftp-with-uag.aspx#3560126</link><pubDate>Thu, 21 Mar 2013 10:49:33 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3560126</guid><dc:creator>Peti</dc:creator><description>&lt;p&gt;Port range end value need to be changed to 65534.&lt;/p&gt;
&lt;p&gt;(So the port range should be 20,21,1024-65534 in order to prevent rapid memory consumption by the IIS Worker process and prevent the server to become unresponsive)&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3560126" width="1" height="1"&gt;</description></item><item><title>re: Publishing FTP with UAG</title><link>http://blogs.technet.com/b/ben/archive/2011/12/29/publishing-ftp-with-uag.aspx#3560124</link><pubDate>Thu, 21 Mar 2013 10:37:56 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3560124</guid><dc:creator>Peti</dc:creator><description>&lt;p&gt;If any SSLVPN application (this is not restricted to an application publishing FTP) is published using port 65535, UAG will enter an infinite loop whenever the application is launched from the UAG portal page.&lt;/p&gt;
&lt;p&gt;At the w3wp.exe process on the UAG server will start rapidly consuming memory which will eventually cause the server to stop responding.&lt;/p&gt;
&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3560124" width="1" height="1"&gt;</description></item></channel></rss>