Web Server Problem

[TalentedFool]

Hi,

I have a web server sitting in a DMZ. It's got a public IP address of 81.31.193.20 and a private of 10.200.1.3 - I haven't had chance as of yet to get my ISP to update the DNS record for this to point at

http://www.site.com-

not a problem - least I don't think it is.

If I go into IE and type in 81.31.193.20 - it says it can't find the server yet inside my company I've updated our internal DNS to point at the machine and I can see it.
to test the outside bit, I've disconnected my network card and dialed up the internet - no joy!

ARGH! How do I get people on the outside to see the machine by just typing in the IP Address?

To let you know, there's a Cisco 1700 router sitting in front of the DMZ that has tcp port 80 open for traffic. I've done a show log and there's nothing being denied from my dial-up IP address.

What am I missing? I feel its something small!

Thanks for your help on a dark and raing Friday afternoon

Lee ~ Remember - Nothing is Fool Proof to a Talented Fool ~

 

[stoney66]

i have a couple basic questions... is there a fireall involved, and does the web server/router have a default route to get out to the internet.

 

[ChrisAC]

When you point your internal DNS at that machine, are you putting the name (

http://www.etc..)

in ie and having your DNS resolve it or are you using the IP address internally. The reason is that you can't always view a web page by IP address if it's hosted on a virtual server. Your browser makes a request to

http://www.yourdomain.com

so that the server knows which pages to serve.

For example, I know the IP address of my ISP's public web server and a couple of web pages hosted on there. If I type the IP address in my browser I get diddly as the server doesn't know which pages to serve.

This might not be related to your problem at all but it's something to bear in mind.

Also, are you logging tcp traffic on the router to se if the requests are being routed through it? You should also check your web server logs to see if the server's been "hit".

Finally, do a traceroute to your web server from the internet to make sure that your ISP is routing the correct range.

Chris.
**********************
Chris Andrew, CCNA, CCSA
chris@iproute.co.uk
**********************