> This is a Filemaker protocol problem, and it can't be fixed without fixing
> Filemaker, unless you've got a firewall in front of the client as well. If
> you do, make the client firewall redirect all stuff destined for the
> internal address to the external address, and let the server firewall
> redirect back again.
>
> And e-mail the Filemaker people and tell them precisely how stupid they are
> for writing an application-level protocol which relies on knowing the
> address (and hence the addressing scheme) of the underlying transport layer
> protocol.
>
> Stupidity is forever.
Thanks, I was afraid that was the case.... I'll have to look at an external
ip for the filemaker (or the filemaker might fix their product?).
Kind regards,
Ray G.
P.S. Sorry for the looooong sig on the original post - stupidity IS forever.
-----------------------------------------------------------
When Apple/Mac Networks HAVE to work!
The software said Windows 98 or better, so I bought a Mac!
--
--
SLUG - Sydney Linux User's Group - http://slug.org.au/
More Info: http://lists.slug.org.au/listinfo/slug
