Kenoli Posted March 13, 2004 Share Posted March 13, 2004 I have gone through the routine to publish Filemaker on the web with mixed results. Some people get on some don't. On one friend's computer, I am able to log onto the file on the his local computer using either http://LAN-IP:port or http://WAN-IP:port. On mine, this doesn't work. It says it can't find the server, though it finds the server fine when I use port 80. (I am using port 8081 for Filemaker). One friend is able to log onto my published Filemaker and also onto his locally published filemaker, while when I try to log onto his Filemaker remotely, his Filemaker goes into spinning disk mode and he has to force quit the software. This latter seems to mean that I am knocking on the door, but things are getting hung up somehow. Any ideas? I hate these inconsistent results. It doesn't leave much to hang onto. Are there any particular ports Filemaker likes or dislikes? I can log onto my own computer using this syntax http://LAN-IP:80 and when I try http://LAN-IP:8081 I get a server not found error. I've tried other ports with similar errors. My router is set up correctly to forward the right ports. Any Windows/MacIntosh issues I should know about? --Kenoli Version: v5.x Platform: Mac OS X Panther Link to comment Share on other sites More sharing options...
Kenoli Posted March 14, 2004 Author Share Posted March 14, 2004 It seems Safari 1.2 is the culprit. Se related post. --Kenoli Link to comment Share on other sites More sharing options...
Recommended Posts
This topic is 7366 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 accountSign in
Already have an account? Sign in here.
Sign In Now