<?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>Dynamic Client Ports in Windows Server 2008 and Windows Vista (or: How I learned to stop worrying and love the IANA)</title><link>http://blogs.technet.com/askds/archive/2007/08/24/dynamic-client-ports-in-windows-server-2008-and-windows-vista-or-how-i-learned-to-stop-worrying-and-love-the-iana.aspx</link><description>Hi, Dave here. I’m a Support Escalation Engineer in Directory Services out of Charlotte, NC. Recently one of our consultants in the field deployed a Windows Server 2008 Beta 3 domain controller at a branch office to test management scenarios. After doing</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Dynamic Client Ports in Windows Server 2008 and Windows Vista (or: How I learned to stop worrying and love the IANA)</title><link>http://blogs.technet.com/askds/archive/2007/08/24/dynamic-client-ports-in-windows-server-2008-and-windows-vista-or-how-i-learned-to-stop-worrying-and-love-the-iana.aspx#1824932</link><pubDate>Sat, 25 Aug 2007 21:13:19 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:1824932</guid><dc:creator>lukasbeeler</dc:creator><description>&lt;p&gt;&amp;gt; Generally speaking, we don’t recommend that you restrict traffic between servers on your internal network.&lt;/p&gt;
&lt;p&gt;I've been telling this to customers too. Do you know of an official statement from Microsoft which states this? It's always nice to have a proper link for such topics.&lt;/p&gt;
</description></item><item><title>re: Dynamic Client Ports in Windows Server 2008 and Windows Vista (or: How I learned to stop worrying and love the IANA)</title><link>http://blogs.technet.com/askds/archive/2007/08/24/dynamic-client-ports-in-windows-server-2008-and-windows-vista-or-how-i-learned-to-stop-worrying-and-love-the-iana.aspx#1840035</link><pubDate>Mon, 27 Aug 2007 19:38:57 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:1840035</guid><dc:creator>NedPyle</dc:creator><description>&lt;p&gt;Hi lukasbeeler,&lt;/p&gt;
&lt;p&gt;Yes and no. We have some KB documentation that has been making this 'don't restrict' guidance:&lt;/p&gt;
&lt;p&gt;179442	How to configure a firewall for domains and trusts&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://support.microsoft.com/default.aspx?scid=kb;EN-US;179442"&gt;http://support.microsoft.com/default.aspx?scid=kb;EN-US;179442&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;832017	Service overview and network port requirements for the Windows Server system&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://support.microsoft.com/default.aspx?scid=kb;EN-US;832017"&gt;http://support.microsoft.com/default.aspx?scid=kb;EN-US;832017&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;However, they have not yet been updated to reflect these new port assignments. Since their guidance was to not block anything, they are ok for now though. This should all be up to date before Windows Server 2008 comes out.&lt;/p&gt;
&lt;p&gt;-Ned&lt;/p&gt;
</description></item><item><title>The case of the blocked FRS replication</title><link>http://blogs.technet.com/askds/archive/2007/08/24/dynamic-client-ports-in-windows-server-2008-and-windows-vista-or-how-i-learned-to-stop-worrying-and-love-the-iana.aspx#3123868</link><pubDate>Mon, 15 Sep 2008 01:03:45 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3123868</guid><dc:creator>'Cos the world needs one more...</dc:creator><description>&lt;p&gt;So I haven't written anything in quite a while and felt compelled to write something I recently ran into.&lt;/p&gt;
</description></item></channel></rss>