Hi everybody:

I have a problem with some databases that can't be accessed by one
customer through the web.

Those databases were suscessfully published for a whole year - this
meaning can be accessed by this particular customer, until we need to
move to another office and had to change the port for web companion.
We were using port 80, but after moving it port was reserved for
router. So I changed the port to 591 and 8080 without suscess.

I made the approriate change in the hyperlink (xxx.xxx.xxx.xxx:591 or
8080) but the customer gets the usual error as when trying to acces a
non-existing web page.

I had tested to access the databases through web from other places
(not the customer), using port 591 or 8080 and it works - except for
this particular customer.

Our details is as follow:

- Databases hosted in a separate PC (Windows XP), using Filemaker
Server 5. This machine is only used for Filemaker hosting.
- A Mac runing Filemaker 5 and web companion activated to serve the
databases to web. This machine is used only to publish the databases
and generate automatics emails.

Before somebody would ask, we have completely sure that it's not
something with the 10 connections limits.

Any sugestion would be appreciated.
Gustavo Chirinos

"Gustavo Chirinos" <chirinog (AT) bellsouth (DOT) net> wrote

If they can be accessed by everyone else, then the problem is at the
customer's end.

DNS, badly configured machine, badly configured black list on their web
services, their ISP has blocked your FileMaker web server etc etc

Webko

"Tim 'Webko' Booth" <T.Booth (AT) isu (DOT) usyd.edu.au> wrote


I'm wondering if there is any way to find out exactly what's the
problem in the customer side. I can't understand why they can't access
the database under the new port number - they were just fine when the
port was 80.

Any test that can be done on their side - as apparently there is no
way no use the port 80 on ours?

Thanks
Gustavo Chirinos

"Gustavo Chirinos" <chirinog (AT) bellsouth (DOT) net> wrote

They almost certainly have a firewall somewhere in between that is not
allowing TCP/IP traffic on 'unusual' ports - they need to punch a hole in it
for Port 591.

It's either their tech staff or their ISP that need to do this.

Cheers

Webko