remote access to network shares lost

[awelch]

We have two new Windows 2008 servers that have SAN drives attached for file sharing. Many users map remotely to the two shares. The servers and shares have been up and tested successfully for the past month. Yesterday I began receiving reports that one of the two server shares was inaccessible by users. I tried an also couldn't connect remotely via a mapped drive. I RDPd into the server and all seemed well with the server and the SAN including the network share folder. Didn't see any problem at all in fact, but rebooted the server and that resolved the problem. This morning the same exact thing occured on the other server's share and it also seemed fine upon logging into the server. Rebooting again solved the problem. I don't see any errors in logs on either server that would account for this. Does anybody have ideas or experience with this type of thing at all? We're new to Windows 2008 server and I'm new to the forum. Thank you.

 

Andrea

[awelch]

No resolution yet, but do have an update on this issue that has continued to be a problem for us. It has continued and we've also noted that the network shares are very slow prior to them becoming unavailable. We opened a case with Microsoft and they are pointing to Symantec as the culprit. We are awaiting further recommendations from MS, but initially they're suggesting updating our NIC drivers on the servers in question. Here is a link they sent which describes similar problem:

http://blogs.technet.com/networking/archive/2008/07/10/intermittent-file-sharing-connectivity-from-various-clients-to-a-windows-server-2008-server.aspx

[awelch]

The problem has continued over the weekend and we have consulted Microsoft tech support. They sent me this link Microsoft Enterprise Networking Team : Intermittent file sharing connectivity from various clients to a Windows Server 2008 server relative to similar reported problems and recommended we upgrade our NIC drivers to the latest version. They are also thinking that Symantec is the root of our problem, but no recommendations on that yet. Since upgrading the drivers we've had about 20 hours with no lost mapped drives.