192.168.x.x is still a local IP and it would not work outside of your LAN (local network). You would have to be on the same router to be able to access it.
What you need to access that server from OUTSIDE of your network is a static IP address, and port forwarding in your router.
The static IP allows anyone outside of your network to connect to the network your server is hosted on.
The port forwarding allows your router to send that incoming internet traffic (port 80) to your filemaker server for resolution.
Usually a static IP is set up by your internet service provider. There are some services like DynDNS that allow for static-ip behavior without upgrading your internet connection.
Port forwarding should be setup by an experienced network technician, although youtube has thousands of videos for doing it.
There are a number of security concerns you should think about, including the use of SSL, firewalls and file encryption, if you want to open up your filemaker server to the outside world.
192.168.x.x is a local IP address not a remote address.
Google what's my IP to find out your remote IP address and test that IP address.
If that doesn't work then you haven't set up port forwarding to port 80 (and also add port 443 for https secure SSL), so webdirect can use port 80 and port 443 and you should port forward both of them incase you turn on SSL in server settings.
yeah, port 443 comes with using SSL and upgrading your security. Was just trying to explain the fundamentals without getting into TOO much detail
I like the network technician suggestion especially if there is say a double router setting. Networks can get so complicated.
That, and a network tech will have other suggestions relating to security as well. Casually opening your router ports to the outside world is a terrible idea if you don't consider the security consequences.
Yes, we have an external static IP (203.45.x.x) and port forwarding is turned on to point to the local FileMaker Server IP 192.168.x.x but that doesn't work.
To test and ensure WebDirect is working I tried those URLs internally to take the port forwarding out of the equation for the moment.
To me this isn't a port forwarding issue, it seems more like a internal network issue.
when you say "it does not work", what does the page actually display?
It seems likely that you are on a different subnet in your local network.
Is the local computer you are accessing it from also on 192.168.2.xxx ?? The fact that you have a .2 network makes me think that you have a complicated setup (default for most DHCP servers is 192.168.0. )
Also the external access problem makes me think that it's a firewall issue or that the router that you did the port forwarding on doesn't have access to the server.