SMB Failure on Electric Eel Upgrade (Server Seen, Zero Directories)

TrueNAS General
1

After upgrading to Electric Eel 24.10.0.2 from the previous release train I have zero SMB function. My pool and datasets are visible in TrueNAS Web UI, but can’t access files from Windows SMB which was previously working on DragonFish. Now Windows just tries to load the directories without any success

I do have a drive adapter, which from another thread looked like it might be a potential problem for now?? Kernel or BIOS related setting? Not certain that applies here since I can see datasets
LSI 9211-8i 6G SAS HBA FW:P20 IT Mode ZFS FreeNAS unRAID 2* SFF-8087 SATA US

image
image1104×825 67.1 KB

image
image1147×1139 109 KB

image
image1149×659 45.2 KB

image
image1144×1483 121 KB

image
image1043×1090 55.7 KB

Did I miss something critical for the upgrade process? I have restarted multiple times, and “upgraded the pool”. I have now also removed any saved Windows Credentials for TrueNAS and not being prompted for a username/password

2

I noticed that you’re connecting as “nobody”. This functionality is deprecated (disabled by default) in Windows. Is it possible you’re running into a client-side issue?

3

I am not intending to connect as “nobody” – but I noticed that too. Possibly after I removed saved Windows credentials

I would prefer that I am prompted for a password logon but any connectivity is better than what I have right now.

4

Try typing from command prompt net use /delete * to forget all of your network shares, or log out of Windows and log back in.

Then try to “map it” as a network drive, instead of trying to navigate to the NAS using WS-Discovery. Make sure to check the box “Use Other Credentials”.

5

C:\WINDOWS\system32>net use /delete *
There are no entries in the list.

I did find that I had some SMB 1.0 feature enabled, which is now disabled and requires a restart (Windows 10 tip: Stop using the horribly insecure SMBv1 protocol)

Trying to manually map a network drive fail for: \\truenas OR \\TRUENAS OR \\192.168.1.50

I was prompted for credentials, failed to connect and Windows troubleshooter was unable to resolve

6

Try \\192.168.1.50\BIZ-DEV

You ran this as administrator. You’d want to run it as the currently logged in user, you shouldn’t have elevated to admin. These mappings are user settings not system ones.

1 Like
7

CMD without admin elevation returned same error

Try \\192.168.1.50\BIZ-DEV

This worked! After I mapped that as a network drive, I was able to enter credentials and get some access…

Now that I try the TRUENAS network location, I can see my other datasets and open them (although loading very slowly). Tried to open an archived YouTube video, but it is PAINFULLY slow to the point where it is “stuck” buffering in VLC & unviewable – only the thumbnail preview is functional.

Perhaps the file system/ZFS/cache needs time to rebuild at this point?