📄️ Global Configuration Settings
The global configuration of tsmb.conf is found between the starting keyword ‘[global]’ and the ending keyword ‘[/global]’.
📄️ Domain
Name of workgroup (for stand-alone servers) or domain (for domain members). This should be full- qualified domain name (e.g., ‘example.com’) if you use Active Directory based domain.
📄️ Network Management
This section provides an overview of the essential configuration options required by Fusion File Share server to handle client requests.
📄️ RDMA
If your network card(s) supports RDMA (SMB Direct), then you can enable RDMA transport via tsmb.conf configuration file. Add the following lines into your global config (for IPv4 and IPv6 traffic):
📄️ SMB Dialects
You can limit the number of dialects exported by Fusion File Share server using the global configuration setting, ‘dialects’:
📄️ CIFS Unix Extension
This setting is only used for CIFS sessions to enable or disable so-called UNIX extensions. To enable UNIX extensions, set the ‘unix_extensions’ setting to ‘true’:
📄️ IPC$ Share Management
Windows defines a special IPC$ share that is used to access different services via RPC protocol. IPC$ is especially used for accessing srvsvc (Server Service) RPC, where RPC returns information about all registered shares.
📄️ Encryption
To force Fusion File Share server to encrypt all messages it sends, change the ‘encrypt_data’ setting to ‘true’.
📄️ Signing
SMB messages can be signed. If you want Fusion File Share server to accept only signed messages and drop all unsigned messages, configure the ‘require_message_signing’ setting to ‘true’:
📄️ Server Name
Server name. If this is not set, local hostname is used. The length of the name can not exceed 15 bytes because of NetBIOS limitations.
📄️ Server Comment
Used for specifying an optional comment string describing the server. This value will be used as a comment in browser announcement frames and is also visible when executing ‘net view’ on Windows command prompt or powershell.
📄️ User Account
Fusion File Share server supports two types of authentications: NTLM and Kerberos.
📄️ Durable Handles Timeout
Durable V1 Timeout
📄️ Connection Failover and Recovery
You may setup a transparent failover and continuous availability in Fusion File Share in an active-passive mode using the following instruction. Fusion File Share stores connections and open handles (durable and persistent) in file system. Hence it is possible for clients to recover and reconnect connections seamlessly. Please also refer to section Continuous Availability (CA) for per-share configuration.
📄️ Logging
Log Destination
📄️ Audit Logging
Fusion File Share supports audit features.
📄️ Services Watchdog
Services Watchdog Timeout
📄️ Distributed File System
Fusion File Share can export DFS capability to clients at negotiation step. You can set the following parameter to ‘true’ if you want to have at least one share that presents in DFS tree structure. You also have set ‘dfs = true’ in the share configuration of the share that you want to be present in the DFS tree structure.
📄️ Compression
Tuxera Fusion File Share supports transparent compression. The ability to compress files inline dur ing transfer can significantly reduce both bandwidth and transfer time. You can expect and network bandwidth savings between 20–70% and transfer speed-ups between 30–300% depending on the data pattern.
📄️ Auxiliary Directory
You may specify the auxiliary directory where Fusion File Share server(s) keep runtime files.
📄️ Crypto Threads
This option controls the number of threads available for encrypting outgoing packets and decrypting incoming packets.
📄️ Change Notify
Change notifications are a feature of SMB server that allows clients to subscribe to notifications about changes in directory structure and the content of the files. This configuration option allows controlling the type of backend to use for enabling change notifications.
📄️ Continuous Availability
Default setting for continuous availability
📄️ Volume Shadow Copy
Default vss
📄️ Case Sensitivity
Default case sensitivity on shares
📄️ Access Based Share Enumeration
Controls whether a share exported by the SMB server will only be visible to users who have at least the access rights to read data (FILEREADDATA) when enumerating (listing) shares. The authorization policy which allow or deny access to a share is computed only using the access rights specified by the configuration option in section Share Permissions.
📄️ Remote Management via RPC
Support remote management of server resources and services via RPC clients
📄️ Apple Extensions
Controls whether the SMB server will enable Apple extensions to the SMB2/3 protocol for MacOS clients.