The following advice only applies if you run your own SiteRemote Server (3 and above) and you need to use port forwarding on the server side. This basically means that the address (IP or host name) you are using on the clients to reach the server is not the actual SiteRemote server itself.
Under the above circumstances you might notice that file synchronization (used for the File Manager and Digital Signage features) does not synchronize any content to the client. Should this be the case and the basic client server communication (registering the client on the SiteRemote server, client status updates etc.) is working, you can try to make a change to the SiteRemote server configuration file. The file is located under ..\PROVISIO\SiteRemote\Config and is named SiteRemoteServer.config. Before you edit the file you should stop the SiteRemote Server Windows service in the Service Management Console of Windows (services.msc) and make a backup of the original. Then open the file with Notepad or your preferred editor and look for the line:
<Torrent.config ClientPort="52138" />
This tag already includes the port used for file synchronization. You can add ClientIPAddress to that tag to force the client to contact the server under a specific IP, in this case the IP of the port forwarder in use. So after the change the line will look like this:
<Torrent.config ClientPort="52138" ClientIPAddress="18.104.22.168" />
Save the SiteRemoteServer.config file and start the SiteRemote Server Windows service again. The new information will be distributed to the clients on the next connection. Note that you may need to stop and restart running synchronizations to see the effect.