<?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>R2 Capacity Planning tool run through and XML file problem</title><link>http://blogs.technet.com/toml/archive/2009/05/19/r2-capacity-planning-tool-run-through-and-xml-file-problem.aspx</link><description>I have had the distinct pleasure or misfortune to have used the LCS 2005 SP1 capacity planning tools and the unreleased OCS 2007 capacity planning tools with customers. As I loaded the tool, I forgot about some of the feedback that I provided on the toolset</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: R2 Capacity Planning tool run through and XML file problem</title><link>http://blogs.technet.com/toml/archive/2009/05/19/r2-capacity-planning-tool-run-through-and-xml-file-problem.aspx#3249446</link><pubDate>Tue, 02 Jun 2009 21:27:43 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3249446</guid><dc:creator>Arnab</dc:creator><description>&lt;p&gt;Hi Tom,&lt;/p&gt;
&lt;p&gt;I ran into similar problems when using the OCS Stress Tool.The user wont log on and the packet captures revealed incomplete tls handshake.After client and server hello there are no change cipher specs messages exchaged and i see no kerberos authentication happening.&lt;/p&gt;
&lt;p&gt;I re ran the test with the password xlm change you suggested...but the results are the same as before.&lt;/p&gt;
&lt;p&gt;Thanks,&lt;/p&gt;
&lt;p&gt;Arnab&lt;/p&gt;</description></item><item><title>re: R2 Capacity Planning tool run through and XML file problem</title><link>http://blogs.technet.com/toml/archive/2009/05/19/r2-capacity-planning-tool-run-through-and-xml-file-problem.aspx#3249448</link><pubDate>Tue, 02 Jun 2009 21:33:18 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3249448</guid><dc:creator>toml-lcskid</dc:creator><description>&lt;p&gt;Getting server logs would help but my first thought would be that the client workstation running the stress is not joined to the domain. If you changed the authentication to NTLM only does it work (restart services)&lt;/p&gt;
</description></item></channel></rss>