I have a client that has a linux web server running apache. I can connect to if from outside with no problem. I am not able to connect to it internally. The domain is different from the internal domain. I can watch the firewall log and the NAT rule is running I can see the port forward rule working just the page is blank or I get connection timed out. I go to the internal IP address and get a blank page.

Mapping a DNS entry would be to say www.yourwebsite.com points/returns {the internal IP address} of the webserver.

Named sites allows Apache (or any webserver) to host a number of different websites while using only a single ip address. The server (Apache) tells the difference by what website the browser requests. Using http://192.168.1.15 doesn't provide Apache enough info to deliver the/any website.

I do have a DNS forwarder to the internal IP. I can access the site from outside the network. Once you are on the internal even if you use the web server IP in a browser its just blank....

This is a Linux server not sure what its running. The people that created it cannot remember any credential to access this server. I have shell access internally but I am waiting for some more information...

I do have a DNS forwarder to the internal IP. I can access the site from outside the network. Once you are on the internal even if you use the web server IP in a browser its just blank....

This sounds like (to me at least) a common problem related to virtual sites configuration. On an internal workstation, ping the site address (www.whateveritis.com) to see if you get the internal IP or the external ip. Report back what you find.

0

This discussion has been inactive for over a year.

You may get a better answer to your question by starting a new discussion.