I am also trying to open a database hosted on FMS. I have installed FMS on a VM in Windows Azure, and tested it with FMP installed on the same VM and was able to open the fmserver_sample file. However, i was not able to access it via internet. I have added endpoints to the VM, on TCP, to ports 5003, 16000, 16001, 5013, 16004, 50003 (followed what the fms userguide said on page 22), but still not able to access the database. Anyone encountered and overcome this problem? Please advise, thank you!
port 5003 is the only one you need. You need to make sure that the port is open on the Windows firewall. Not sure what "endopoints to the VM" means...
Yes, as Wim describe: Have port 5003 open in your FireWall and:
- Set up access from a real - external - IP number through your firewall, pointing to your internal number (NAT)
- Open your FileMaker Pro and write the path to your server or use favourrite (create your server by entering a favorite)
This should do it
Thanks wimdecorte and Carsten! However, I could not figure out where can I do the changes for the firewall on a virtual machine. I went to the Windows Firewall with Advanced Security and added new inbound rules to allow localport 5003, 16000, 16001. But still cannot access the hosted database. What else could be missing? I can sense that we're getting warmer already....
You may also have to open the firewall on the local virtual machine that is acting as the server.
But what we are referring to is the "real" firewall protecting you local network.
It is the unit that is between your internetconnection and your local network.
On the "inside" you will see IP numbers that does probably look somewhat like 192.168.x.x or 10.10.x.x or or something like that.
Have a look here: https://en.wikipedia.org/wiki/Private_network
Your network must have real fixed (externl) internet number (or more) like 18.104.22.168 ... this is the one you can use to access your network from the outside. The router then must be able to connect to external number to the internal number. You should ask your network administrator about this.
When you are in the open remote dialog, there is a "view" drop down box at the top, change this to "favorite hosts". Then click the "Add" button, this will popup a box that allows you to enter the IP address of the machine that is running FM Server (see carsten's post about a fixed external IP address ), and assign a name to that server (IE "My Server").
Once you have saved it, and assuming your Filemaker server is configured correctly, is hosting a file, and is on a network that allows port 5003 incoming to connect to your server, then you should either receive a login prompt, or be able to view the "available files"
Once here, choose the available file you want to open from the host.
After you have opened the file once, it will be available under your "open recent" file menu. And using the above, will also store that server address for opening future files from that server.
http://www.ipchicken.com on your server will give you your "front-facing" external IP address.
If you can't reach your filemaker server by trying to connect to this IP address, then chances are there is something in your network setup your server is on that is prohibiting port 5003 to get through to your server.
Your router settings will usually allow you to use NAT (google NAT to find out more) to force all incoming port 5003 traffic connections to go to a certain machine ID or internal IP address. This is how I normally route incoming traffic in the right direction.
Thanks Carsten! I thought that the ip address shown on FMS was the external ip address, but since it is 10.xx.xx.xx as you have mentioned they are internal address, I found that there was an external address that I did not used. And with this change, I was able to connect to my FMS databases!
Your information was really helpful! Thanks very much for the sharing!
Thanks Mike! I have followed your advise, and assigned a name to my server under favorite host, and now it looked really neat! We are using 2 ipads to monitor our students' attendence and progress recording, and keeping this naming of favorite host consistent across devices will remove the confusion later on when we use different servers.
Thanks very much for the tip!