Harry Catharell Posted May 22, 2015 Posted May 22, 2015 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
Jesse Barnum Posted May 22, 2015 Posted May 22, 2015 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
Harry Catharell Posted May 23, 2015 Author Posted May 23, 2015 (edited) Does this version also contain the fix made for the image problem that we are having ? Cheers Harry Edited May 23, 2015 by Harry Catharell
Recommended Posts
This topic is 3473 days old. Please don't post here. Open a new topic instead.
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now