Filemaker not appearing online

[bradford]

I have looked hard for answers to this but no luck---maybe y'all can help:

The FM5 file appears locally through FileMaker Open Remote. It appears by typing the local IP address in the browser but if I type the actual IP address (the one provided through checkip, the one I use to connect remotely through Timbuktu) I get nothing.

I have opened up Port 80 on my Mac OS X 10.2.6 iMac, but no luck. I have turned port-forwarding for port 80 on my Linksys router, but no luck.

Suggestions?

Thanks.

Brad

[Garry Claridge]

To access with FM Client you will need to have Port 591 open.

If you are trying to access via WebCompanion you will need to check which Port is configured in the WebCompanion Plug-in. Port 80 is used by Apache (Personal Web Sharing) if it is "on".

Good Luck.

Garry

[bradford]

Hmmm. I tried WebCompanion. Apache is off. Nothing for port 80 is on in FileSharing. Nothing is coming up in the browser. I am not sure where to go from here. I have configured the router to open 80 and now 591. I know this has worked in the past with Timbuktu. If I had Filemaker at home I'd try and tap into it there with the application as well as the browser.

Stuck. Should Personal Web Sharing be on? It's off right now and won't turn on.

[ernst]

comcomcom said:

Should Personal Web Sharing be on? It's off right now and won't turn on.

If you want to be able to contact Filemaker like you do with the 'Open remote' or the 'Host' button in the Open dialog, then you should open port 5003 on your Linksys router.

Regards,

Ernst.

[Garry Claridge]

Whoops! Yes Port 5003 is the one. (Port 591 is the registered FM WebCompanion port.)

Garry

p.s. You don't need Web Sharing on.

[Leb i Sol]

OT:

Garry :>

speaking of ports...and windowz this might ease out your load

http://www.freewareweb.com/cgi-bin/archive.cgi?screenshot=1&ID=1393

http://www.insecure.org/nmap/nmap_download.html *******

free

....move along nothing to see here

Good Luck!

[Steve T.]

OPEN (hosts) and OPEN REMOTE are examples of sharing db's among FileMaker users and clients. To share on the www, the Web Companion plug-in must be installed in the application and each db to be shared must be configured to be shared by Web Companion (all under Preferences Application/Document).

As Leb and Garry pointed out, port 80 (:80) is the default for web sharing but may conflict with other server software. On Mac OS X, if Apache is already using port 80, you must reconfigure either Apache or FileMaker to use another port since they both cannot use the same one. As Gary indicated, port 591 is FileMaker's recommended alternate web serving port if :80 is in use. URL's would look like... http://www.yoursite.com:591.

Instant Web Publishing will get you db published, but Custom Web Publishing is more popular with folks who can do a little web work (you have to create your own web pages).

Good Luck!

--ST

[bradford]

My gut feeling is there's an issue with the router. If I plug in the IP address of the local machine into the browser I get the FileMaker Web Companion webpage template. ALL GOOD. If I type in the actual IP address, the one that actually is the router, then I get nothing. This is not good. Because it's a cable modem shared by many computers there must be something I am missing, no?

FYI: Remotely, I can connect to the database using FileMaker, using Open Remote and typing in the actual IP address. If I use a browser, nothing. NOT GOOD. I opened all the ports everyone asked me to open and there's only Personal File Sharing on, nothing else.

Help!

[Steve T.]

Hmmm... I don't know if you can do that. A static IP address is best. A dynamic IP address will work for as long as you have it. Typing in a router IP because it's shared w/many users? Dumb hubs send all signals to each computer but I think a router does not do this so how will it know which computer is hosting FMP? I'm surprised OPEN REMOTE works, but maybe when you're sharing a file the host actively broadcasts that it is hosting whereas the web server does not. I dunno... just thinking out loud, I guess.

Good luck! --ST

[ernst]

Steve T. said:

I'm surprised OPEN REMOTE works, but maybe when you're sharing a file the host actively broadcasts that it is hosting whereas the web server does not.

That sounds like a reasonable explanation to me to.

So for protocols that do not broadcast their replies, the Linksys would have to be programmed to specifically forward traffic to a certain IP address, i.e. port 80 would have to be open AND forwarded to the IP address of the machine that is running the webservice.

And further the machine acting as server should NOT get it's IP address via DHCP from the linksys, but static.

Ernst.

[Leb i Sol]

regardless of your external IP (dynamically or staticly assigned by ISP) set your Internal IP to static (eg. 192.168.0.69) and will be able to test.access your server by http://192.168.0.69 or http://192.168.0.69:xxxx where "xxxx" is any port number of your choice. Next step (if u do have a static IP from ISP)i sopening your roter to the world (open/create new service to WAN http://192.168.0.69 on port 80)

note: If u have only 1 static IP and domain name in place mysite.com that is hosted at your office...behind that 1 IP...u WILL NOT be able to access it by http://www.my_domain.com but as mentioned (by LAN IP) since DNS will be pointing back to YOU - you whole office...this is where the router comes in and directs to appropriate machine on your network. However, if u walk down to internet caffee and type the domain_name.com (after it has been registered for a few days) u will get it.......there probably old news to you... <

All the best!