File Share
File Share Server Data Connector
The File Share Server Data Connector enables Tricloud Nexus to integrate with traditional network file shares using the Samba Protocol (SMB), allowing Edge devices to read from or write to shared folders on Windows servers, NAS devices, or other compatible systems. This connector is ideal for automating file exchange with legacy applications, lab equipment, document archives, or enterprise IT systems - bridging OT and IT workflows securely at the Edge.
Note: This connector is commonly used for file-based integration jobs such as uploading production reports, retrieving recipe files, or exchanging batch documentation between the factory floor and central servers.
Key Features
Edge-Based Operation: Connects Edge devices directly to local or remote SMB/CIFS file shares, even if cloud connectivity is unavailable.
Flexible Compatibility: Supports modern SMB protocol versions (e.g., SMB 2.0) and a variety of authentication methods.
Domain Support: Can join Active Directory or workgroup-based shares as needed for enterprise security.
Direct Transport: Uses direct TCP/IP for efficient, secure file transfer.
Configuring the File Share Server Data Connector
1. Add a New Connector
Select the Area node where you want to configure file share integration.
Go to the Data connectors tab.
Click + New data connector, choose File Share Server, and enter a name (e.g.,
FileShareServer).
2. Configure Connection Settings
Name: Enter a descriptive name for your connector (e.g.,
FileShareServer).Server Address: IP address or DNS hostname of the file server (e.g.,
123.10.10.156).File Share Name: The name of the shared folder (e.g.,
SharedDocuments). You must enter a name as it appears on the network. Share names are generally case-insensitive. This is particularly true on Windows-based SMB servers.Domain: (Optional) Enter a valid domain (e.g.,
company.local) if required for authentication, otherwise leave blank for workgroup access.If you are connecting to a standalone server that is not part of a domain (it's in a workgroup), you typically do not need to specify the domain. In such cases, you would authenticate using local user accounts defined on the SMB server itself.
Non domain joined file share server (Workgroup) - Leave the domain input blank. Instead use the credentials of a locally created user account on the file share server to connect.
Domain joined server (Active Directory Domain Environment) - You must specify the name of the domain so the credentials used to connect can be verified by the AD domain. Example of domain: mycompany.com
3. Authentication
Username / Password: Credentials for accessing the file share (e.g.,
nexusclient).Protocol: Select the SMB protocol version (e.g.,
SMB 2.0). Match this to your server’s configuration for best compatibility and security:SMB 1.0 - Older protocol supported by the following operating systems: Windows XP Windows Server 2003
SMB 2.0 - Newver protocol supported by the following operating systems: Windows 7 Windows 8 Windows 10 Windows 11 Windows Server 2008 Windows Server 2008R2 Windows Server 2012 Windows Server 2016 Windows Server 2019 Windows Server 2022
Transport Type: Choose
Direct TCP IPfor most modern environments.
Example File Share Data Connector Configuration
Name
FileShareServer
Server Address
123.10.10.156
File Share Name
SharedDocuments
Domain
(leave blank for workgroup) or mycompany.com
Username
nexusclient
Password
●●●●●●●●
Protocol
SMB 2.0
Transport Type
Direct TCP IP
Best Practices
Use strong credentials and keep them updated for secure access.
Match protocol version (e.g., SMB 2.0) to your server’s configuration - older servers may require SMB 1.0 (not recommended due to security risks).
Specify the correct domain if your environment uses Active Directory; otherwise, use local or workgroup accounts.
Use clear connector names to simplify troubleshooting and management.
Validate access and file permissions with a test job before deploying in production.
Last updated
Was this helpful?