Web access crawling on non-default port, something lost in translation?
Posted on 2006-10-23
Wanted to ask you a question, we have a apache server that is a dev box we are using right now. We already had a webserver on another IP (.3) running on port 80. This is correctly mapped and everything is working great. The Apache server we are running (.6) we changed to port 81 and internally everything works great. I added this to our ACL and our static mappings, however access from the outside CRAWLS, on Firefox you can see on the bottom "connecting to 192.168.0.6" and it seems as if it is having a very hard time loading images. What do you guys think?
Update, something interesting, keeping in mind I am outside the firewall so I have to type www.domain.com:81 which is in the 24.73.166.x block. If I click on a link I am getting a "connection timed out" error saying the server at 192.168.0.6 is taking to long to respond, shouldn't this be my outside IP address, do I have a mapping backwards?