Network Share (SMB)
Read and write files on a Windows network share or a NAS over SMB 2 and 3, signing in with a user name and password, with the same folder globbing, Bookmark and per-file fan-out the other file connectors have.
Settings
What the connection form asks for. Every connection has a Staging side, which it needs, and an optional Production side with values of its own; both ask for the same settings.
| Server | The file server's name or address, like fileserver or 10.0.0.12. Trinium must be able to reach it on port 445. |
| Port | Blank uses 445. |
| Share | The share's name, the part right after the server: for \\fileserver\exports it is exports. |
| Root folder | Optional folder inside the share that every path on a node is relative to, like daily/incoming. Blank uses the share itself. |
| User name | |
| Domain | The Windows domain of the account, like CORP. Leave it blank for an account that belongs to the server itself. |
| Password | Stored encrypted, and never shown again after you save it. |
Testing the connection
Test signs in, opens the share and reads the root folder. It only reads, never writes to the share, and gives up after 10 seconds. A wrong password, a share that does not exist and a root folder that is not there all fail by name. An account that signs in but may not list the share's top folder still passes, because a real sign-in is already proven by then.
Good to know
- Trinium signs in with a user name and password, the way a computer that is not joined to the domain connects to a share. Fill in Domain for a domain account and leave it blank for an account that belongs to the file server itself.
- Every request is signed. A share that requires encryption refuses Trinium for now, and Test names that as a possible cause.
- It speaks SMB 2 and 3 on port 445, and is tested against a Windows share and against Samba, the software most NAS boxes run.
- A path copied from File Explorer (
\\fileserver\finance\exports) works in a node when it names the connection's own server and share. - A server that goes silent cannot hold a run for ever: Trinium gives up on a request that gets no answer for a minute and fails the run by name.
- A Live run reading from a share waits for each file to stop changing before it reads it, and skips by name one that is still being copied.
- Each file is written under a temporary name and renamed to its real name once it has fully arrived, so nobody opens a half-written file.
Nodes that use it
Copy, move or delete the files an input, List Files or File from URL hands it through its Files anchor, before the data is processed or after the run succeeds or fails.
List the files in a folder as rows, with each one's path, name, size and modified time, without reading any of them.
Write the pipeline's output to a Windows network share or a NAS over SMB with a templated path (dates, run id) and a write mode.
Read a single file or a whole folder from a Windows network share or a NAS over SMB. A Bookmark can read only the files no successful run has read.