<?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: Microsoft Office Communications Server Remote Connectivity Analyzer</title>
	<atom:link href="http://blog.insideocs.com/2009/08/25/microsoft-office-communications-server-remote-connectivity-analyzer/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.insideocs.com/2009/08/25/microsoft-office-communications-server-remote-connectivity-analyzer/</link>
	<description>Microsoft Office Communications Server - Tips, Tricks, and Insight</description>
	<lastBuildDate>Thu, 09 Sep 2010 22:10:09 -0400</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.3</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Curtis Johnstone</title>
		<link>http://blog.insideocs.com/2009/08/25/microsoft-office-communications-server-remote-connectivity-analyzer/comment-page-1/#comment-507</link>
		<dc:creator>Curtis Johnstone</dc:creator>
		<pubDate>Thu, 15 Oct 2009 14:49:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.insideocs.com/?p=501#comment-507</guid>
		<description>Agreed - some of these free tools can be frustrating when things don&#039;t work, and there is typically little documentation and good information to help.

I believe the tool is still officially in &#039;Beta&#039;, and I noticed a Feedback button right on the main page -  it might be worth submitting details of your issue. I like your idea of helpful pointers at each stage; let&#039;s take a shot at this one.

Each stage has expandable details.  What details are shown for the last stage (where, as you say, the actual remote user sign-in occurs)?

FYI - The tool has worked for me (all 4 stages) in two production environments.</description>
		<content:encoded><![CDATA[<p>Agreed &#8211; some of these free tools can be frustrating when things don&#8217;t work, and there is typically little documentation and good information to help.</p>
<p>I believe the tool is still officially in &#8216;Beta&#8217;, and I noticed a Feedback button right on the main page &#8211;  it might be worth submitting details of your issue. I like your idea of helpful pointers at each stage; let&#8217;s take a shot at this one.</p>
<p>Each stage has expandable details.  What details are shown for the last stage (where, as you say, the actual remote user sign-in occurs)?</p>
<p>FYI &#8211; The tool has worked for me (all 4 stages) in two production environments.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Henry</title>
		<link>http://blog.insideocs.com/2009/08/25/microsoft-office-communications-server-remote-connectivity-analyzer/comment-page-1/#comment-506</link>
		<dc:creator>John Henry</dc:creator>
		<pubDate>Thu, 15 Oct 2009 07:19:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.insideocs.com/?p=501#comment-506</guid>
		<description>Sure it&#039;s great if it all works - but how about some helpful pointers at each stage if it fails?

Ours fails at the last stage every time, the actual remote sign-in part, and I&#039;ve went through the list of checks the link provides but still no joy.

What would be great would be if someone stated real-life helpful reasons why a particular stage fails</description>
		<content:encoded><![CDATA[<p>Sure it&#8217;s great if it all works &#8211; but how about some helpful pointers at each stage if it fails?</p>
<p>Ours fails at the last stage every time, the actual remote sign-in part, and I&#8217;ve went through the list of checks the link provides but still no joy.</p>
<p>What would be great would be if someone stated real-life helpful reasons why a particular stage fails</p>
]]></content:encoded>
	</item>
</channel>
</rss>
