I had upgraded the security giving one user R/W access to some necessary shares and locking the other shares to read only. 

 

The security for these shares was changed from public to private and after fighting with Win10 for several hours, both laptops were able to access the files after saving the login information.  However today three days later, 2 of these shares suddenly became inaccessable, while the other 4 continue to work as expected.  The first one is still visible and all files are viewable, but accessing the jpg files results in a ("you do not have permission to access this file") error.  Other text files are accessible without issue.  Rebooting the workstations and the server did not change this.  Setting the SMB share security back to public also did not change this error. 

 

The second share with problems is totally inaccessible.  No files are viewable. Even after I change the access for the share back to public, there is no possibility of accessing this share from either laptop.  The error "you might not have permission to use this network resource.  The handle is invalid"

 

Running 6.1.9 on this server....

 

 

In my experience, this kind of shenanigans is caused by windows credential handling.

 

Try purging the cached login data, making sure that first contact with the server is made with the user you want to use, not an anonymous login. The net use command line is a good way to force the correct login.

Yes, I would agree, as I have seen this too, but the same one login credentials are used for all the shares.  4 shares are working as expected, and 2 are not.  Doesn't that mean that the correct credentials are being used?  The credentials manager in control panel shows the correct ones being used, and there are no other credentials on the laptop.

 

Testing further with net use.....

During testing using MC I renamed the inaccessible share and it instantly needed a login, when trying to access it.  It should have been public.  Just to check, I stopped the array and restarted the array, and the renamed share showed up as expected, and it is public as expected. but Windows cannot access it at all now.  It doesn't even give a login screen, just goes directly to "you do not have permission to access \\tower\renamedShare

 

I can create a new root level folder on the server, and the creator laptop can access it fine.  The other laptops get a login screen when trying to access that share.  Files moved into that share are full accessible from the creator laptop, but inaccessible from the other laptop.

 

Here is my share.cfg file and full diagnostics are attached.

# Generated settings:
shareDisk="yes"
shareUser="e"
shareUserInclude="disk2,disk3,disk4,disk5,disk6,disk7,disk8"
shareUserExclude=""
shareSMBEnabled="yes"
shareNFSEnabled="yes"
shareNFSFsid="101"
shareAFPEnabled="no"
shareInitialOwner="Administrator"
shareInitialGroup="Domain Users"
shareCacheEnabled="yes"
shareCacheFloor="2000000"
shareMoverSchedule="40 3 * * *"
shareMoverLogging="yes"
fuse_remember="330"
shareAvahiEnabled="yes"
shareAvahiSMBName="%h"
shareAvahiSMBModel="Xserve"
shareAvahiAFPName="%h-AFP"
shareAvahiAFPModel="Xserve"

kim-diagnostics-20160902-1631.zip