SMB share hanngs most windows machines but not others

Let me start by saying I came from the widows world and am Very new to truenas. Storagespaces was way to slow for my bulk storage so I built a truenas system adn up untill today thought it was all going great. untill now I had always conected with just one of my cluster nodes to the nas. its been flawless. I can do 4GBps SMB wich is the fastests I have ever pushed storage. I moved my plex server over and its been super fast. then I found tdarr and thought “cool, lets use all my spare cpu power to transcode”.

I maped the SMB share on 3 other Identiacl nodes and it when great…till I clicked on it. instant freeze of the whole OS. give it 2 minutes an we are back…untill you click another folder than 2 monre minutes of freeze.

heres the kicker. the 4 node computers are identaical. they are a hyper-v cluster and were setup with scripts. so hardware and software is all the same. node 4 has no issues. It breezes through directorys and pulls data as fast it can to its SSD’s. nodes 1 2 and 3 for some reason freeze when opening the share.

I have ne more server (the old storage server) and it also has no issues.

Truenas and nodes 1,2,3, and 4 are Dell r820 with quad E5-4657 v2, 768 ram and quad 40GB nics in teams (LACP on Trunas)

all of them talk to the SMB share on the old storage server with no issue but nodes 1,2 and 3 freeze talking to the truenass share. I have restarted all the machine exept the truenas.

the only differenc I know is that node 4 and the old storage server where connected when the share was empty. then I copied over 40TB to the share.

all of these nodes are server 2022 and have indexing and search turned off.

Sorry to double post. I couldent find a way to edit my original post but I have more information.

I restarted the truenas server and all the nodes could brows about 3 directories deep…but now its exactly the same. but I noticed my old plex sever that ran on windows in a virtual server on the cluster works just fine. so Its not netwroking as the virtual servers use the same netwroking as the hosts.

looking more and more like a wierd windows issue. Node 4 still has no issue and the old storage server is also fine. still weird that this is the only SMB share that has an issue. I have other smb shares on other windows servers that still work fine. its only the truenas smb share.

Ping is perfect sub millisecond on all nodes to the truenas and between all nodes.

Just going to post some generalities that I would do in these cases of weird and wonderful Windows SMB.

Are there stored credentials?
Have you tried a net use /del from the troubled clients? and then reconnect?
Perhaps a ipconfig /flushdns may reset the DNS flip flop which sometimes locks in.
Is it possible to change to only one DNS server?
Assuming Win2022 has no registry overrides to SMB versions, but does TrueNas have any auxiliary parameters?
What does a netstat -a or -b have to say during a hang situation?

Hopefully a few places to check things.

Thnaks for the reply,

there are no stored credetials. I have removed them from credential manager and in an effort to test stuff added the truenas to the domain and am now using domain credentials but some result.

no use for net use as I am not curently mapping the drives. just browsing the share but when mapped they act the same way.

defitaly flused DNS but even when using IP address to eleimate DNS issue its the same.

no overrides in server 2025 and all 4 nodes are clean installes with noting but hyper-v and failover clustering featuers. netwroking is idental and works for clustered storage wich is really picky. All SMB shares work exept the truenas share but the thrunas share works on every computer but nodes 1, 2 and 3. however VMs running on these nodes access the share just fine so its not physical wiring.

I made a quick vid to help people understand. on the right is an identical SMB share on server 2019. you can see I can browse areound super fast. on the left is the Truenas share and I can only go 2 folders deep. 3rd folder will always freeze the system. any 3 folders, even going 2 folders deep then hitting back will freeze the syste for 2 minutes. then it will unfreeze and I can go 2 more folders.

https://www.youtube.com/watch?v=W3Auk7a-xew