- 4 minutes to read

Release Notes
Prerequisites for the File and FTP Monitoring Agent

This page describes the prerequisites to successfully install and run the Nodinite File Monitoring Agent to achieve MFT Monitoring.

graph LR subgraph "Nodinite Instance" roNI(fal:fa-folder File and FTP Monitoring agent) --- roMonitor[fal:fa-monitor-waveform Monitoring] end subgraph "Windows/Linux" roMonitor --- roSMB(fal:fa-folders Folders - SMB) roMonitor --- roNFS(fal:fa-folders Folders - NFS) end subgraph "SFTP" roMonitor --- roSFTP(fal:fa-file-certificate Folders) end subgraph "FTP/FTPS" roMonitor --- roFTP(fal:fa-file-export Folders) end

Instances of this agent can be installed on-premise using TCP/IP for local network access and/or in the cloud/off-site using Service Bus Relaying (see also the external link for additional information MicrosoftServiceBusRelayingLink).

We recommend that you keep this agent close to the Nodinite Core Services. This documentation covers local network setup (usually on the Nodinite application server)

Verified Topic
Software Requirements
What Windows User Rights does the File and FTP Monitoring agent require?
What Firewall settings are required for the File and FTP Monitoring agent?

Software Requirements

Product
Windows Server Windows 2022
Windows 2019
Windows 2016
Windows 2012 R2
Windows 2012
.NET Framework .NET Framework 4.8 or later New 6.0
Our recommendation is .NET Framework 4.8.1 or later

Versions 6.0 and later make use of the .NET Framework 4.8 or later.
Versions 5.4 and subsequently make use of the .NET Framework 4.6.2 or later.
Versions before 5.4 make use of the .NET Framework 4.5.2 or later.

What Windows User Rights does the File and FTP Monitoring agent require?

The agent is installed as a Windows Service usually on the Nodinite application server. Virtual machines are supported.

For each Folder being monitored you may need to provide alternate credentials, review the Configuration user guide for additional details.

least privileges (basic usage)

What Firewall settings are required for the File and FTP Monitoring agent?

The File Monitoring Agent has both inbound and outbound communication:

  1. Between the Monitoring Service and the File Monitoring Agent
  2. Between the File Monitoring Agent and any of the following file based services
    • SMB Services (Typically Windows file shares)
    • NFS Services (Typically Linux file shares)
    • FTP/FTPS
    • SFTP
graph LR subgraph "Nodinite Instance" roMonitoringService(fal:fa-watch-fitness Monitoring Service) roNI(fal:fa-folder File and FTP Monitoring agent) roMonitoringService --> |"8000 (default)"| roNI roNI --> |"443 (Service Bus Relay)"| roMonitoringService end subgraph "Windows/Linux" roNI --- | 135-139, 445| roSMB(fal:fa-folders Folders - SMB) roNI --- | 111, 665-x, ...| roNFS(fal:fa-folders Folders - NFS) end subgraph "SFTP" roNI --- |20,22|roSFTP(fal:fa-folder-tree Folders) end subgraph "FTP/FTPS" roNI --- |21|roFTP(fal:fa-folder-tree Folders) end

NOTE: The exact ports in use, may vary with your policies and current configuration/reality

1. Between the Monitoring Service and the File Folder Monitoring agent

The following ports must be allowed on the Windows server where the agent is installed and running :

Port Name Inbound Outbound TCP UDP Comment
53 DNS The Agent needs to know where your other servers/services are (can sometimes optionally be solved using entries in the local hosts file)

And further with 'Option 1' or 'Option 2' as documented next:

Option 1 (Local network)

Port Name Inbound Outbound TCP UDP Comment
8000 RPC Communication is initiated by the Monitoring Service

Option 2 (Cloud/Hybrid)

Use Service Bus Relayed connections when Nodinite and the agent are on totally different networks.

Nodinite uses the same principle technique as the On-Premise data gateway, see 'Adjust communication settings for the on-premises data gateway' user guide.

Port Name Inbound Outbound TCP UDP Comment
443 HTTPS Secure outbound traffic
5671, 5672 Secure AMQP
9350 - 9354 Net.TCP

2. Between the File Monitoring Agent and file based services

Additional firewall requirements may exist depending on the usage of the Samba protocol, FTP, FTPS, SFTP, Certificates, NTLM, Kerberos, Sun RPC.

SMB

Port Name Inbound Outbound TCP UDP Comment
53 DNS The Agent needs to know where your other servers/services are (can sometimes optionally be solved with user-defined entries in the hosts file in each Windows server instance), review the following 'Microsoft' user guide
135-139 SMB Microsoft file sharing SMB
445 SMB Direct-hosted SMB traffic

FTP/FTPS

Port Name Inbound Outbound TCP UDP Comment
21 FTP/FTPS Default

SFTP

Port Name Inbound Outbound TCP UDP Comment
22 SFTP (SSH) Default secure port
20 SFTP (SSH) Default for download

NFS

Port Name Inbound Outbound TCP UDP Comment
111
665-1024 when using privileged ports option
1039
1047
1048
2049

Next Step

Install File Monitoring Agent

Add or manage Monitoring Agent
Monitoring
Administration