Lost permission to the server

[AltecBX]

Hi, I had to reboot my Windows 11 machine for an update. Once I did, my mount was X out.

I also can't access my server with my name and PW like I've had before. I click on my TrueNas server, and it brings up my name and tells me to put in my password. I enter my password and it says "You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions."

What can I do? My password has never changed.
I even went to Accounts > Users > Edit the user >enter password to confirm I'm using the correct password and that didn't work. I also turn on and off SMB services. I rebooted my windows machine several times well.

Just tested it on my mac, and everything works fine there.

 

[anodos]

Hi, I had to reboot my Windows 11 machine for an update. Once I did, my mount was X out.

I also can't access my server with my name and PW like I've had before. I click on my TrueNas server, and it brings up my name and tells me to put in my password. I enter my password and it says "You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions."

What can I do? My password has never changed.
I even went to Accounts > Users > Edit the user >enter password to confirm I'm using the correct password and that didn't work. I also turn on and off SMB services. I rebooted my windows machine several times well.

Just tested it on my mac, and everything works fine there.

Check what creds the Windows box is passing to the TrueNAS server. midclt call smb.status AUTH_LOG | jq make sure it's not a microsoft account. Do you have guest access enabled on the server? This is a legacy feature that doesn't necessarily work well with modern security settings in Windows.

 

[AltecBX]

I don't have a guest account enabled on the server
I ran that line on the Shell, and I got back that it's an NTLMv2. Don't know what to do now?

 

[AltecBX]

Update:
Just type in the server IP in windows explorer and boom I can see my share folders. (Read and write to it)
Why can't I still access it via the network?
\\192.168.1.5 - works
\\freenas - doesn't work
Media (\\freenas) (Z:) - Map drive doesn't work

 

[anodos]

Update:
Just type in the server IP in windows explorer and boom I can see my share folders. (Read and write to it)
Why can't I still access it via the network?
\\192.168.1.5 - works
\\freenas - doesn't work
Media (\\freenas) (Z:) - Map drive doesn't work

Do you have the netbios name server running on your server? Is "freenas" the netbios name of your server?

 

[AltecBX]

Yes that's the name.
Here is a picture of the settings on the SMB. (Nothing has changed in my settings for years)

 

[Redcoat]

Isn't the netbios name case-sensitive? Freenas...

Edit - I just tested and it doesn't seem to be for me anyway...

 

[AltecBX]

Isn't the netbios name case-sensitive? Freenas...

Edit - I just tested and it doesn't seem to be for me anyway...

Nope!
It works with lowercase, first-letter capital, or all capital case
I haven't changed any settings since I set this server up years ago.

 

[anodos]

Nope!
It works with lowercase, first-letter capital, or all capital case
I haven't changed any settings since I set this server up years ago.

I'm referring to netbios name server being enabled in `Network->Global Configuration`. You can check output of midclt call smb.status AUTH_LOG | jq and make sure that your client is using correct credentials when trying to access using the netbios name. Windows clients can store different credentials depending on how server is accessed. This is especially a concern if "guest access" is enabled for any shares on the server.