Re: Cannot connect to Win. Auth site with IP address in URL
- From: "Ken Schaefer" <kenREMOVE@xxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 22 Sep 2009 22:25:44 +0800
Hi,
Internet Explorer can not display the webpage is a generic error message. Turn off "Show Friendly HTTP Errors" in IE, and reload the page. If it still says the same thing (with text to the effect of "can not contact server or DNS error" in IE7 or less) then there is no response from IIS (either the request is not getting there, or something is preventing the request from being processed). Alternatively if you get a HTTP status code (404, 500) etc, then you know that something else is up with IIS.
If you are sure that there is no proxy server that the request is going through, and there is no response from IIS (according to IE) then please look in:
a) httperr.log file on IIS server to see if http.sys is dropping the request for some reason (e.g. bad host name)
b) Windows event logs on IIS server to see if app pool is crashing or similar
c) IIS log file to see if IIS is processing the request but for some reason no response is being sent.
Cheers
Ken
"Rich Armstrong" <RichA24@xxxxxxxxxxxxx> wrote in message news:6C4E70B6-657D-447A-9CF8-346091F50709@xxxxxxxxxxxxxxxx
Something more is involved. In the interest of brevity, I omitted some things
from my initial post:
# Every browser (IE) used to investigate this problem is configured with
10.*.*.* in the Intranet Zone site list. (For good measure, we also added the
specific IP addresses of the problem servers.) These browsers routinely
connect to other Windows-authenticated web applications all over the
corporate network, and can do so via simple host name, fully-qualified host
name, or IP address.
# The connection to the Windows-authenticated application fails only on
servers at one site (office) on our corporate network. Moreover, the
connection succeeds with a fully-qualified host name. In other words, this
URL works:
http://InternalServer.InternalDomain.net/MyWinAuthApp
in spite of the periods in the host name.
We’ve also tried adding a simple alias to the local hosts file, e.g.,
10.1.2.3 BadServer, and then using BadServer as the host name in the URL,
but that fails, too.
By the way, “failure” can mean any of the following:
* The browser prompts for user name and password. Valid credentials are
entered and then IE displays “Internet Explorer cannot display the webpage.”
* The browser prompts for only the password, with the user name is already
in place. A valid password is entered and then IE displays “Internet Explorer
cannot display the webpage.”
* No prompt appears at all and IE displays “Internet Explorer cannot display
the webpage.”
Any ideas about what else may be the cause would be appreciated.
--
Rich Armstrong
.
- Follow-Ups:
- Re: Cannot connect to Win. Auth site with IP address in URL
- From: Rich Armstrong
- Re: Cannot connect to Win. Auth site with IP address in URL
- References:
- Cannot connect to Win. Auth site with IP address in URL
- From: Rich Armstrong
- RE: Cannot connect to Win. Auth site with IP address in URL
- From: "WenJun Zhang[msft]"
- RE: Cannot connect to Win. Auth site with IP address in URL
- From: Rich Armstrong
- Cannot connect to Win. Auth site with IP address in URL
- Prev by Date: Frontpage extension, webbot keeps asking username password
- Next by Date: Re: Cannot connect to Win. Auth site with IP address in URL
- Previous by thread: RE: Cannot connect to Win. Auth site with IP address in URL
- Next by thread: Re: Cannot connect to Win. Auth site with IP address in URL
- Index(es):
Relevant Pages
|