Access a Samba share from the MxCloud

Last update: Download PDF Edit

Using the Mendix Cloud and a VPN connection you will be able to use a Samba connection to pull or push files to a windows share. When doing this you need to use the static ip address in the connection string. The library could support the usage of a Server name, however that requires some extensive configuration to specify the DNS server location, DFS address, etc. It is far more efficient to use the IP Address.

Code example

When connecting to a samba share using a regular username, password and ip-address the code below with the NTLMFileHandler is sufficient. Based on the SMB configuration and the name of the FileDocument the FileHandler will connect to the Samba share and pull the document with the same file name. 

public ReadFileFromSMBDrive(SMBConfiguration SMBConfig, FileDocument DocumentParameter1)
    this.SMBConfig = SMBConfig;
    this.DocumentParameter1 = DocumentParameter1;

public Boolean executeAction() throws Exception

    NTLMFileHandler fileHandler = new NTLMFileHandler(getContext(), this.SMBConfig.getDomainName(), this.SMBConfig.getUsername(), this.SMBConfig.getPassword());
    fileHandler.getSingleFile(this.SMBConfig.getImportFolder(), this.DocumentParameter1.getName(getContext()), this.DocumentParameter1.getMendixObject(), this.DocumentParameter1.getDeleteAfterDownload());;

    return true;

Using a servername instead of ip-address

If you choose to connect to a server based on the server name instead of the ip-address, you will have to enable all the properties related to this option. See this page: Setting Name Resolution Properties That page describes the different WINS properties that need to be specified in order for the library to resolve the domain and the server.

Name Resolution Properties

The cloud edit library however requires an additional property override. The DFS property is not supposed to be enabled in the Mendix cloud since the Mendix cloud cannot resolve the DFS server by default. If you choose to enable the DFS you will need to make sure that the server will be able to resolve the DFS, based on domain name and DNS location.

jcifs.smb.client.dfs.disabledIf this property is true, domain based DFS referrals will be disabled. The default value is false, but the cloud edit version has a default value of True. This property can be important in non-domain environments where domain-based DFS referrals that normally run when JCIFS first tries to resolve a path would timeout causing a long startup delay (e.g. running JCIFS only on the local machine without a network like on a laptop).
jcifs.smb.client.dfs.ttlThe time in seconds that DFS topology information should be cached. The default value is 300 seconds (although the trusted domains list is cached for 10 timesjcifs.smb.client.dfs.ttl).
jcifs.smb.client.dfs.strictViewThis property controls how JCIFS behaves if it fails to enumerate DFS roots but succeeds to enumerate shares. By default this value is false to indicate that JCIFS should quitely return the list of shares even if the DFS root enumeration fails. If this value is set to true, an exception will be thrown if DFS information cannot be successfully retrieved (e.g. an SmbAuthException due to insufficient access).

The cloud does not allow the properties to be specified using the system properties. Therefore you will need to specify these through Java, before initializing any of the JCIFS classes you will need to specify the exact Config options. This can be done by using the following line of code:


Additional information describing all the properties can be found here:


Related content