<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.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>Account Lockouts..</title><link>http://blogs.msdn.com/spatdsg/archive/2005/12/23/507103.aspx</link><description>Account lockouts. I wont go into the pros and cons of setting this option So this is an entry based on a recent case I debugged but the problem wasn’t a bug. There was a case open with PSS from a large government contractor. The case had to do with a</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Optimum setting for account Lockout</title><link>http://blogs.msdn.com/spatdsg/archive/2005/12/23/507103.aspx#882516</link><pubDate>Fri, 27 Oct 2006 21:44:50 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:882516</guid><dc:creator>Chandan Patralekh</dc:creator><description>&lt;p&gt;Hi All,&lt;/p&gt;
&lt;p&gt;Please look into the given link which talks about:&lt;/p&gt;
&lt;p&gt;&amp;quot;Microsoft Windows 2000 Server and Windows Server 2003: Password and Account Lockout Features&amp;quot;.&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://support.microsoft.com/default.aspx?scid=%2Fservicedesks%2Fwebcasts%2Fen%2Fwc022703%2Fwct022703.asp"&gt;http://support.microsoft.com/default.aspx?scid=%2Fservicedesks%2Fwebcasts%2Fen%2Fwc022703%2Fwct022703.asp&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Enjoy!&lt;/p&gt;
&lt;p&gt;Chandan Patralekh&lt;/p&gt;
</description></item><item><title>Logging the source IP of simple LDAP binds</title><link>http://blogs.msdn.com/spatdsg/archive/2005/12/23/507103.aspx#8547357</link><pubDate>Sat, 24 May 2008 17:37:25 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8547357</guid><dc:creator>JefTek.com</dc:creator><description>&lt;p&gt;Simple bind events don't record the calling Computer as the source, but record the ADDS-DC or the ADLDS instance name, so you cannot determine where the simple bind request came from. So if you are trying to track down where the calling machine is that&lt;/p&gt;
</description></item></channel></rss>