<?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>Name Hijacked, Bystander DC Hangs</title><link>http://blogs.technet.com/ad/archive/2008/11/24/name-hijacked-bystander-dc-hangs.aspx</link><description>I learn more about AD and other things every day, which is part of the fun of this job we do-learning about how things work. This story does a good job of lending some understanding to something that can be tough to understand-trust secure channels. This</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Name Hijacked, Bystander DC Hangs</title><link>http://blogs.technet.com/ad/archive/2008/11/24/name-hijacked-bystander-dc-hangs.aspx#3159600</link><pubDate>Wed, 26 Nov 2008 05:13:00 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3159600</guid><dc:creator>Scharique</dc:creator><description>&lt;p&gt;Wow !! so much for a good uniform naming convention across the board&lt;/p&gt;
</description></item></channel></rss>