Web Server Behind a Firewall Behind a Firewall Webmills <james[ at ]instantecommerce.co.uk> 19.06.2007 10:56:00 Hi, I have an obscure problem. I hope that this is the correct newsgroup for this item. Apologies if it is not. My problem is this... We sit behind a corporate firewall. We have a fixed IP address which forwards to an internal IP address of 192.168.102.11 with no port restrictions. Because of this, I have added our own firewall / router at 192.168.102.11. Behind this sits our web server. The firewall is set up to use NAT, so forwards relevant ports to our web server on 192.168.1.10. If I try to see a website hosted on our server from outside of the building (i.e. outside of the corporate firewall) using a domain name then it works as required. I also need to be able to see websites hosted on the server from my desk machine which also has a corporate IP address (192.168.102.25 say). If I try to connect using a domain name then this fails. It seems to be unable to find the route to the server. I would appreciate any help with this problem. Thanks James

Re: Web Server Behind a Firewall Behind a Firewall "Steven L Umbach" <n9rou[ at ]n0-spam-for-me-comcast.net> 19.06.2007 23:07:56 This is really more of a DNS question. Try using the IP of the internal router instead as in http://192.168.102.11 from your computer to see if that works. Steve "Webmills" <james[ at ]instantecommerce.co.uk> wrote in message news:1182250560.247467.206720[ at ]u2g2000hsc.googlegroups.com... [Quoted Text] > Hi, I have an obscure problem. I hope that this is the correct > newsgroup for this item. Apologies if it is not. My problem is this... > > We sit behind a corporate firewall. We have a fixed IP address which > forwards to an internal IP address of 192.168.102.11 with no port > restrictions. > > Because of this, I have added our own firewall / router at > 192.168.102.11. Behind this sits our web server. The firewall is set > up to use NAT, so forwards relevant ports to our web server on > 192.168.1.10. > > If I try to see a website hosted on our server from outside of the > building (i.e. outside of the corporate firewall) using a domain name > then it works as required. > > I also need to be able to see websites hosted on the server from my > desk machine which also has a corporate IP address (192.168.102.25 > say). If I try to connect using a domain name then this fails. It > seems to be unable to find the route to the server. > > I would appreciate any help with this problem. > > Thanks > > James >

Re: Web Server Behind a Firewall Behind a Firewall Webmills <james[ at ]instantecommerce.co.uk> 20.06.2007 09:19:24 Thanks for the reply. The situation is this... If I attempt to access our web server remotely (i.e. from outside of the building) using the external IP address, then pages are served correctly. If I attempt to access our web server locally (i.e. from my desk within the building) using the internal IP address (e.g. 192.168.102.10), then pages are served correctly. However ... If I attempt to access our web server locally (i.e. from my desk), but use the external IP address, then pages are not served. This becomes a real and vital issue because the web server hosts a multiple number of sites that we need to access locally by domain name. I understand that this can be solved by adding a line to the routing table of the corporate Cisco router. James

Re: Web Server Behind a Firewall Behind a Firewall "Steven L Umbach" <n9rou[ at ]n0-spam-for-me-comcast.net> 21.06.2007 01:04:10 Hmm. What you also could try is to create an entry in your hosts file on your computer for the internal IP address of 192.168.102.10 for each website you need to access. The links below explains more on how to do that. Be sure to save the hosts file with no extension as it currently is. Steve http://support.microsoft.com/kb/228760/ http://www.bleepingcomputer.com/tutorials/tutorial51.html "Webmills" <james[ at ]instantecommerce.co.uk> wrote in message news:1182331164.876965.38730[ at ]q69g2000hsb.googlegroups.com... [Quoted Text] > Thanks for the reply. The situation is this... > > If I attempt to access our web server remotely (i.e. from outside of > the building) using the external IP address, then pages are served > correctly. > > If I attempt to access our web server locally (i.e. from my desk > within the building) using the internal IP address (e.g. > 192.168.102.10), then pages are served correctly. > > However ... If I attempt to access our web server locally (i.e. from my > desk), but use the external IP address, then pages are not served. > This becomes a real and vital issue because the web server hosts a > multiple number of sites that we need to access locally by domain > name. > > I understand that this can be solved by adding a line to the routing > table of the corporate Cisco router. > > James >