Hi, According to your description, I suggest to perform these tests to troubleshoot the issue: 1 Logon with Clean Boot 2 Temporary disable firewall and antivirus program Furthermore, I suggest to contact Samba to see if they have any solution for this kind of issue: http://www.samba.org/samba/support/ Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information. Thank you for your understanding. Regards, Leo Huang TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Samba version 3.0.33-3.29.el5_7.4 Our windows 7 clients occasionally, somewhat randomly, start giving the System error 64 - the specified network name is no longer available when connecting to a UNC path to our SAMBA share. They work fine up to this happening. Using a different DNS name makes it prompt for the login, and then works. Logging out and back in or rebooting also fixes it until it happens again randomly. It may be related to using Office products like Word on files stored on the UNC path, or to opening and closing many files in a short period of time when synchronizing such as with Allwaysync. Any ideas?

Hi, According to your description, I suggest to perform these tests to troubleshoot the issue: 1 Logon with Clean Boot 2 Temporary disable firewall and antivirus program Furthermore, I suggest to contact Samba to see if they have any solution for this kind of issue: http://www.samba.org/samba/support/ Please Note: Since the website is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information. Thank you for your understanding. Regards, Leo Huang TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, Did your issue solved? Please feel free to give me any update. Thanks. Regards, Leo Huang TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.comPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Hi, I began to have the same problem about the same time as the original poster. Starting early November (2011) we have two windows servers (one 2008, one 2003) that suddenly stopped communicating with our NAS backup device. The device is a Drobo and is running Samba shares. I have tried disabling (uninstalling) the server's AV, tried hard-coding speed/duplex, rebooted the servers, disabled SMB2 in registry, enabled the max throughput in registry, checked for newer NIC drivers, altered many various setting within the NICs and have googled the heck out of this...all to no avail. This doesn't seem like a Samba/Drobo problem as any other PC or server on the network is still able to access the shares without issue. The error message first started out as "The specified network name is no longer available", then after a week or so it changed to "An unexpected network error occurred"...then after I rebooted the servers last night it is now back to the original "The specified network name is no longer available" message. I can pretty well pinpoint the day this failed as being the Patch Tuesday of this past November, as my last successful backup of these servers was Monday November the 7th, 2011. I hope this added information can help to find resolution to this issue...I have to get these backups working again! Thanks, 32bit

Hi, As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as ‘Answered’ as the previous steps should be helpful for many similar scenarios. If the issue still persists, please feel free to reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish. BTW, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks for your understanding and efforts. Regards, Leo Huang TechNet Subscriber Support in forum. If you have any feedback on our support, please contact tngfb@microsoft.com Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.