cFosSpeed didn't see smb protocol

and close avoid data packet loss option on preferences
i found QUIC in agreements.QUIC_C QUIC_S

can't inspect besides click advanced

And cfosspeed disfunction has more，
i often see unknow，they should gonna support tls1.3(QUIC）promptly(but they don't) ，SSL_S i haven't seem ever

emm，i'm not network expert.And i’m poor at English.There's SSL has a lot of different uses（e.g.certificate https required), i see most SSL in cfosspeed connect interface is SSL_c OR bundelidk.
SMB3.1.1 maybe work mixing SSL/TLS with QUIC，idk how to setting SMB those opinions 

Capture client and server sided traffic

docs.microsoft.com/en-us/windows-server/storage/file-server/smb-over-quic
docs.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/smb-multichannel-troubleshooting
The second webstie's codes idk how smb client print info.
Sorry for waste ur time, i couldn't offer satisfied answear.

1.emmm,all my suggestion won't help u with the cfosspeed bug(support SMB tx traffic),i mentioned sniff software because i think its a possible way to traffic identification.Despite of Cfosspeed not whole PCAP,  unkow links with unknow protocols always in the cfos connections window(localhost:1487/cfosspeed/console.htm.)


2.Of course，but i'm not network expert. Like above opinion,  i think cfosspeed just read the little information exposed（e.g.Package Header).or database already.SMB3 didn't be added , i think it's  unlike SNMP or early SMB, the security and other encryption means will conceal itself. Of course i think Sniff software can find these （by decrypting）when cfosspeed didn't support.Cfosspeed connection window can show tons of unkown, maybe you can try to check ports 80，443，445，svhost or something realted with SMB in advanced connections.
If u can‘t find whatever u know, reach ur goal (bug making other process goed laggy)，close SMB services（bad way),or cfosspeed(idk effect)


other related article
docs.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/slow-file-transfer mmaybe it can be reverse.

1. wireshark is just sniffer, it won't help you at any moment with the cFosSpeed SMB bug, idk why did you mention it
2. tunneling SMB via SSL is possible, there is many solutions.. if u google "windows 10 smb over ssl" you will get lots of results like:
"Configuring Samba with SSL - O'Reilly"
https://www.oreilly.com/openbook/samba/book/appa.pdf

Of course,i have same expectation that not use profession program
 Probably  smbcmp will be more easy to use.PPT below



Aptel-New_SMB3_features_in_Wireshark.pdf
7-day-limited i cant bypass

i think that couldnt be successful.SSL tunnel need professional unpackage program like Wireshark，In my mind，cfosspeed should be easy to use with GUI and like other light component hiden in Butler software（e.g. Huorong Softwave  and its huorong sword/traffic monitor，or PCHunt).Emm,In spite of its（cfosspeed）  drive program （Qos and NDIS6, it has problem and disfunction like this data whatever network bandwith was authentic.
Maybe cfosspeed can monitor specific ports by ssl/tls？If it‘s true，it will  need type related Console command   in cfosspeed CMD manually（idk，maybe spd cons?but it just like GUI localhost:1487/cfosspeed/console.htm).
Or maybe hrping could do it?No,its cant do (its special technology is ICMP)
I think its disfunction can last for a longer period.Because windows10 SMB3 has different signature with SMB2（the above one idk，the next one you can look wiki below).If u wanna try Wireshark,remember typing right SSL ports like picture below and search related information 




you can try read wireshark document（ i havent use this program）
wiki.wireshark.org/SampleCaptures#smb3-1-handshake

Hello, thanks for trying to help,
but question was not about how to get SMB protocol secured (which I believe is possible with SSL tunneling?), but about the cFosSpeed application:
it's mission is to gain control over all the network traffic on your PC,
but in case of SMB traffic - it was just unrecognized by cFosSpeed, and that actually caused it's mission failure, because SMB took all the network bandwidth while cFosSpeed didn't even see that, so all other applications started suffering network bandwidth insufficient and lag.

I'd measure that as major bug and disfunction.

But I didn't checked that bug with the lastest cFosSpeed version and we didn't got any official answer from the support, so current state of this question is unknown.

In the next month I'm going to copy by SMB big amounts of data to backup some files on external LAN filestorage and will gonna recheck it again.

maybe on smb protocol‘s case  working principle   based on the low-level Look at the remote computer  Architecture 
Even it can transfer reach the memory space，i majored in MCU course，but i was academic scum and i dont learn about systerm。
You can read recommend technology articles below, I hope them could help u assisted with ur goal that solution（e.g. the secondary links supports solution by using firewall /monitor application supported by windows self?i cant understand)


Related articles：
How to Secure SMB Traffic in Windows (microsoft.com)  
Secure SMB Traffic in Windows Server | Microsoft Docs
docs.microsoft.com/en/windows-server/storage/file-server/smb-security


because the forum newbies 7 day limited, i cant post external links

Hello,
as topic says if I try to copy some files with using SMB protocol (windows network shares) cFosSpeed didn't see that traffic.
I'm using Total Commander to connect remote share and copy file and there is no TC in cfos connections window neither it's meter showing that traffic in transfer amount counters.

Any solution Other processes goes laggy since smb protocol takes all possible channel width.

I'm using cFosSpeed version 12.002512 on Windows 10 pro