<?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>Troubleshooting Kerberos Authentication problems – Name resolution issues</title><link>http://blogs.technet.com/askds/archive/2008/05/14/troubleshooting-kerberos-authentication-problems-name-resolution-issues.aspx</link><description>Hi Rob here. I thought I would show you how we in Microsoft Commercial Technical Support typically troubleshoot Kerberos authentication issues. This discussion should do much to get you more comfortable viewing network traces for Kerberos authentication</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Logging the source IP of simple LDAP binds</title><link>http://blogs.technet.com/askds/archive/2008/05/14/troubleshooting-kerberos-authentication-problems-name-resolution-issues.aspx#3059599</link><pubDate>Fri, 23 May 2008 06:02:42 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3059599</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><item><title>Kerberos Authentication problems – Service Principal Name (SPN) issues - Part 1</title><link>http://blogs.technet.com/askds/archive/2008/05/14/troubleshooting-kerberos-authentication-problems-name-resolution-issues.aspx#3062846</link><pubDate>Thu, 29 May 2008 20:50:23 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3062846</guid><dc:creator>Ask the Directory Services Team</dc:creator><description>&lt;p&gt;Hi Rob here again. I hope that you found the first blog on troubleshooting Kerberos Authentication problems&lt;/p&gt;
</description></item><item><title>Ask the Directory Services Team : Troubleshooting Kerberos Authentication problems – Name resolution issues</title><link>http://blogs.technet.com/askds/archive/2008/05/14/troubleshooting-kerberos-authentication-problems-name-resolution-issues.aspx#3113883</link><pubDate>Fri, 29 Aug 2008 15:55:07 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3113883</guid><dc:creator>SharePoint Thinks, Links and Clinks</dc:creator><description>&lt;p&gt;&amp;amp;#160; Ask the Directory Services Team : Troubleshooting Kerberos Authentication problems – Name resolution&lt;/p&gt;
</description></item><item><title>Domain Infrastructure Research</title><link>http://blogs.technet.com/askds/archive/2008/05/14/troubleshooting-kerberos-authentication-problems-name-resolution-issues.aspx#3193658</link><pubDate>Wed, 28 Jan 2009 18:25:49 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3193658</guid><dc:creator>Confluence: Campus Active Directory</dc:creator><description>&lt;p&gt;Microsoft Support Documents 2008 &amp;quot;Lag site&amp;quot; or &amp;quot;hot site&amp;quot; (aka delayed replication) for Active Directory Disaster Recovery support&lt;/p&gt;
</description></item></channel></rss>