1
Recently I installed a library catalog software program on our server, which runs on Windows 2003. Our server does not have IIS installed and the library catalog software comes with Apache files. The install also installs Apache Tomcat and if the program installs correctly, then the administrator does not have to do anything with Apache Tomcat. The problem is that we can't get users outside of our network to successfully browse our catalog. Internally, when users point their browser to the server's IP address, the program works, and hence the developer does not provide tech support for our problem.
Environment: we have a static IP and have entered this address in the router. We have opened up the ports, forwarded them, and ensured that no firewall is blocking them, either on the router or on the server. The ISP has assured us that they are not blocking the ports.
Is there some kind of setting in Windows Server 2003 that we need to adjust to allow others to access our web server catalog? Users eventually receive the message that the request has timed out, which normally indicates that the server can't handle the request, however, within our network, everything works fine, and then the server is fulfilling similar requests.
