Hi there,
I am running a self-made content management system in my office, and having a problem with ScriptMaster plugin on Windows.
My solution utilizes ScriptMaster's "GetUrlAsText" function to fetch XML from our intranet system. It works on my MAC perfectly, but when it comes to WINDOWS, the plugin (360Works_ScriptMaster.fmx) always fails to establish network connection and shows time-out error.
I am wondering if our company's firewall is blocking communication. Does the plugin use any special ports other than 80? Any ideas???
I have tried to figure out what's wrong by trying these cases:
- On Showcase file (ScriptMaster.fp7) , GetUrlAsTest function fails to establish net connection. The plugin seems to be loaded correctly, and "basic example" on top of the modules list does work.
- Custom plugin generation of ScriptMaster Advanced also fails as showing network connection error, when used on Windows PCs in my office.
- The problem is reproduced on multiple Windows PCs in my office, with XP and Vista. No difference between Filemaker Pro 10 and 11 Advanced environment.
- Custom plugin ( Windows version which has produced on my Mac ) does not work also.
- IE, Firefox and other internet clients, including Filemaker's Web Viewer, works nicely on same machines.
- On a Windows PC in my home, the plugin does work. No problem.
- Using Sun Java 1.6.x. I checked firewall settings in Sun Java control panel, inputted same values as the browser but nothing changes.
- I've tried a freeware plugin which has similar networking function. It also stops at error 500.
FYI... currently Filemaker (master database) is running on Mac OS 10.6 Server and accessed by Windows PCs via IWP (browsers). Both Mac/Win machines in my office has Symantec installed. The mac plugin works well in this environment. However, IWP engine often become unstable and I want to switch to client-server system using FileMaker client applications.
I tried to use Filemaker's original GetObjectAttribute function instead, but having problem with getting content from Web Viewer because XML purser of IE browser engine - which is used in Web Viewer - generates dirty source. Any workaround ideas are welcomed.
Thanks.