I've setup a user account, set the samba share private, set the user on unraid to have read/write access, and cannot connect.  Previously, while public, I could connect without issue.  This includes restarting windows PC and server.

Edited November 11, 20205 yr by rgreene42

 

The server information is not remembered and the net use * /delete will not fix it if it doesn't exist.

Windows 10 is set as a microsoft account login, not a local too.  So I'm still just as lost as I've used his post already to try to remedy this.

 

Try connecting to the share using the IP Address of the server---   \\IP_Address\Share_Name   ---  using Windows Explorer.

 

If that does not work, try using this--   \\Server_Name\Share_Name

 

Of course, the 'Share_Name' should be the name of your Private share.  (This technique has worked in the past to 'trick' the SMB server into allowing a second connection from a Client computer.)   Be sure that you observe all capitalization of share names as Linux is case sensitive! 

I only use the ip address.  I'll have to try again tomorrow.

Gave up, made another user with same access to fix it.  Probably, was the denied utterly issue from the first post, but no workaround other than an new user really worked for me.

Edited November 13, 20205 yr by rgreene42

2 minutes ago, rgreene42 said:

Gave up, made another user with same access to fix it.

If I remember correctly, SMB has some problems with passwords which contain certain special characters.  It is probably best to avoid using special characters in any SMB password.