I reported about this issue in this thread (https://forums.mydigitallife.net/threads/copying-files-speed-decreases-after-update-to-22h2.85904/) but is possibly not the same. My network consists of two Belkin RT3200 which both run Openwrt. One has the role of router and the other as AP. My NAS is connected to the router (Asustor 6202). Two Windows 11 machines are connected to the AP. All network traffic runs over copper. Machine A (Asus CH VIII with AMD 5900x and Intel I211 NIC) was recently updated to 22H2. Machine B (a mini PC with Intel I3 and also Intel I211 NIC) is still running 22H1. On both machine A and machine B I get the expected 1 Gbps speeds (about 110 MB/s). I measured this with iperf3, both upload and download to the NAS. Now comes the strange thing. When a large file (e.g. 5 GB) is downloaded (from the NAS) to machine A, the download speed does not exceed about 90 MB/s and fluctuates quite a bit. On the other hand, machine B does what is expected, a constant download speed of about 110 MB/s. The upload from both machines to the NAS is as expected. When I run WindowsToGo 22H1 on machine A, everything seems to work at the expected download speed. Before the 22H2 update the download speed was also as expected. So I would conclude that there is something with 22H2. I resorted already to a complete new fresh install of 22H2 on machine A but this didn't improve the issue. Hardware wise I've already switched cables and used different ports, threw out the AP, tried different Intel drivers but nothing affected the above behavior. Anyone recognize this behavior? Does anyone know what else I could try?
I guess are you talking about SMB transfers. And SMB is notorious for beeing an ever changing protocol. So first I would check if your machines has the same configuration (say smb1protocol, is enabled in both machines, only one of them, both, none ? ) Then I would test a different mean. I guess you can enable the ftp server on your nas, try to enable it and check the speed. If the transfer via ftp is fast while via smb is slow, we can rule out any low level network problem, and focus on SMB settings. If the transfer via ftp is slow as well, it's a different matter (nic driver, firewall settings, advanced nic settings and so on)
Thanks for your respons. Yes, i'm talking about SMB transfers. This is the smb config of machine B (running 22H2) .. and this on machine A (unfortunately Get-SMBConnection doesn't work here, i don't know why) ...and this is the SMB configuration of the I tested a large (~6 GB) file download to machine B over a ftp connection (with Winscp) and it downloaded at around 105-110 MB/s. So maybe a bit lower than max. but still OK. This is that same file copying via the Windows explorer (on machine B). For machine A this is an almost straight line at around 110 MB/s.
So If I understand correctly The speed of machine A is the same as machine B via ftp. Correct ? Via SMB the slower machine is slower than the faster machine in both directions? If the above is correct try to look for any meaningful difference in SMB configuration comparing the result of both Get-SmbServerConfiguration and Get-SmbClientConfiguration eventually paste them here (maybe under spoiler tag, to not clutter the forum)
FTP download seems to be fine on both machines. SMB download is too slow machine B (22H2). Spoiler: Screenshots machine B (22H2 slow) Code: PS C:\Users\Jack> Get-SmbClientConfiguration CompressibilitySamplingSize : 524288000 CompressibleThreshold : 104857600 ConnectionCountPerRssNetworkInterface : 4 DirectoryCacheEntriesMax : 16 DirectoryCacheEntrySizeMax : 65536 DirectoryCacheLifetime : 10 DisableCompression : False DormantFileLimit : 1023 EnableBandwidthThrottling : False EnableByteRangeLockingOnReadOnlyFiles : True EnableCompressibilitySampling : False EnableInsecureGuestLogons : True EnableLargeMtu : True EnableLoadBalanceScaleOut : True EnableMultiChannel : True EnableSecuritySignature : True EncryptionCiphers : AES_128_GCM, AES_128_CCM, AES_256_GCM, AES_256_CCM ExtendedSessionTimeout : 1000 FileInfoCacheEntriesMax : 64 FileInfoCacheLifetime : 10 FileNotFoundCacheEntriesMax : 128 FileNotFoundCacheLifetime : 5 ForceSMBEncryptionOverQuic : False KeepConn : 600 MaxCmds : 50 MaximumConnectionCountPerServer : 32 OplocksDisabled : False RequestCompression : False RequireSecuritySignature : False SessionTimeout : 60 SkipCertificateCheck : False UseOpportunisticLocking : True WindowSizeThreshold : 8 PS C:\Users\Jack> Get-SmbServerConfiguration AnnounceComment : AnnounceServer : False AsynchronousCredits : 64 AuditSmb1Access : False AutoDisconnectTimeout : 15 AutoShareServer : True AutoShareWorkstation : True CachedOpenLimit : 10 DisableCompression : False DisableSmbEncryptionOnSecureConnection : True DurableHandleV2TimeoutInSeconds : 180 EnableAuthenticateUserSharing : False EnableDirectoryHandleLeasing : True EnableDownlevelTimewarp : False EnableForcedLogoff : True EnableLeasing : True EnableMultiChannel : True EnableOplocks : True EnableSecuritySignature : False EnableSMB1Protocol : False EnableSMB2Protocol : True EnableSMBQUIC : True EnableStrictNameChecking : True EncryptData : False EncryptionCiphers : AES_128_GCM, AES_128_CCM, AES_256_GCM, AES_256_CCM InvalidAuthenticationDelayTimeInMs : 0 IrpStackSize : 15 KeepAliveTime : 2 MaxChannelPerSession : 32 MaxMpxCount : 50 MaxSessionPerConnection : 16384 MaxThreadsPerQueue : 20 MaxWorkItems : 1 NullSessionPipes : NullSessionShares : OplockBreakWait : 35 PendingClientTimeoutInSeconds : 120 RejectUnencryptedAccess : True RequestCompression : False RequireSecuritySignature : False RestrictNamedpipeAccessViaQuic : True ServerHidden : True Smb2CreditsMax : 2048 Smb2CreditsMin : 128 SmbServerNameHardeningLevel : 0 TreatHostAsStableStorage : False ValidateAliasNotCircular : True ValidateShareScope : True ValidateShareScopeNotAliased : True ValidateTargetName : True Spoiler: Screenshot machine A (22H1 fast) Code: PS C:\Users\QotomX> Get-SmbClientConfiguration SkipCertificateCheck : False ConnectionCountPerRssNetworkInterface : 4 DirectoryCacheEntriesMax : 16 DirectoryCacheEntrySizeMax : 65536 DirectoryCacheLifetime : 10 DormantFileLimit : 1023 EnableBandwidthThrottling : True EnableByteRangeLockingOnReadOnlyFiles : True EnableInsecureGuestLogons : True EnableLargeMtu : True EnableLoadBalanceScaleOut : True EnableMultiChannel : True EnableSecuritySignature : True ExtendedSessionTimeout : 1000 FileInfoCacheEntriesMax : 64 FileInfoCacheLifetime : 10 FileNotFoundCacheEntriesMax : 128 FileNotFoundCacheLifetime : 5 ForceSMBEncryptionOverQuic : False KeepConn : 600 MaxCmds : 50 MaximumConnectionCountPerServer : 32 OplocksDisabled : False RequireSecuritySignature : False SessionTimeout : 60 UseOpportunisticLocking : True WindowSizeThreshold : 8 EncryptionCiphers : AES_128_GCM, AES_128_CCM, AES_256_GCM, AES_256_CCM PS C:\Users\QotomX> Get-SmbServerConfiguration AnnounceComment : AnnounceServer : False AsynchronousCredits : 64 AuditSmb1Access : False AutoDisconnectTimeout : 15 AutoShareServer : True AutoShareWorkstation : True CachedOpenLimit : 10 DisableSmbEncryptionOnSecureConnection : True DurableHandleV2TimeoutInSeconds : 180 EnableAuthenticateUserSharing : False EnableDownlevelTimewarp : False EnableForcedLogoff : True EnableLeasing : True EnableMultiChannel : True EnableOplocks : True EnableSecuritySignature : False EnableSMB1Protocol : False EnableSMB2Protocol : True EnableStrictNameChecking : True EncryptData : False IrpStackSize : 15 KeepAliveTime : 2 MaxChannelPerSession : 32 MaxMpxCount : 50 MaxSessionPerConnection : 16384 MaxThreadsPerQueue : 20 MaxWorkItems : 1 NullSessionPipes : NullSessionShares : OplockBreakWait : 35 PendingClientTimeoutInSeconds : 120 RejectUnencryptedAccess : True RequireSecuritySignature : False ServerHidden : True Smb2CreditsMax : 2048 Smb2CreditsMin : 128 SmbServerNameHardeningLevel : 0 TreatHostAsStableStorage : False ValidateAliasNotCircular : True ValidateShareScope : True ValidateShareScopeNotAliased : True ValidateTargetName : True RestrictNamedpipeAccessViaQuic : True EnableSMBQUIC : True EncryptionCiphers : AES_128_GCM, AES_128_CCM, AES_256_GCM, AES_256_CCM
"EnableBandwidthThrottling" is a parameter that smells suspicious and is different on A/B Also there are some compression related parameter that are missing on one machine, try to set those in line with fast machine and try if something changes. (restart the server and workstation services between test (or reboot the machine alltogether)
Well, i tried chancing some parameters but no real improvement. Mostly it gets worse. Additionally, I installed the same Intel driver (12.18) on the slow machine as on fast machine to eliminate this variable. Also no improvement. I'm starting to think this is something buried deep in Win 11. Unless someone has something to try i just have to live with it or go back to 22H1.
Well... it could be just a regression in W11, if that's the case you could only hope they fix it on nex CU's Whatever, you posted the relevant data maybe some networking guru has a better idea than me about how to fix (or workaround your problem). Perrsonally I use ftp (filezilla server, not the MS one which is slow) more than SMB given I need to transfer files not just on windows clients but also Linux and android. And there the speed advantage is really huge (like 5x the speed of SMB)
@Jack007, I own 2 ASUSTOR NAS and I run Windows 10 and 11, I never got no decreased speed! on my base 1000mbps LAN and I transfer large 4.7 and 8GB files I get 113MB/sec.. ATGPUD2003
FYI, Go your SMB setting on NAS Storage, and try change SMB Signing: AUTO and uncheck Enable only NTLMv2. then Click Apply.. Also suggest is go to Settings and see "Network" if you are using DHCP Server Setting, Disable it, and use Static IP address and DNS, Submask behind of your DHCP Server this way can reserved.. ATGPUD2003
Tried all of the above but no improvement. As stated in the MS message: I guess we just have to wait for a fix.
Likely the asustor doesn't matter but different NICs and/or drivers combination between yours and his PC matters