We have WIN2003/ IIS 6.0 webserver hosting multiple websites.

These sites are setup on single IP address using host-headers.
Everything works fine and any of these sites can be browsed from
workstations connected to Internet, however I can not browse these
websites from the WebServer itself. Request timesout with DNS Error.

Even trying to ping WebServer from the webserver itself fails!

Any ideas on this behaviour?

Many Thanks

Re: IIS Help by Kristofer

Kristofer
Tue Dec 13 13:17:58 CST 2005

Hello,

It sounds like a DNS resolution issue. Perhaps the webserver is using a
different DNS server compared to your workstations. Nothing indicates that
it is an IIS problem since even ping fail.


--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info


CodeFun wrote:

>We have WIN2003/ IIS 6.0 webserver hosting multiple websites.
>
>These sites are setup on single IP address using host-headers.
>Everything works fine and any of these sites can be browsed from
>workstations connected to Internet, however I can not browse these
>websites from the WebServer itself. Request timesout with DNS Error.
>
>Even trying to ping WebServer from the webserver itself fails!
>
>Any ideas on this behaviour?
>
>Many Thanks

Re: IIS Help by CodeFun

CodeFun
Tue Dec 13 14:21:40 CST 2005

Only thing I cannot understand is why the webserver which is hosting
the websites can not browse those website.

If I goto Internet Information Services, right click on website and say
browse, it can-not browse to the webpages. These are only static HTML
pages, nothing fancy at all.

Webserver can ping the internal IP address 192.0*** , it can also ping
127.0.0.1. But it cannot ping the external IP address 83.**** that is
exposed to Internet. How wierd can it get!

Any help would be highly appreciated.


Re: IIS Help by Kristofer

Kristofer
Tue Dec 13 14:48:51 CST 2005

So if ping to the IP fails (after reading your other post i thought you
pinged the name and not IP), then it is a networking issue. This has
nothing to do with IIS.

It is not weird at all that you cannot ping the external IP from inside.
If a NAT router for example is assigned this IP, and this device do not
support loopback, you will not be able to ping the external IP.

--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info


CodeFun wrote:

>Only thing I cannot understand is why the webserver which is hosting
>the websites can not browse those website.
>
>If I goto Internet Information Services, right click on website and say
>browse, it can-not browse to the webpages. These are only static HTML
>pages, nothing fancy at all.
>
>Webserver can ping the internal IP address 192.0*** , it can also ping
>127.0.0.1. But it cannot ping the external IP address 83.**** that is
>exposed to Internet. How wierd can it get!
>
>Any help would be highly appreciated.

Re: IIS Help by CodeFun

CodeFun
Tue Dec 13 15:05:10 CST 2005

Many Thanks Kristofer,

Reason I associated this issue with IIS is when I tried to browse the
website on webserver, in the status bar message comes "connecting to
83.*.*.*" and then the DNS error. So if the loopback is enabled on NAT
router would that resolve the IIS issue.

Cheers,


Re: IIS Help by CodeFun

CodeFun
Wed Dec 14 02:07:47 CST 2005

I made adjustments to the HOST file to include the website that server
is hosting. After doing this everything is working as expected. Many
Thanks