<?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>Are your client machines getting errors such as “Network Path Not Found” or “The Specified Network Name Is No Longer Available” when connecting to a Windows 2008 Server share?</title><link>http://blogs.technet.com/b/essentialbusinessserver/archive/2010/09/24/are-your-client-machines-getting-errors-such-as-network-path-not-found-or-the-specified-network-name-is-no-longer-available-when-connecting-to-a-windows-2008-server-share.aspx</link><description>[Today’s post comes to us courtesy of Robert Paige from the Windows Server Partner Ecosystem Team] We wanted to resurface a continuing support issue with deployments that we first commented on back in December of 2009 , and again in a March post on the</description><dc:language>en-US</dc:language><generator>Telligent Evolution Platform Developer Build (Build: 5.6.50428.7875)</generator></channel></rss>