we are developing asp.net web application with form authentication in IIS 6 - Windows server 2003.
the application is working fine.
but if we call any .html extension we are getting the following errors,
Diagnose Connection Problems
Internet Explorer cannot display the webpage
What you can try:
Diagnose Connection Problems
Internet Explorer cannot display the webpage
This problem can be caused by a variety of issues, including:
Internet connectivity has been lost.
The website is temporarily unavailable.
The Domain Name Server (DNS) is not reachable.
The Domain Name Server (DNS) does not have a listing for the website's domain.
There might be a typing error in the address.
If this is an HTTPS (secure) address, click Tools, click Internet Options, click Advanced, and check to be sure the SSL and TLS protocols are enabled under the security section.
For offline users
You can still view subscribed feeds and some recently viewed webpages.
To view subscribed feeds
Click the Favorites Center button , click Feeds, and then click the feed you want to view.
To view recently visited webpages (might not work on all pages)
Click Tools , and then click Work Offline.
Click the Favorites Center button , click History, and then click the page you want to view.
This problem can be caused by a variety of issues, including:
Internet connectivity has been lost.
The website is temporarily unavailable.
The Domain Name Server (DNS) is not reachable.
The Domain Name Server (DNS) does not have a listing for the website's domain.
There might be a typing error in the address.
If this is an HTTPS (secure) address, click Tools, click Internet Options, click Advanced, and check to be sure the SSL and TLS protocols are enabled under the security section.
For offline users
You can still view subscribed feeds and some recently viewed webpages.
To view subscribed feeds
Click the Favorites Center button , click Feeds, and then click the feed you want to view.
To view recently visited webpages (might not work on all pages)
Click Tools , and then click Work Offline.
Click the Favorites Center button , click History, and then click the page you want to view.
This problem can be caused by a variety of issues, including:
Internet connectivity has been lost.
The website is temporarily unavailable.
The Domain Name Server (DNS) is not reachable.
The Domain Name Server (DNS) does not have a listing for the website's domain.
There might be a typing error in the address.
If this is an HTTPS (secure) address, click Tools, click Internet Options, click Advanced, and check to be sure the SSL and TLS protocols are enabled under the security section.
For offline users
You can still view subscribed feeds and some recently viewed webpages.
To view subscribed feeds
Click the Favorites Center button , click Feeds, and then click the feed you want to view.
To view recently visited webpages (might not work on all pages)
Click Tools , and then click Work Offline.
Click the Favorites Center button , click History, and then click the page you want to view.
I don't really trust Internet Explorer when it comes to troubleshooting, so the first thing i would do is use WFetch, send a request for a .html-file and see what the response is.
You may also find useful information in the IIS logfile (assuming the request got to IIS). Please see if you have any requests for .html-files logged, and if so, post the entries here so we can have a look at it.
As a side not, i have noticed that this happens in Internet Explorer (later version) due to the html (strange, but it seems to happen, i have never really understand why). Have you tried to use Firefox or any other browser? It does not solve your problem,
but it tells us what is wrong. WFetch should also tell us if the HTML is returned to the client, and if, we can rule out IIS and instead focus on a client side issue.
Hope this help and that we can assist you further if you need more help to troublshoot this.
Yes, let's see if the IIS log file has anything for this request. The error message is saying that IE can't find the web server (which is strange because it can find the web server for your ASP.NEt requests).
There seems to be a redirection (302). If you use WFetch, you can figure out where it redirects. But this probably explains the problem, it probably redirects to something that doesn't exist.
Kristofer Gafvert
http://www.it-notebook.org
Marked as answer by Leo Tang - MSFT on Dec 24, 2010 11:39 AM
rangasamy007
8 Posts
Diagnose Connection Problems
Dec 17, 2010 08:39 AM|LINK
Hi All,
Thank you for advance.
we are developing asp.net web application with form authentication in IIS 6 - Windows server 2003.
the application is working fine.
but if we call any .html extension we are getting the following errors,
Diagnose Connection Problems
Internet Explorer cannot display the webpage
What you can try:
Diagnose Connection Problems
Internet Explorer cannot display the webpage
This problem can be caused by a variety of issues, including:
For offline users
You can still view subscribed feeds and some recently viewed webpages.
To view subscribed feeds
To view recently visited webpages (might not work on all pages)
Internet Explorer cannot display the webpage
What you can try:
This problem can be caused by a variety of issues, including:
For offline users
You can still view subscribed feeds and some recently viewed webpages.
To view subscribed feeds
To view recently visited webpages (might not work on all pages)
- Click Tools
, and then click Work Offline.
- Click the Favorites Center button
, click History, and then click the page you want to view.
</div>Internet Explorer cannot display the webpage
What you can try:
This problem can be caused by a variety of issues, including:
For offline users
You can still view subscribed feeds and some recently viewed webpages.
To view subscribed feeds
To view recently visited webpages (might not work on all pages)
- Click Tools
, and then click Work Offline.
- Click the Favorites Center button
, click History, and then click the page you want to view.
</div>How can we fix that error?
KristoferG
1343 Posts
Moderator
Re: Diagnose Connection Problems
Dec 17, 2010 09:06 AM|LINK
Hi,
I don't really trust Internet Explorer when it comes to troubleshooting, so the first thing i would do is use WFetch, send a request for a .html-file and see what the response is.
You may also find useful information in the IIS logfile (assuming the request got to IIS). Please see if you have any requests for .html-files logged, and if so, post the entries here so we can have a look at it.
As a side not, i have noticed that this happens in Internet Explorer (later version) due to the html (strange, but it seems to happen, i have never really understand why). Have you tried to use Firefox or any other browser? It does not solve your problem, but it tells us what is wrong. WFetch should also tell us if the HTML is returned to the client, and if, we can rule out IIS and instead focus on a client side issue.
Hope this help and that we can assist you further if you need more help to troublshoot this.
http://www.it-notebook.org
tomkmvp
7657 Posts
MVP
Moderator
Re: Diagnose Connection Problems
Dec 17, 2010 12:08 PM|LINK
Yes, let's see if the IIS log file has anything for this request. The error message is saying that IE can't find the web server (which is strange because it can find the web server for your ASP.NEt requests).
http://mvp.support.microsoft.com/
rangasamy007
8 Posts
Re: Diagnose Connection Problems
Dec 17, 2010 12:25 PM|LINK
Hi,
thank for your response.
I have checked my iis log. but i didnt get it.please give the idea about that
url is http://www.mydomain.com/omOSgWRreyaccrg5iqsNOg--.html
Log Message
2010-12-17 12:26:58 W3SVC169631172 SERVER1 64.27.9.245 GET /omOSgWRreyaccrg5iqsNOg--.html - 80 - 64.27.9.245 HTTP/1.1 Mozilla/4.0+(compatible;+MSIE+7.0;+Windows+NT+5.2;+WOW64;+.NET+CLR+2.0.50727;+.NET4.0C;+.NET4.0E;+.NET+CLR+3.0.04506.648;+.NET+CLR+3.5.21022) __utma=116798234.1321986317.1287468238.1292504686.1292588794.37;+__utmz=116798234.1287468238.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none);+__utmb=116798234.1.10.1292588794;+__utmc=116798234;+ASP.NET_SessionId=njluc545u4vl31ahamvbhmzx - www.mydomain.com 302 0 0 521 767 0
rangasamy007
8 Posts
Re: Diagnose Connection Problems
Dec 17, 2010 12:29 PM|LINK
the application wes developed with asp.net/c# and running under IIS 6
the .aspx exn is working fine. the problem is .html exn.
KristoferG
1343 Posts
Moderator
Re: Diagnose Connection Problems
Dec 17, 2010 01:03 PM|LINK
Hi,
There seems to be a redirection (302). If you use WFetch, you can figure out where it redirects. But this probably explains the problem, it probably redirects to something that doesn't exist.
http://www.it-notebook.org