Since the Admin Console traffic is not encrypted; I use a ssh tunnel.
Every time I go to http://127.0.0.1:16000 to start the link; it downloads
the admin_console_webstart.jnlp module again & then runs.
I assume I've missing a step somewhere that will provide a lasting startup link....
I hate to pull up a 4 year old thread, but this 403 issue with the admin console seems to have been around a long time and there are never any resolutions or fixes. This is clearly NOT a firewall issue. If it was, there would be no response from the server, but there is an instant 403. This indicates the traffic is fine, its some permissions issue on the server in the Filemaker configuration, be it their files or IIS setup. I have been unable to track down where this problem occurs, mostly due to the hidden and mysterious file structures used by the server software.
Admin console launches fine on the server, as well as workstations on some subnets. However, from outside subnets, or even our VPN system, it's 403. This indicates that there is some network based permissions issue at work since there is no authentication involved to cause a permissions failure. How this could be the case however is entirely unclear, but that's what the conditions point to.
If anyone has actually resolved this permissions configuration problem with the Admin Console, please please please detail the resolution for us!