I'm not 100% certain, but based on your description, it sounds like you don't have a DNS entry for "IPpublic". Did you reserve a domain name?
You might want to forward TCP traffic coming in on port 80 to that same address (192.168.1.5).
192.x.x.x is an INTERNAL IP address. you need to see if you have an EXTERNAL IP address (static IP).
Based on his post, I think he is using a public IP to connect, and port forwarding to route the traffic to the internal address.
He's forwarding traffic coming in over port 5003, which should allow remote FileMaker Pro and Go users to connect. However, it doesn't sound like he's doing the same for the requests on port 80.
Thank's a lot for your answer.
My problem is that the port 80 is already use by other server 192.168.1.5.
Is it possible use the port 80 also for the IP 192.168.1.4 (server Filemaker)? If yes like?
Or is it possible to change the port number (from 80 to 81 for example) in the configuration of filemaker server 13 (webdirect)?
"Is it possible use the port 80 also for the IP 192.168.1.4 (server Filemaker)? If yes like?"
You might try this:
• Setup a forwarding rule using another external port (one that isn't already being used and is safe to use, such as 65500) to 192.168.1.4:80.
• If necessary, open up any firewall(s) that you have in place so that they allow traffic over that port.
• Then change your connection string in the external Web app to reflect the port that you've selected. It would end up looking something like this: IPpublic(static):65500/FMI/WEBD
That should work. internally you would still be able to hit the database using 192.168.1.4 on port 80. However, externally you would be hitting it over the public IP and the port that you chose.