<?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>Kerberos Authentication problems – Service Principal Name (SPN) issues - Part 3</title><link>http://blogs.technet.com/askds/archive/2008/06/11/kerberos-authentication-problems-service-principal-name-spn-issues-part-3.aspx</link><description>Now we have seen what it looks like when there is no Service Principal Name defined , and when the Service Principal Name is not unique in the forest. We will now cover what things look like when the Service Principal Name is NOT added to the correct</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Interesting Links – 6/15/2008</title><link>http://blogs.technet.com/askds/archive/2008/06/11/kerberos-authentication-problems-service-principal-name-spn-issues-part-3.aspx#3069619</link><pubDate>Wed, 11 Jun 2008 22:44:16 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3069619</guid><dc:creator>Matt Johnson's Technical Adventures</dc:creator><description>&lt;p&gt;This week’s interesting collection of links! Kerberos Authentication problems – Service Principal Name&lt;/p&gt;
</description></item></channel></rss>