Recently ran into this problem right after updating from 5.something to 6.2.2. My shares are no longer accessible using either windows 10 pro, or Ubuntu 16.04. I'm able to access the the web console, and I'm also able to ssh into the machine without any issue, but my samba shares aren't accessible. When I try to access it using windows explorer with \\SERVERNAME, I get prompted with 3 separate login popups, and after entering my unraid credentials (for a new user I created), it simply says Windows cannot access \\SERVERNAME, with an unspecified error. In a similar case, when I try to connect to smb://SERVERNAME on Ubuntu, nothing shows up. The machine doesn't want to show up on any of my computers, despite the fact that I see it as an active device in my router's settings, and can access it through its dns servername.

 

All my shares are set to public, export "yes", and Local Master is also set to "yes" in my SMB settings.

 

I tried using a couple of different windows 10 machines all on the same default WORKGROUP, but nothing seems to be working, so I'm stumped.

 

Any help or advice would be very much appreciated!! Thx

I would suggest you start by going to the Credential Manager and deleting all of the credentials. 

 

Having suggested that, a while back, there have been a lot of folks with problems like yours.  You should try search the portion of the board and see if any of the solutions that they found will work for you. 

 

You can also try shutting down all of the windows machines and that Ubuntu machine on your network and wait about thirty minutes and fire them back up.  (The Windows Local Master election process is somewhat of a 'black art' as SMB is, at best, a kludge, that usually works but when it doesn't it is a bear to troubleshoot!)

Hmm... I already wen't through a bunch of topics on the forum looking for fixes, including clearing out credentials but I haven't tried giving the server time for local master election! I'll give it a try! If this works I'll just come to the conclusion that windows is haunted.

I forget one thing.  There is a tool which might help you--  The Dynamix Local Master plugin.  You can find it in the first post of this thread:

 

    http://lime-technology.com/forum/index.php?topic=36543.0

 

It will tell you which computer in the workgroup is the local master. 

I have the exact same issue.  My server was working fine on 6.1.9, then it started acting up the past week where it would just go inaccessible at some point (http, SSH, SMB share or NFS share access), and I would have to do a hard reboot since it runs headless.

I thought this was a good time to upgrade so went to 6.2.1 and then I lost access via SMB.  I can access using http, SSH, or NFS but not SMB. 

Upgraded to 6.2.2 and same thing.  I have tried from Windows 7, Windows 8.1, Windows 10, and from Android.  It doesn't accept any of my user credentials (have changed the password to several different accounts).   

FTP access works as well so I do know everything appears to be running.

Have tried samba start through SSH with no luck.

Not really sure what I should do at this point.

I have the exact same issue.  My server was working fine on 6.1.9, then it started acting up the past week where it would just go inaccessible at some point (http, SSH, SMB share or NFS share access), and I would have to do a hard reboot since it runs headless.

I thought this was a good time to upgrade so went to 6.2.1 and then I lost access via SMB.  I can access using http, SSH, or NFS but not SMB. 

Upgraded to 6.2.2 and same thing.  I have tried from Windows 7, Windows 8.1, Windows 10, and from Android.  It doesn't accept any of my user credentials (have changed the password to several different accounts).   

FTP access works as well so I do know everything appears to be running.

Have tried samba start through SSH with no luck.

Not really sure what I should do at this point.

 

You should be able to get a clean shutdown with a QUICK push of the power button. 

 

As I read your post, you have http access at this point.  You need to attach your diagnostic file for the real Gurus to look at your server. 

 

Next thing.  Changing the credentials in Windows is usually a losing battle because (apparently) Windows never forgets the old ones and then uses them first!  The only way to get rid of old credentials is to delete all of them from the credential manager and start over. 

 

I will point out that you might get a more responses if you post your issues to a new thread.