in 6.6.1 - Unable to access files shares from windows

[wegotg]

Last weekend my shares stopped working. I am able to browse the folders in the shares but not open or copy and files in the shares. I have run new permissions, created new share which ends up with the same problem, created new users and added to shares. nothing has worked. My dockers are still able to access the shares just fine. Any suggestions? Thank you. Tim

[trurl]

Are you talking about Windows network access to your shares? 

[wegotg]

20 minutes ago, trurl said:

Are you talking about Windows network access to your shares? 

yes, using a windows 10 or 7 machine to access the tower shares over the local area network. the shares do show up and prompt for a login. i am able to login and see the folders and files. i can browse the folders but am unable to open files. create new files. copy files. etc..

 

my setup has been working for about 3 years. my unraid and windows 10 are both at the latest versions.

 

Edited October 5, 2018 by wegotg

[trurl]

Are these all public shares? Did it always prompt for a login before or is this new behavior?

 

The thing about Windows is it will only allow one login to a remote computer at a time. And if you already have a login to the remote it won't take another one, even if it prompts you. It could be trying a different login than you think it is, then when that doesn't work, it prompts for another, but it won't use it anyway.

 

In Windows Control Panel, go to Credential Manager and delete any credentials to your Unraid server so they can be renegotiated.

 

There is a whole topic about this and other Windows network issues pinned near the top of this same subforum.

[wegotg]

15 minutes ago, trurl said:

Are these all public shares? Did it always prompt for a login before or is this new behavior?

 

The thing about Windows is it will only allow one login to a remote computer at a time. And if you already have a login to the remote it won't take another one, even if it prompts you. It could be trying a different login than you think it is, then when that doesn't work, it prompts for another, but it won't use it anyway.

 

In Windows Control Panel, go to Credential Manager and delete any credentials to your Unraid server so they can be renegotiated.

 

There is a whole topic about this and other Windows network issues pinned near the top of this same subforum.

The shares are a mix of public and secure. i have deleted the unraid credentials out of the Credential Manager. Built a brand new Windows 7 and 10 machine to eliminate any cache possibility.

 

[wegotg]

Getting the following errors in the sys log when trying to access files.

 

Oct  7 07:40:24 Tower smbd[28262]: [2018/10/07 07:40:24.980067,  2] ../source3/auth/auth.c:314(auth_check_ntlm_password)
Oct  7 07:40:24 Tower smbd[28262]:   check_ntlm_password:  authentication for user [bob] -> [bob] -> [bob] succeeded
Oct  7 07:40:24 Tower smbd[28262]: [2018/10/07 07:40:24.980478,  2] ../source3/auth/token_util.c:713(finalize_local_nt_token)
Oct  7 07:40:24 Tower smbd[28262]:   WARNING: Failed to create BUILTIN\Administrators group!  Can Winbind allocate gids?
Oct  7 07:40:24 Tower smbd[28262]: [2018/10/07 07:40:24.980592,  2] ../source3/auth/token_util.c:732(finalize_local_nt_token)
Oct  7 07:40:24 Tower smbd[28262]:   WARNING: Failed to create BUILTIN\Users group! Can Winbind allocate gids?
Oct  7 07:40:24 Tower smbd[28262]: [2018/10/07 07:40:24.980807,  2] ../source3/auth/token_util.c:713(finalize_local_nt_token)
Oct  7 07:40:24 Tower smbd[28262]:   WARNING: Failed to create BUILTIN\Administrators group!  Can Winbind allocate gids?
Oct  7 07:40:24 Tower smbd[28262]: [2018/10/07 07:40:24.980881,  2] ../source3/auth/token_util.c:732(finalize_local_nt_token)
Oct  7 07:40:24 Tower smbd[28262]:   WARNING: Failed to create BUILTIN\Users group! Can Winbind allocate gids?
Oct  7 07:40:24 Tower smbd[28034]: [2018/10/07 07:40:24.981152,  2] ../source3/smbd/close.c:805(close_normal_file)
Oct  7 07:40:24 Tower smbd[28034]:   bob closed file New Text Document.txt (numopen=2) NT_STATUS_OK
Oct  7 07:40:24 Tower smbd[28034]: [2018/10/07 07:40:24.981302,  2] ../source3/smbd/service.c:1120(close_cnum)
Oct  7 07:40:24 Tower smbd[28034]:   pc (ipv4:192.168.10.51:55382) closed connection to service TestShare

 

[wegotg]

Oct 7 07:54:41 Tower smbd[2427]: WARNING: The "null passwords" option is deprecated
Oct 7 07:55:41 Tower smbd[3045]: [2018/10/07 07:55:41.678269, 1] ../lib/param

[Frank1940]

Be sure that you read through this entire thread:

 

     https://forums.unraid.net/topic/71601-windows-10-spring-update-2018-changes-solved/

 

 

There is also a post in there about Win7 problems that 'happened' after MS decided to shutdown the Windows Discovery services on the Workgroups network settings.  It still works on the Home Network setting (for now). 

 

Understand that MS actually controls the SMB specs and they often make changes in it without informing the rest of the world.  Samba has been 'reversed  engineered'.  Most of these problems happen when MS makes a change to that spec (usually for security reasons).  Your Windows computers get the updates (perhaps unknown to you) and things are broken... 

[wegotg]

so i have discovered that this issue is only happening across vlans.

my tower is on vlan50 and my windows machine is on vlan10.

when i move my windows machine to vlan50 everything is working fine.

i have been running this vlans this way for years without issue.

something last weekend changed that.