Jump to content

SuperContainer only working on guest computers


This topic is 5323 days old. Please don't post here. Open a new topic instead.

Recommended Posts

I set up SuperContainer last week (standalone, running on a Mac using FileMaker Pro 10). I open the database (hosted on that Mac) with a PC computer, and SuperContainer is working fine on the PC (which has FM Pro Advanced 10).

However, today I can't get SuperContainer to work properly on the (host) Mac, though it is still working on the (guest) PC. The Mac error, which comes up in the web view box, just says, "Timed out". I don't get this error on the PC.

Any thoughts? I thought I'd solved my container issues when I found SC, and yet here's another snag...

Link to comment
Share on other sites

Are you using any sort of internet filtering software? It sounds like it is being blocked either by your browser or by some other software.

Try using the style=noapplet parameter and see if you can access it that way. If you can, it means that your issue is due to java trying to launch and being blocked.

Link to comment
Share on other sites

I tried the "noapplet" style, but to no avail. Here's where it gets odd:

Currently (with things not working on my host Mac), the web browser points to "http://name-of-computer.local:8020/SuperContainer/Files..." etc. This works for me to open on the guest PC, as I mentioned before, but doesn't work on the local Mac. However, if I change this to "http://localhost:8020/SuperContainer..." etc., it does work on the local Mac. Of course, then I can't open it on the PC. If I change it to "http://ipaddress:8020/..." it works on both computers. Unfortunately, I am trying quite hard to avoid using the ip address in formatting the web browser, since my ip address changes and my network administrator would rather not assign a static address.

Thoughts?

Link to comment
Share on other sites

J

The best thing would be to get the network administrator to reserver a specific IP address for the machine that runs SuperContainer server. It's possible that your machine is caching the IP address of name-of-computer.local and when the IP changes it stops working.

Please feel free to call or post further questions here.

Link to comment
Share on other sites

This topic is 5323 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.