Skip to main content
Feedback

File Share

File Share endpoints contain metadata to configure the MFT Node, which is a managed file transfer agent that will be installed on your server. Configurations define file flows inside your local area network (LAN) or between your LAN and MFT’s cloud. These configurations may also require file processing such as compression, renaming, encryption, and so on.

This resource uses the SMB/CIFS protocol or a native path to a network mount to connect to other file systems, including Windows, Linux, or Unix.

important

You must set up an MFT Node before adding your first File Share endpoint.

To create a File Share endpoint:

  1. Click Organizations.
  2. Select an organization.
  3. Click Endpoints.
  4. Click the Add Endpoint button.
  5. In the Endpoint Name field, enter the name.
  6. Select File Share protocol from the Type drop-down.
  7. Select the MFT node from the Associate with Thru Node drop-down.
  8. Enter a File Share Path.
  9. Enter a Domain if needed.
  10. Enter your Username.
  11. Enter your Password.
  12. Click Save.
caution

A Node installed on a Linux operating system cannot access a Windows File Share directly. To enable access, the file share must be either soft-mounted or hard-mounted in advance. Improper setup of the file share will prevent your Node application running on Linux from accessing necessary files and may cause errors.

Username/Domain formatting support

MFT uses the Net Use command to connect to a shared resource.

MFT calls the Directory.GetFileSystemEntries() on the path in the config to decide whether it can connect.

First, MFT calls this without net use. If it succeeds, the connection is considered successful regardless of domain, username, or password.

If it fails, MFT formats the net use command like this if there is an entry in the domain field:

/C net use \"{_networkPath}\" /user:\"{_domain}\\{_username}\" \"{_password}\" /persistent:Yes

or like this if there is nothing in the domain field:

/C net use \"{_networkPath}\" /user:\"{_username}\" \"{_password}\" /persistent:Yes

If this fails, an .\\ is added to the command:

/C net use \"{_networkPath}\" /user:\".\\{_username}\" \"{_password}\" /persistent:Yes

Finally, if this fails, MFT makes one more attempt with 'local' before considering it a failure:

/C net use \"{_networkPath}\" /user:\"local\\{_username}\" \"{_password}\" /persistent:Yes

Syntax

net use [{<DeviceName> | *}] [\\<ComputerName>\<ShareName>[\<volume>]] [{<Password> | *}]] [/user:[<DomainName>\]<UserName] >[/user:[<DottedDomainName>\]<UserName>] [/user: [<UserName@DottedDomainName>] [/savecred] [/smartcard] [{/delete | /persistent:{yes | no}}]
net use [<DeviceName> [/home[{<Password> | *}] [/delete:{yes | no}]]
net use [/persistent:{yes | no}]
On this Page