Skip to content

Commit 6af2ffe

Browse files
b-ahibbardb-ahibbard
committed
unsupported smb
1 parent 610cfbd commit 6af2ffe

File tree

1 file changed

+29
-21
lines changed

1 file changed

+29
-21
lines changed

‎articles/azure-netapp-files/sever-message-block-support.md

Lines changed: 29 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -75,27 +75,35 @@ This FSCTL is used by Hyper-V for space efficiency. For example, if file deletes
7575
| Windows administrators mapped to root UNIX user | Users in Active Directory that are listed as Administrators (or users specified as Administrators in Active Directory connections) map as the UNIX user root in dual protocol environments. | Enabled |
7676
| Idle timeout before SMB session disconnects | SMB sessions remain connected for 900 seconds if left idle. | 900 seconds |
7777
| [Dynamic Access Control (DAC)](/windows-server/identity/solution-guides/dynamic-access-control-overview) | DAC isn't supported with Azure NetApp Files volumes. | Disabled |
78-
| File system sector size | Azure NetApp Files will report sector sizes of 4096 bytes to clients. In rare cases, Windows applications require 512 bytes, which is not supported in Azure NetApp Files. Consult with your application vendor if there are concerns over sector size requirements. | 4096b (4KiB)
79-
Fake open support “Fake open” is one way that Azure NetApp Files optimizes open and close requests when querying for attribute information on files and directories for better performance. In some cases, this functionality can cause pending file deletion messages not to be passed on to clients who are attempting access to a file that is in the process of being deleted. Enabled
80-
UNIX extensions Enabling UNIX extensions allows the SMB server to transmit POSIX/UNIX security information over SMB to the UNIX-based client, which then translates the security information into POSIX/UNIX security. This option is only needed when leveraging SMB over Linux-based clients (such as MacOS). Disabled
81-
Search short names “Short names” in SMB limit file names to a maximum of 8 characters for the name and 3 for the extension. (8.3)
82-
83-
Names exceeding that limit will truncate and use a ~ in place of the remaining characters. For instance, a file named “not-a-short-name.txt” truncates to “not-a-sh~.txt.”
84-
85-
A search of short names (where an SMB find will look for short and long names) does not take place in Azure NetApp Files. Disabled
86-
Guest user access Guest user access is disallowed in Azure NetApp Files. Disabled
87-
Null user access NULL user access is disallowed in Azure NetApp Files. Disabled
88-
Hide “dot” files Hide files with a “.” preceding the name.
89-
For instance, .ssh. Disabled
90-
SMB multichannel
91-
SMB feature that provides support for multiple TCP connections over the same SMB share mount point. This provides increased performance for some workloads. Enabled
92-
Maximum connections per multichannel session Maximum simultaneous allowed TCP connections using multi-channel. In general, 4 is enough to see significant performance gains.
93-
32
94-
Large MTU Unrelated to network MTU size. Instead, this is the maximum size allowed by the SMB protocol for transfers. This is similar to wsize/rsize in NFS. Azure NetApp Files supports up to 1MB transfer sizes in SMB. Enabled
95-
NetBIOS over TCP port 139 Keeps TCP port 139 open for NetBIOS traffic. Enabled
96-
NBNS over UDP port 137 UDP port 137 is closed to NBNS service. Disabled
97-
SMB max credits SMB credits determine the number of outstanding simultaneous requests that the client can have on a particular connection. Azure NetApp Files allows up to 128 per connection, while Windows clients can potentially send more simultaneous requests to Azure NetApp Files than is allowed. In these cases, requests will wait until new credits are available. See Tuning parameters for SMB file servers for more information.
98-
128
78+
| File system sector size | Azure NetApp Files will report sector sizes of 4,096 bytes to clients. In rare cases, Windows applications require 512 bytes, which isn't supported in Azure NetApp Files. Consult with your application vendor if there are concerns over sector size requirements. | 4,096b (4 KiB)
79+
| Fake open support | "Fake open" is one way that Azure NetApp Files optimizes open and close requests when querying for attribute information on files and directories for better performance. In some cases, this functionality can cause pending file deletion messages not to be passed on to clients who are attempting access to a file that is in the process of being deleted. | Enabled |
80+
| UNIX extensions | Enabling UNIX extensions allows the SMB server to transmit POSIX/UNIX security information over SMB to the UNIX-based client, which then translates the security information into POSIX/UNIX security. This option is only needed when leveraging SMB over Linux-based clients (such as MacOS). | Disabled |
81+
| Search short names | []"Short names"](/openspecs/windows_protocols/ms-fscc/18e63b13-ba43-4f5f-a5b7-11e871b71f14) in SMB limit file names to a maximum of 8 characters for the name and 3 for the extension (8.3). <br></br> Names exceeding that limit are truncated and use a tilde (~) in place of the remaining characters. For example, a file given the name "not-a-short-name.txt” is shortened to "not-a-sh~.txt." <br></br> A search of short names (where an SMB find looks for short and long names) doesn't take place in Azure NetApp Files. | Disabled |
82+
| Guest user access | Guest user access is disallowed in Azure NetApp Files. | Disabled |
83+
| Null user access | NULL user access is disallowed in Azure NetApp Files. | Disabled |
84+
| Hide "dot" files | Hide files with a "." preceding the name, such as .ssh. | Disabled |
85+
| [SMB multichannel](azure-netapp-files-smb-performance.md#smb-multichannel) | This SMB feature provides support for multiple TCP connections over the same SMB share mount point, providing increased performance for some workloads. | Enabled |
86+
| Maximum connections per multichannel session | Maximum simultaneous allowed TCP connections using multi-channel. In general, [four is enough to see significant performance gains](azure-netapp-files-smb-performance.md#performance-for-smb-multichannel). | 32 |
87+
| Large MTU | Unrelated to network MTU size. Instead, large MTU is the maximum size allowed by the SMB protocol for transfers. Large MTU is similar to wsize/rsize in NFS. Azure NetApp Files supports up to 1-MB transfer sizes in SMB. | Enabled |
88+
| NetBIOS over TCP port 139 | Keeps TCP port 139 open for NetBIOS traffic. | Enabled |
89+
| NBNS over UDP port 137 | UDP port 137 is closed to NBNS service. | Disabled |
90+
| SMB max credits | SMB credits determine the number of outstanding simultaneous requests that the client can have on a particular connection. Azure NetApp Files allows up to 128 per connection, while Windows clients can potentially send more simultaneous requests to Azure NetApp Files than is allowed. In these cases, requests wait until new credits are available. For more information, see [Tuning parameters for SMB file servers](/windows-server/administration/performance-tuning/role/file-server/smb-file-server#tuning-parameters-for-smb-file-servers). | 128 |
9991

10092

10193
## Unsupported SMB features in Azure NetApp Files
94+
95+
- Encrypted File System (EFS)
96+
- Logging of NT File System (NTFS) events in the change journal
97+
- Microsoft File Replication Service (FRS)
98+
- Microsoft Windows Indexing Service
99+
- Remote storage through Hierarchical Storage Management (HSM)
100+
- Quota management from Windows clients
101+
- Windows quota semantics
102+
- The LMHOSTS file
103+
- NTFS native compression
104+
105+
## SMB share property support information in Azure NetApp Files
106+
107+
| Share property | Definition/Considerations | Default |
108+
| --- | ------ | - |
109+

0 commit comments

Comments
 (0)