New computer, same login credentials, lost permissions?

[ucrbuffalo]

My mobo on my main desktop died so I upgraded to a new system. When I installed Win10, I used all the same login credentials to get into my PC as I had on the previous setup. I thought that I would have all the same permissions in FreeNAS when I tried to read/write, but it looks like I don't have permission to write to the share. I can still read all the data as before. I'm not sure what I've done wrong, or where to start looking other than in the Shares tab (all looks normal to me) or the user (again, looks normal to me, but don't take my word for it).

Old rig:
Intel Core i5-4670K
ASRock Z87 Extreme4
MSI GTX 1060 6GB Gaming-X
G.Skill Ripjaws X 16GB (2x 8GB)

New rig:
Ryzen 1700X
Gigabyte GA_AX370-Gaming
MSI GTX 1060 6GB Gaming-X
G.Skill Trident Z RGB 32GB (2x 16GB)

FreeNAS version: FreeNAS-9.10.2-U5 (561f0d7a1)

Thanks in Advance

 

[Ericloewe]

Did you by any chance move from a local user account to a Microsoft account or vice-versa? Windows' credentials management is rather silly at times.

 

[ucrbuffalo]

The account was, and is, a local account only.

Maybe I could try deleting and recreating the User in FreeNAS?

 

[Ericloewe]

Maybe I could try deleting and recreating the User in FreeNAS?

No, that doesn't address any issues.

Are you using the same username but different passwords on the client and the server?

 

[ucrbuffalo]

Login for the user on the server side didn't have a password. But other than that, yes.

 

[Ericloewe]

Okay, that's going to cause some trouble.

My recommendation is to do things The Right Way (tm) - separate usernames (to make Windows logins easier) and passwords. Just have Windows store the credentials and it'll just work after that.

 

[ucrbuffalo]

Perhaps I misunderstood the question? The login for Windows is different from the login I use to access the GUI. However, the user I made inside FreeNAS has the same credentials as the Windows machine. I did it this way when I set it up because Windows was using incorrect credentials initially. When I set it this way, it worked.

 

[Ericloewe]

However, the user I made inside FreeNAS has the same credentials as the Windows machine.

Right. Unless the passwords match, that's going to be a pain in the ass. Do they match? If so, something else is going on.

 

[ucrbuffalo]

Right. Unless the passwords match, that's going to be a pain in the ass. Do they match? If so, something else is going on.

Passwords match.

 

[Ericloewe]

I wonder what happened there... Try to apply default permissions and then redo the specifics from Windows.

 

[ucrbuffalo]

I wonder what happened there... Try to apply default permissions and then redo the specifics from Windows.

So here's what I've done (to no avail):
I applied the default permissions to the SMB share. I disconnected the network drive so that I could remap it. When I did so, I selected "Reconnect at startup" and made sure not to select "Connect with different credentials". I do not have permission to write, but I still have permission to read.

 

[Ericloewe]

Then the dataset in question has to be owned by the wrong user. Default permissions are full control for owners, read-only for others.

 

[ucrbuffalo]

Then the dataset in question has to be owned by the wrong user. Default permissions are full control for owners, read-only for others.

A-HA!!!!
Got it fixed. Thank you so much for the advice and direction.
Here's what I did:
In the sidebar, I navigated to Storage>Volumes>mnt/Primary>mnt/Primary/Media [This is the share I was having problems with].
Then I selected "Change Permissions" Turns out the Owner (Group) had somehow been changed to "wheel" instead of "HomeNetwork", which is the group each of the Users are in.
So I changed it back to "HomeNetwork", saved, and tried again.
Viola! It works!

Thank you again @Ericloewe for your kind direction.

EDIT: Oh, I should also add that if this is the problem you're experiencing to make sure you check "Set Permission Recursively" so you have write permissions in all the existing folders too, not just the root.

 

[Ericloewe]

Glad that's fixed.

 

[ucrbuffalo]

I added this in the post above, but Wanted to make sure it was here too. I also needed to check the box for "Set Permission Recursively" so that I would have access to all the folders I've already created in the share.