<?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>“Network Path Not Found” and “The Specified Network Name Is No Longer Available” errors when running Symantec antivirus products on Windows Server</title><link>http://blogs.technet.com/b/networking/archive/2010/03/19/network-path-not-found-and-the-specified-network-name-is-no-longer-available-errors-when-running-symantec-antivirus-products-on-windows-server.aspx</link><description>Hello, I am Robert Paige from the Windows Server Partner Ecosystem Team. In December, I posted an article on the Windows Server Division WebLog about networking issues that can result from running versions of Symantec Endpoint Protection prior to version</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator><item><title>re: “Network Path Not Found” and “The Specified Network Name Is No Longer Available” errors when running Symantec antivirus products on Windows Server</title><link>http://blogs.technet.com/b/networking/archive/2010/03/19/network-path-not-found-and-the-specified-network-name-is-no-longer-available-errors-when-running-symantec-antivirus-products-on-windows-server.aspx#3320296</link><pubDate>Sun, 21 Mar 2010 00:54:53 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3320296</guid><dc:creator>RJ</dc:creator><description>&lt;p&gt;Here's a link to where we found out about this bug:&lt;/p&gt;
&lt;p&gt;&lt;a rel="nofollow" target="_new" href="http://www.symantec.com/connect/forums/sep-11-and-net-framework-problems"&gt;http://www.symantec.com/connect/forums/sep-11-and-net-framework-problems&lt;/a&gt; &lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3320296" width="1" height="1"&gt;</description></item><item><title>re: “Network Path Not Found” and “The Specified Network Name Is No Longer Available” errors when running Symantec antivirus products on Windows Server</title><link>http://blogs.technet.com/b/networking/archive/2010/03/19/network-path-not-found-and-the-specified-network-name-is-no-longer-available-errors-when-running-symantec-antivirus-products-on-windows-server.aspx#3320295</link><pubDate>Sun, 21 Mar 2010 00:50:04 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3320295</guid><dc:creator>RJ</dc:creator><description>&lt;p&gt;There's another big gotcha. Symantec Endpoint Protection MR4 MP2, the recommended fix for this problem, was superseded by RU5 months ago. (Yes, they are no longer &amp;quot;Maintenance Releases&amp;quot; and &amp;quot;Maintenance Patches&amp;quot; but &amp;quot;Release Updates&amp;quot;. Sheesh.)&lt;/p&gt;
&lt;p&gt;RU5 does not play nicely with the .Net Framework if you have enabled Symantec's Application and Device Control feature, like we did. This feature lets us control USB usage as well as what applications a user can or cannot run. The symptoms are:&lt;/p&gt;
&lt;p&gt;1. iisreg.exe will fail to run unless you uninstall Symantec.&lt;/p&gt;
&lt;p&gt;2. The .Net Optimization service will fail to run after a patch to the .Net Framework is installed. That hangs the patch install process. Again, you need to uninstall Symantec.&lt;/p&gt;
&lt;p&gt;In both cases you can reinstall Symantec Endpoint Protection RU5 when you're done and all will be well until the next time. There is no patch yet. We rolled all of our servers back to MR4 MP2 because of this. Fortunately we had not rolled it out to any desktops yet.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;&lt;img src="http://blogs.technet.com/aggbug.aspx?PostID=3320295" width="1" height="1"&gt;</description></item></channel></rss>