<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://msmvps.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>The other steveb - Steve Banks' Blog on SBS, EBS, and other Small Business Technology Topics : .NET</title><link>http://msmvps.com/blogs/steveb/archive/tags/.NET/default.aspx</link><description>Tags: .NET</description><dc:language>en</dc:language><generator>CommunityServer 2008.5 SP2 (Build: 40407.4157)</generator><item><title>Do not install IPv6 on your SBS 2003 box</title><link>http://msmvps.com/blogs/steveb/archive/2009/02/21/net-framework-3-5-service-pack-1.aspx</link><pubDate>Sat, 21 Feb 2009 14:24:00 GMT</pubDate><guid isPermaLink="false">d67277c4-116b-43f1-b688-e9ef184ea916:1673088</guid><dc:creator>steveb</dc:creator><slash:comments>0</slash:comments><wfw:commentRss xmlns:wfw="http://wellformedweb.org/CommentAPI/">http://msmvps.com/blogs/steveb/rsscomments.aspx?PostID=1673088</wfw:commentRss><comments>http://msmvps.com/blogs/steveb/archive/2009/02/21/net-framework-3-5-service-pack-1.aspx#comments</comments><description>&lt;p&gt;I owe the .NET team an apology for blaming them as the original cause of the problems described in this post.&amp;nbsp; The pro and con of blog posting is that we can fire off a post and later find out there was a different cause for the effect we were hit with.&amp;nbsp; So sorry guys and gals for coming down on you so hard.&amp;nbsp; Figured with the SBS 2008 issues we&amp;#39;ve been seeing after 3.5 SP1 that they were spilling over to SBS 2003 as well. - Steve&lt;/p&gt;
&lt;p&gt;This post was originally called  - .NET Framework 3.5 Service Pack 1 when I wrote it last Saturday, the 21st of February.&amp;nbsp; While I still recommend running the .NET family updates mentioned below, the reason the SBS box went into a tail spin turned out to be installation of &lt;a target="_blank" href="http://www.ietf.org/rfc/rfc2460.txt" title="Internet Protocol Version 6 Ipv6 Specification"&gt;IPv6&lt;/a&gt; we did while testing an app on the box that happened to coincide within the same week the .NET SP had been applied.&amp;nbsp; Confirmed this today.&amp;nbsp; With the application vendor on the phone, I re-ran their installer and configuration tool and the server decided it was time to restart:&lt;/p&gt;
&lt;p style="margin:0in 0in 0pt;" class="MsoPlainText"&gt;&lt;span style="font-size:x-small;font-family:Arial;"&gt;---------------------------&lt;/span&gt;&lt;/p&gt;
&lt;p style="margin:0in 0in 0pt;" class="MsoPlainText"&gt;&lt;span style="font-size:x-small;font-family:Arial;"&gt;System Shutdown&lt;/span&gt;&lt;/p&gt;
&lt;p style="margin:0in 0in 0pt;" class="MsoPlainText"&gt;&lt;span style="font-size:x-small;font-family:Arial;"&gt;---------------------------&lt;/span&gt;&lt;/p&gt;
&lt;p style="margin:0in 0in 0pt;" class="MsoPlainText"&gt;&lt;span style="font-size:x-small;font-family:Arial;"&gt;The system is shutting down.&lt;span style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/span&gt;Please save all work in progress and log off.&lt;span style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/span&gt;Any unsaved changes will be lost.&lt;span style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/span&gt;This shutdown was initiated by NT AUTHORITY\SYSTEM.&lt;span style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/span&gt;Shutdown will begin in 44 seconds.&lt;span style="mso-spacerun:yes;"&gt;&amp;nbsp; &lt;/span&gt;Shutdown message: Windows must now restart because the Remote Procedure Call (RPC) service terminated unexpectedly.&lt;/span&gt;&lt;/p&gt;
&lt;p style="margin:0in 0in 0pt;" class="MsoPlainText"&gt;&lt;span style="font-size:x-small;font-family:Arial;"&gt;---------------------------&lt;/span&gt;&lt;/p&gt;
&lt;p style="margin:0in 0in 0pt;" class="MsoPlainText"&gt;&lt;span style="font-size:x-small;"&gt;&lt;span style="font-family:Arial;"&gt;OK&lt;span style="mso-spacerun:yes;"&gt;&amp;nbsp;&amp;nbsp; &lt;/span&gt;&lt;/span&gt;&lt;/span&gt;&lt;/p&gt;
&lt;p style="margin:0in 0in 0pt;" class="MsoPlainText"&gt;&lt;span style="font-size:x-small;font-family:Arial;"&gt;---------------------------&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;This looked extremely familiar to last week&amp;#39;s issue, so now we had a culprit.&amp;nbsp; What we looked at next was that the application (we&amp;#39;re in pre-beta testing so can&amp;#39;t give out the name at the moment) was using &lt;a target="_blank" href="http://www.microsoft.com/technet/network/ipv6/teredo.mspx" title="Microsoft Teredo Overview"&gt;Teredo&lt;/a&gt; to tunnel out over IPv6 and would install IPv6 if it didn&amp;#39;t see it installed.&amp;nbsp; By going into &lt;a target="_blank" href="http://support.microsoft.com/kb/242468" title="KB 242468 - How to Use the Netsh.exe Tool and Command-Line Switches"&gt;netsh&lt;/a&gt; we were able to remove the protocol.&amp;nbsp; I&amp;#39;m including the command to remove IPv6 from your SBS 2003 if you by chance decide to install it on your box too and need to get it off of there.&amp;nbsp; It broke RPC over HTTP, POP3, and IMAP4 Exchange Protocols in addition to the box &amp;quot;forgetting&amp;quot; it was an SBS box as shown below in the original post.&amp;nbsp; Here&amp;#39;s what you need to type to remove it (do not remove from SBS 2008 boxes, you need it on there).&lt;/p&gt;
&lt;p&gt;
&lt;p&gt;type: netsh &amp;lt;ENTER&amp;gt;&lt;/p&gt;
&lt;p&gt;at the prompt type: interface ipv6 uninstall &amp;lt;ENTER&amp;gt;&lt;/p&gt;
&lt;p&gt;You will be prompted to restart the server after it completes.&lt;/p&gt;
&lt;p&gt;So, again, sorry to the .NET team for the error in placing blame.&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;p&gt;&lt;img width="168" src="http://msmvps.com/cfs-file.ashx/__key/CommunityServer.Blogs.Components.WeblogFiles/steveb/Microsoft_5F00_Visual_5F00_Studio.gif" alt="Microsoft Visual Studio" height="97" /&gt;For those of us in the SBS world, we have a love/hate, with mostly hate, relationship with .NET Framework updates.&amp;nbsp; Seems they are always causing trouble with our boxes.&amp;nbsp; Turns out the recent &lt;a target="_blank" href="http://www.microsoft.com/downloads/details.aspx?familyid=ab99342f-5d1a-413d-8319-81da479ab0d7&amp;amp;displaylang=en" title="MSFT Download Location for SP1"&gt;.NET Framework 3.5 Service Pack 1&lt;/a&gt; is no exception, both on &lt;a target="_blank" href="http://www.microsoft.com/sbs/en/us/default.aspx" title="SBS 2008"&gt;Small Business Server 2008&lt;/a&gt; and &lt;a target="_blank" href="http://www.microsoft.com/windowsserver2003/sbs/default.mspx" title="SBS 2003"&gt;Small Business Server 2003&lt;/a&gt;.&amp;nbsp; While it is &lt;a target="_blank" href="http://support.microsoft.com/kb/951847" title="KB 951847 - List of changes and fixed issues in the .NET Framework 3.5 Service Pack 1"&gt;supposed to fix 25+ issues in .NET&lt;/a&gt;, my personal SBS 2003 production box reacted so badly with it that the box had no idea it was running SBS anymore.&amp;nbsp; When I attempted to run the CEICW in an effort to bring back my RPC over HTTP / Outlook Anywhere functionality that had died after running with the update for a few days, here&amp;#39;s the error it came back with:&lt;/p&gt;
&lt;p&gt;&amp;nbsp;&lt;img width="516" src="http://msmvps.com/cfs-file.ashx/__key/CommunityServer.Blogs.Components.WeblogFiles/steveb/Dot_2D00_NET_5F00_stole_5F00_my_5F00_SBS_5F00_Server.jpg" alt=".NET stole my SBS!" height="188" /&gt;&lt;/p&gt;
&lt;p&gt;I was also having &amp;quot;issues&amp;quot; with POP3 and IMAP4 (we use SSL on each of these for specific tasks at our office) protocols stopping after either an iisreset or a full restart of the server.&amp;nbsp; Strange thing with those protocols was that their respective services were still running.&amp;nbsp; Figure that one out.&lt;/p&gt;
&lt;p&gt;I restored the system drive from a StorageCraft ShadowProtect image last night to get the machine back on its feet.&amp;nbsp; I personally have left 3.5 SP1 on our box and added the &lt;a href="http://support.microsoft.com/kb/959209" title="MSFT KB 959209 .NET 3.5 SP1 &amp;quot;Update&amp;quot;"&gt;update patches&lt;/a&gt; that are supposed to resolve the problems the Service Pack is causing with our boxes; using our company&amp;#39;s server as a guinea pig before putting&amp;nbsp;the service pack or subsequent update suite of three patches&amp;nbsp;into production&amp;nbsp;at client sites.&amp;nbsp; Personally, I will not install .NET Framework 3.5 Service Pack 1 without these fixes on any box I touch now.&amp;nbsp; I&amp;#39;d recommend you do the same for any machines you admin and ensure you have a very good back up before playing with these or any updates.&amp;nbsp; ;-)&lt;/p&gt;
&lt;p&gt;Steve&lt;/p&gt;
&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://msmvps.com/aggbug.aspx?PostID=1673088" width="1" height="1"&gt;</description><category domain="http://msmvps.com/blogs/steveb/archive/tags/SBS+2003/default.aspx">SBS 2003</category><category domain="http://msmvps.com/blogs/steveb/archive/tags/SBS+2008/default.aspx">SBS 2008</category><category domain="http://msmvps.com/blogs/steveb/archive/tags/IPv6/default.aspx">IPv6</category><category domain="http://msmvps.com/blogs/steveb/archive/tags/.NET/default.aspx">.NET</category><category domain="http://msmvps.com/blogs/steveb/archive/tags/Teredo/default.aspx">Teredo</category></item></channel></rss>