You can only have static IP Address on a device that actually have a static place and network line. FileMaker Go is relying on WiFi/3G.
If you want to access a specific FileMaker Server and want the FMS to have a static IP address then you better host your solution on a computer that do not use DHCP. You can easily move your FMS license to FileMaker Cloud. There you will have a static IP address
Johan Hedman wrote:
You can easily move your FMS license to FileMaker Cloud. There you will have a static IP address
No you won't. AWS assigns a dynamic public IP address and DNS name. It will get reset when you shut down the instance.
Does anybody know how to keep the static IP addresses in filemaker go for accessing a server remotely?
I "pin" them but they do not stay!
Can you describe how you 'pin' it?
In Go (just like in Pro) you define a fav host and if you use the static IP of the remote host or its DNS name then it should stick.
I have a static IP address, 81.xxx.xxx.xxx, that is Port Forwarded with filemaker only to the server where we have numerous Filemaker Databases all doing different things for different people.
When those people in conference within our LAN away from their computers they have with them iPad or iPhone for referring to, for example, a contact database or a recipe database for nutritionals etc.
When they are in the field and away from the internal WiFi we rely on the 3G/4G network and, of course, when available, WiFi from whichever WiFi host is available.
We require the address in each Filemaker Go on each device to be set as 81.xxx.xxx.xxx/Data/filemakerfile.fmp12 which is in the Network File Path.
Once that has connected you can then go into Recent and "click" on the page with the tick [now] and it provides you with three icons one of which is a Pin which, when you have selected the file drops onto it and I assumed "sticks" it there .... but it doesn't!
1 of 1 people found this helpful
I would say that you should have 81.xxx.xxx.xxx/filemakerfile as your file in External Sources and exclude the folder Data
Another option is that you can create an "opener" database and send that to FileMaker Go. The "Opener" database is just a single FileMaker file with one script step which is open file( ... )
You can email that file and it's easy to save the file to FileMaker Go from the email.
Thanks Johan but the initial access is not a problem it works fine it is the problem of keeping the address for reuse and it appears that CarlSchwarz has the answer, which is what I had been thinking as the solution, so thanks CarlSchwarz that is the route I will use.
Many thanks all
It's important to note though that the address to a FM file from a FM client should NEVER contain actual folder or path names. That's not how it works. And if you enable network file access / OS-level sharing on those folders to 'make it work', if anyone can find / manipulate the FM files through Windows Explorer or Finder then deployment is faulty and your files are at risk of corruption.
Hi wimdecorte - just to be clear in my mind could you be so kind as to expand a little and provide an example please
The example was already given. To target a file directly on a server you can use a reference like this:
fmnet:/<server IP or DNS name>/the_file
Where exactly the 'the_file' FMP file is stored, in what folder on the server is irrelevant because you are just talking to FMS and FMS will give you access to the hosted file wherever it is stored.
I'm going brain dead!
Of course... Many thanks