Dear Steve,
You may be correct re port 5003 and FM Pro Clients, but my ISP
apparently blocks port *), so I have to use some other port anyway. If
I can't use port 80, does it matter what other port I forward?
Jay
On Jun 20, 2008, at 11:54 AM, Steve Cassidy wrote:
Hi Jay
I'm not sure if I can help at all; maybe I'll just confuse things
some more... But that port 5003 looks fishy to me.
As far as I'm aware, 5003 is the port (or one of them) that
Filemaker uses for host to client communications -- so it would be
relevant if you were trying to connect to your server using the
Filemaker client.
In your case, if I understand correctly, you are trying to view
pages served up by IWP, which I would think -- unless you configure
things otherwise -- are on port 80.
1. Set up Mac networking manually for a static address eg
192.168.1.50
2. Disable the firewall on the router by unchecking "block
anonymous internet requests" and set up port forwarding for port
5003, the port that Filemaker listens on. (Portforward.com was
invaluable in walking me through this.)
So I think you need to forward port 80 to your Filemaker server, not
5003. Obviously, this will only work if port 80 is not already being
forwarded to another web server...
3. Open a dyndns account at dyndns.com and register for two host
names, a visitor host and a destination host. This allows
redirection to the 5003 port of your computer. You need to webhop
from the visitor URL to the destination URL and then assign your
external IP address to the destination URL. (dyndns.com has good
tutorials on how to do all this.)
I have no idea what this is all about. When I used no-ip, which is a
similar service, I simply had to set up the domain forwarding. As
far as I'm concerned that's it; there's nothing else for the domain
forwarding service to do.
4. Download and configure the update client from dyndns.com. You
need this because the cable company will change your external IP
address and the update client keeps dyndns.com informed.
5. I could not initially connect with my Filemaker file using the
Visitor or Destination Host, or with the external IP address. It
turns out that this was a loopback error and was fixed by port
forwarding port 80 on my router. This was the tricky part that
stymied me for two days.
6. But even after all this, I can't access from outside.
I have no idea what loopback is. But this port 80 is, I think, the
core of your problem. You need to forward port 80 from your router
to your Filemaker server.
Steve
Jay Erlebacher
[EMAIL PROTECTED]
201 894-8846 home
201 569-4901 office
201 906-1290 cell
