Network File System (SMB)

Network File System (SMB)

On This Page

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.

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.

NFSv4, NFSv3, and NFSv2 protocols are not supported.

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 DryvIQ NFS (SMB) connector. The DryvIQ NFS (SMB) connector does not support some custom SMB protocol settings.

Creating a Connection

The first step is to create the connection by providing the connection information required for DryvIQ to connect to the file share.

  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 NFS (SMB)

Field

Description

Required

Field

Description

Required

Display as

Enter the display name for the connection. If you need to create multiple connections, ensure the name readily identifies each connection. The name is displayed 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 and allows you to configure actions based on migration job policies and behaviors. The information below is platform-specific. Use the Platform Comparison tool to see how your platforms may interact regarding features and limitations. 

Supported Features

Unsupported Features

Other Features/Limitations

Supported Features

Unsupported Features

Other Features/Limitations

Timestamp preservation
(When used as the source connection)

Version preservation

File size maximum: No maximum

Account map
(When used as the source connection)

Author/Owner preservation

Path length maximum: 32,767

Group map
(When used as the source connection)

File lock propagation

Restricted types: none

Permission preservation
(When used as the source connection)

Mirror lock ownership

Segment path length: No maximum

 

User impersonation

Invalid characters: /

 

Metadata map

 

 

Tags 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.

DryvIQ Platform Version: 6.3
Release Date: October 10, 2025