We have just finished setting up a test server for a client

MirrorSync now sits on one of their servers which is in a DMZ but has an outward facing DNS name and uses NAT to get the traffic through to FM Server (and MirrorSync, of course)

We have also setup MirrorSync to use separate internal and external IP addresses

From the server, we have the MirrorSync Client Config tool open and choose to Download database and create a link and the link has the internal IP address embedded in it as follows:

http://192.168.12.23/MirrorSync/dbDownload/a3d34edd-0805-49e4-929c-f5847931f893

This fails locally as the mobile client cannot see the internal IP address of the server

If I change the URL to use the DNS as in example: http://mobile.server.com/MirrorSync/dbDownload/a3d34edd-0805-49e4-929c-f5847931f893

Then the file is downloaded and I can launch and use it

Any ideas where we may have gone wrong during setup ?

Cheers

Harry

The version you have will use whatever address you enter into the browser when you launch MirrorSync as the host for the download links.

This version (2.40513) will use the external IP address for the download links.

http://s3-external-1.amazonaws.com/com.prosc.support.uploads/Outbound/360Works MirrorSync 2.40513.zip?AWSAccessKeyId=AKIAIDQUCQL7APZLJCDA&Expires=1434909294&Signature=ltG%2FeeT%2B3qT9%2B4u2n0GXEquTzic%3D

Does this version also contain the fix made for the image problem that we are having ?

Cheers

Harry

Edited May 23, 201510 yr by Harry Catharell

Yes