SMB Protocol Issues
What SMB versions does CFS support?
Currently, CFS supports the primary functionalities of SMB versions, including SMB 1, SMB 2, and SMB 3.
Which operating system versions does SMB support respectively?
Since SMB 1 has significant shortcomings regarding both security and performance, it is strongly advised that users adopt SMB 2 or later versions, such as the operating system clients starting from Windows Vista onward. For details on SMB protocol support for each Windows version, refer to the table below:
| SMB version | Years | Corresponding OS version |
|---|---|---|
| SMB 3.1.1 | 2015 | Windows 10 / Windows Server 2016 |
| SMB 3.0.2 | 2013 | Windows 8.1 / Windows Server 2012 R2 |
| SMB 3.0 | 2012 | Windows 8 / Windows Server 2012 |
| SMB 2.1 | 2009 | Windows 7 / Windows Server 2008 R2 |
| SMB 2.0.2 | 2008 | Windows Vista SP1 / Windows Server 2008 |
| SMB 2.0 | 2007 | Windows Vista |
Which features are not supported by CFS SMB?
Currently, CFS SMB does not support the following features:
- Cross-protocol access is not supported, meaning users cannot use both NFS and SMB to access the same file system.
- File byte-range locking or client caching based on Oplocks and Lease is not supported.
- File ACL management is not supported.
- Asynchronous file I/O is not supported.
- SMB 3 advanced features like multichannel, persistent file handles, SMB direct, and SMB directory leasing are not supported.
- IOCTL/FSCTL operations, such as sparse files, file compression, network card status queries, and reparse points, are not supported.
Why is the update of file properties lagging in some editors within Windows Explorer?
Take Notepad as an example: If a user opens Notepad, edits content, and saves the file, they might notice the file size doesn't update right away. In such cases, right-clicking to view the “General” properties or refreshing Windows Explorer will display the updated size.
This issue arises from how certain editors in Windows (like Notepad) update the file properties displayed in Windows Explorer during edits. By this time, the file’s actual properties have already been updated; however, Windows Explorer has failed to refresh the display. Hence, this issue does not impact typical usage. For other editors like WordPad, this problem does not occur.
