most likely you're having trouble connecting to your FMS because your FMS is behind a NAT. if you're running at Amazon AWS then you're definitely behind a NAT. FMS must be configured to know about its own translation in order for clients behind symmetric NATs to be able to connect. this is because the initial connection from the client to FMS is to the "fmsedge", which redirects to an "fms core" process. the edge process needs to know the translated address of the core in order to get the client (when behind a symmetric NAT or a port-restricted cone NAT or common firewalls) connected.
you configure the translation in the RTMFP section of the Adaptor.xml FMS config file.
Thanks for your answer.
I have read the RTMFP section in my Adapter.xml file forward and backward, but I have no clue how to configure the translation you refer to.
Two specs that comes close are:
Please hold my hand, Thanks!
it is the HostPortList section. the comments in that section should explain it to you. in particular, look at the example at the end using the "public" attribute. that's exactly your situation (where the "public" address is different than the local address).
if your public address is 192.0.2.5, and the ports are mapped directly (so public port 19350 is mapped to local port 19350), then the entry might look like
if you need more help than that, you should probably ask in the FMS forums.
Thanks Michael, I see what you mean.
My service provider has confirmed that the server is not NATted, but servers have public ip addresses.
Nevertheless, the servers do have MULTIPLE public addresses:
Public rtmfp-core addresses for listener _defaultRoot_ are: 127.0.0.1:19352;188.8.131.52:19352;184.108.40.206:19352;220.127.116.11:19352
After the change that you suggested it is now:
Public rtmfp-core addresses for listener _defaultRoot_ are: 18.104.22.168:19350
The address used by clients for the FMS server is 22.214.171.124.
Can you comment on this?
Meanwhile waiting for my client to confirm whether it does now work, or not.