Network File System (SMB) Connection

Learn how to create a connection to a Network File System using SMB protocol.


Overview

The Network File System (SMB) connector uses SMB protocol to connect to network file shares so you can analyze, migrate, copy, and synchronize files. The connector is available in Linux environments but not in Microsoft Windows. However, it can access both Linux and Windows file shares. There are some limitations regarding the SMB and NFS versions it supports, which are listed below. 

Supported Protocols

All current SMB2/SMB3 protocols are supported, including 2.0.2, 2.1.0, 3.0.0, 3.0.2, 3.1.0, 3.1.1.

 

Unsupported Protocols

NFSv4, NFSv3, and NFSv2 protocols are not supported.

 

Unsupported Features

The following features are not supported:

  • Root-level connections are not supported.
  • Integrated authentication is not supported.
 

SMB Azure File Share Protocol Settings

When using the SMB file system protocol in Azure Files, the default profile is Maximum compatibility. DryvIQ recommends leaving the default profile when using the managed NFS connector. DryvIQ’s managed NFS connector does not support some custom SMB protocol settings. 

Azure Files Maximum Compatibility Profile

Creating a Connection

  1. Expand the Manage section in the left navigation menu.
  2. Click Connections.
  3. Click Add connection.
  4. Select Network File System (SMB) as the platform on the Add connection modal. (The SMB connection only displays in the Connections list on Linux environments. It will not be available on machines running Microsoft Windows. However, it can access both Linux and Windows file shares.)
  5. Enter the connection information. All red fields are required for this connection.
  6. Test the connection to ensure DryvIQ can connect using the information entered.
  7. Click Done.
Add Connection Modal for Network File Systen (SMB)

 

Field Description Required
Display as

Enter the display name for the connection. If you will be creating multiple connections, ensure the name readily identifies the connection. The name displays in the application, and you can use it to search for the connection and filter lists.

 

If you do not add a display name, the connection will automatically be assigned a default name. 

Optional
UNC Path

Enter the UNC path for the connector. The UNC path will be to a folder at least 1 level off the server's root, for example, \\<server name>\<folder on server>. Root-level connections are not supported.

 

You can also use the server IP address, for example, \\<ipaddress>\<folder on server>. 

Required
User Name Enter the user name for the administrator account. The account must have the authority to access the content you will process. Required
Password Enter the password for the administrator account. Required
Use Kerberos Authentication

By default, the SMB connector uses NTLM authentication.

 

Select No (or skip this field) if NTLM authentication is acceptable.

 

Select Yes if you prefer to use Kerberos as the authentication method. 

Optional

Features and Limitations

Platforms all have unique features and limitations. DryvIQ’s transfer engine manages these differences between platforms, allowing you to configure actions based on Job Policies and Behaviors. The information below is platform-specific. Use the Platform Comparison‍ tool to see how your integration platforms may interact regarding features and limitations.

Supported Features Unsupported Features Other Features/Limitations
Timestamp Preservation‍ 
(When used as the source connection)
Author/Owner Preservation‍   File Size Maximum‍: No maximum
Account Map‍  
(When used as the source connection)
File Lock Propagation‍   Path Length Maximum‍: 32,767
Group Map‍  
(When used as the source connection)
Mirror Lock Ownership‍   Restricted Types‍: None
Permission Preservation‍ 
(When used as the source connection)
User Impersonation‍   Segment Path Length‍: No maximum
  Tags Map‍   Invalid Characters‍: /
  Version Preservation‍   
  Metadata Map‍   

Last Accessed Date

DryvIQ processing affects the Last Accessed date for files, but DryvIQ restores the original Last Accessed date after reading the file to preserve this date. If the NFS account used to create the source connection has read-only permissions to the source files, DryvIQ cannot restore the Last Accessed date, so the date will be affected by DryvIQ processing. This behavior applies to content scans and migrations.

Permissions

Network File System supports assigning permissions to a specific folder (“This folder only”). DryvIQ does not support “This folder only” permissions when moving content from NFS to other destinations. DryvIQ will add permissions to the folder on the destination based on the platform rules.

Unix Users and Groups

DryvIQ's SMB connector does not support viewing Unix users and groups.