orondf343

I have tried the tuning command, Network I/O Boost, stopping WSearch. I have yet to try the network adapter options, but have tried disabling LargeSendOffload in the past. I have also managed to reproduce this issue in a Win11 virtual machine running on the server itself.

Hi, I think I am experiencing the same issue. Each file takes 35 seconds to start transferring, after which it transfers normally. These events (ID 1020) appear in Event Viewer for each file (details removed): File system operation has taken longer than expected. Client Name: Client Address: User Name: Session ID: Share Name: File Name: Command: 8 Duration (in milliseconds): 35379 Warning Threshold (in milliseconds): 15000 Guidance: The underlying file system has taken too long to respond to an operation. This typically indicates a problem with the storage and not SMB. The duration is always just over 35 seconds. This event tells me that something is wrong at the filesystem level. I've also noticed that when the SMB client first connects to the share (which also takes around 35 seconds), I can't load the shared folder in File Explorer on the server. I also get the same warning in Event Viewer for the desktop.ini file. I have occasionally experienced the same latency issue when browsing to a folder or transferring files on the server itself, but not often, and certainly not every single time as with SMB. Edit: The above is what happens consistently when the SMB client is Windows 10 and the share is on the DrivePool volume. I don't have any issues when the SMB client is Total Commander on Android.