Hi,

Whenever I try to browse the default web site, either on my server or from
another machine on the LAN, I get the error

"Internet Explorer cannot display the webpage
Most likely causes:
You are not connected to the Internet.
The website is encountering problems.
There might be a typing error in the address. "

-The website is listening on port 80 (confirmed by telnet) on all adapters.
There is no firewall etc blocking access and no other programs listening on
this port.
-Anonymous access is allowed
-The files at c:\inetpub\wwwroot seem ok
-There are no IP restrictions

I've setup logging but no log files seem to be created.

Can anyone suggest what might be going on?

Cheers,
H

Re: Unable to browse default website by Pablo

Pablo
Tue Aug 05 12:09:50 CDT 2008

From the client machine:

ping domain
Works ?

telnet domain 80
Works ?

Test it from the client.


Saludos!

"Huwy" <cymru@mbyth.com> wrote in message
news:uC4NYLx9IHA.4892@TK2MSFTNGP05.phx.gbl...
> Hi,
>
> Whenever I try to browse the default web site, either on my server or from
> another machine on the LAN, I get the error
>
> "Internet Explorer cannot display the webpage
> Most likely causes:
> You are not connected to the Internet.
> The website is encountering problems.
> There might be a typing error in the address. "
>
> -The website is listening on port 80 (confirmed by telnet) on all
> adapters. There is no firewall etc blocking access and no other programs
> listening on this port.
> -Anonymous access is allowed
> -The files at c:\inetpub\wwwroot seem ok
> -There are no IP restrictions
>
> I've setup logging but no log files seem to be created.
>
> Can anyone suggest what might be going on?
>
> Cheers,
> H
>
>
>
>
>
>
>
>



Re: Unable to browse default website by Dave

Dave
Tue Aug 05 12:42:20 CDT 2008

Huwy wrote:
> Whenever I try to browse the default web site, either on my server or
> from another machine on the LAN, I get the error
>
> "Internet Explorer cannot display the webpage
> Most likely causes:
> You are not connected to the Internet.
> The website is encountering problems.
> There might be a typing error in the address. "
>
> -The website is listening on port 80 (confirmed by telnet) on all
> adapters. There is no firewall etc blocking access and no other
> programs listening on this port.
> -Anonymous access is allowed
> -The files at c:\inetpub\wwwroot seem ok
> -There are no IP restrictions

What happens if you use the IP Address?



--
Dave Anderson

Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms.



Re: Unable to browse default website by Huwy

Huwy
Wed Aug 06 01:52:26 CDT 2008

Same problem. It's definately not a DNS/firewall issue. My guess is
something in IIS has gone awry.

"Dave Anderson" <NPQRWPDWZGSP@spammotel.com> wrote in message
news:u$hkdKy9IHA.2324@TK2MSFTNGP06.phx.gbl...
> Huwy wrote:
>> Whenever I try to browse the default web site, either on my server or
>> from another machine on the LAN, I get the error
>>
>> "Internet Explorer cannot display the webpage
>> Most likely causes:
>> You are not connected to the Internet.
>> The website is encountering problems.
>> There might be a typing error in the address. "
>>
>> -The website is listening on port 80 (confirmed by telnet) on all
>> adapters. There is no firewall etc blocking access and no other
>> programs listening on this port.
>> -Anonymous access is allowed
>> -The files at c:\inetpub\wwwroot seem ok
>> -There are no IP restrictions
>
> What happens if you use the IP Address?
>
>
>
> --
> Dave Anderson
>
> Unsolicited commercial email will be read at a cost of $500 per message.
> Use of this email address implies consent to these terms.
>



Re: Unable to browse default website by Daniel

Daniel
Wed Aug 06 03:46:05 CDT 2008

What's in the page you're requesting? Do you have any redirection set for
the site in the IIS settings?

Dan

Huwy wrote on Wed, 6 Aug 2008 07:52:26 +0100:

> Same problem. It's definately not a DNS/firewall issue. My guess is
> something in IIS has gone awry.

> "Dave Anderson" <NPQRWPDWZGSP@spammotel.com> wrote in message news:u$hkdKy9IHA.2324@TK2MSFTNGP06.phx.gbl...
>> Huwy wrote:
>>> Whenever I try to browse the default web site, either on my server
>>> or from another machine on the LAN, I get the error

>>> "Internet Explorer cannot display the webpage
>>> Most likely causes:
>>> You are not connected to the Internet.
>>> The website is encountering problems.
>>> There might be a typing error in the address. "

>>> -The website is listening on port 80 (confirmed by telnet) on all
>>> adapters. There is no firewall etc blocking access and no other
>>> programs listening on this port.
>>> -Anonymous access is allowed -The files at c:\inetpub\wwwroot seem
>>> ok -There are no IP restrictions

>> What happens if you use the IP Address?



>> --
>> Dave Anderson

>> Unsolicited commercial email will be read at a cost of $500 per
>> message.
>> Use of this email address implies consent to these terms.




Re: Unable to browse default website by Huwy

Huwy
Wed Aug 06 05:33:42 CDT 2008

No redirection set. I can open up c:\inetpub\wwwroot\default.htm and it
shows the SBS homepage. It's got me completely flummoxed!

There's also a sharepoint site on 8081 - I can't connect to this either -
same error.

"Daniel Crichton" <msnews@worldofspack.com> wrote in message
news:%23HNseD69IHA.5544@TK2MSFTNGP03.phx.gbl...
> What's in the page you're requesting? Do you have any redirection set for
> the site in the IIS settings?
>
> Dan
>
> Huwy wrote on Wed, 6 Aug 2008 07:52:26 +0100:
>
>> Same problem. It's definately not a DNS/firewall issue. My guess is
>> something in IIS has gone awry.
>
>> "Dave Anderson" <NPQRWPDWZGSP@spammotel.com> wrote in message
>> news:u$hkdKy9IHA.2324@TK2MSFTNGP06.phx.gbl...
> >> Huwy wrote:
> >>> Whenever I try to browse the default web site, either on my server
> >>> or from another machine on the LAN, I get the error
>
> >>> "Internet Explorer cannot display the webpage
> >>> Most likely causes:
> >>> You are not connected to the Internet.
> >>> The website is encountering problems.
> >>> There might be a typing error in the address. "
>
> >>> -The website is listening on port 80 (confirmed by telnet) on all
> >>> adapters. There is no firewall etc blocking access and no other
> >>> programs listening on this port.
> >>> -Anonymous access is allowed -The files at c:\inetpub\wwwroot seem
> >>> ok -There are no IP restrictions
>
> >> What happens if you use the IP Address?
>
>
>
> >> --
> >> Dave Anderson
>
> >> Unsolicited commercial email will be read at a cost of $500 per
> >> message.
> >> Use of this email address implies consent to these terms.
>
>
>



Re: Unable to browse default website by Daniel

Daniel
Wed Aug 06 08:10:42 CDT 2008

Have you tried turning off "Show friendly error messages" in IE and see what
the actual error returned from the server is? Also check the IIS logs and
see what the response code is.

Dan

Huwy wrote on Wed, 6 Aug 2008 11:33:42 +0100:

> No redirection set. I can open up c:\inetpub\wwwroot\default.htm and it
> shows the SBS homepage. It's got me completely flummoxed!

> There's also a sharepoint site on 8081 - I can't connect to this either
> - same error.

> "Daniel Crichton" <msnews@worldofspack.com> wrote in message news:%23HNseD69IHA.5544@TK2MSFTNGP03.phx.gbl...
>> What's in the page you're requesting? Do you have any redirection set
>> for the site in the IIS settings?

>> Dan

>> Huwy wrote on Wed, 6 Aug 2008 07:52:26 +0100:

>>> Same problem. It's definately not a DNS/firewall issue. My guess is
>>> something in IIS has gone awry.

>>> "Dave Anderson" <NPQRWPDWZGSP@spammotel.com> wrote in message
>>> news:u$hkdKy9IHA.2324@TK2MSFTNGP06.phx.gbl...
>>>> Huwy wrote:
>>>>> Whenever I try to browse the default web site, either on my server
>>>>> or from another machine on the LAN, I get the error

>>>>> "Internet Explorer cannot display the webpage
>>>>> Most likely causes:
>>>>> You are not connected to the Internet.
>>>>> The website is encountering problems.
>>>>> There might be a typing error in the address. "

>>>>> -The website is listening on port 80 (confirmed by telnet) on all
>>>>> adapters. There is no firewall etc blocking access and no other
>>>>> programs listening on this port.
>>>>> -Anonymous access is allowed -The files at c:\inetpub\wwwroot seem
>>>>> ok -There are no IP restrictions

>>>> What happens if you use the IP Address?



>>>> --
>>>> Dave Anderson

>>>> Unsolicited commercial email will be read at a cost of $500 per
>>>> message.
>>>> Use of this email address implies consent to these terms.






Re: Unable to browse default website by Huwy

Huwy
Wed Aug 06 08:43:27 CDT 2008

Hi, yes I have tried turning off "show friendly messages" you get the
message I posted below.
Weirdly I;ve set the IIS logging to hourly but no new logs are appearing?

"Daniel Crichton" <msnews@worldofspack.com> wrote in message
news:%23z6rVX89IHA.3884@TK2MSFTNGP05.phx.gbl...
> Have you tried turning off "Show friendly error messages" in IE and see
> what the actual error returned from the server is? Also check the IIS logs
> and see what the response code is.
>
> Dan
>
> Huwy wrote on Wed, 6 Aug 2008 11:33:42 +0100:
>
>> No redirection set. I can open up c:\inetpub\wwwroot\default.htm and it
>> shows the SBS homepage. It's got me completely flummoxed!
>
>> There's also a sharepoint site on 8081 - I can't connect to this either
>> - same error.
>
>> "Daniel Crichton" <msnews@worldofspack.com> wrote in message
>> news:%23HNseD69IHA.5544@TK2MSFTNGP03.phx.gbl...
> >> What's in the page you're requesting? Do you have any redirection set
> >> for the site in the IIS settings?
>
> >> Dan
>
> >> Huwy wrote on Wed, 6 Aug 2008 07:52:26 +0100:
>
> >>> Same problem. It's definately not a DNS/firewall issue. My guess is
> >>> something in IIS has gone awry.
>
> >>> "Dave Anderson" <NPQRWPDWZGSP@spammotel.com> wrote in message
> >>> news:u$hkdKy9IHA.2324@TK2MSFTNGP06.phx.gbl...
> >>>> Huwy wrote:
> >>>>> Whenever I try to browse the default web site, either on my server
> >>>>> or from another machine on the LAN, I get the error
>
> >>>>> "Internet Explorer cannot display the webpage
> >>>>> Most likely causes:
> >>>>> You are not connected to the Internet.
> >>>>> The website is encountering problems.
> >>>>> There might be a typing error in the address. "
>
> >>>>> -The website is listening on port 80 (confirmed by telnet) on all
> >>>>> adapters. There is no firewall etc blocking access and no other
> >>>>> programs listening on this port.
> >>>>> -Anonymous access is allowed -The files at c:\inetpub\wwwroot seem
> >>>>> ok -There are no IP restrictions
>
> >>>> What happens if you use the IP Address?
>
>
>
> >>>> --
> >>>> Dave Anderson
>
> >>>> Unsolicited commercial email will be read at a cost of $500 per
> >>>> message.
> >>>> Use of this email address implies consent to these terms.
>
>
>
>
>



Re: Unable to browse default website by Dave

Dave
Wed Aug 06 09:44:36 CDT 2008

Huwy wrote:
>> What happens if you use the IP Address?
>
> Same problem. It's definately not a DNS/firewall issue. My
> guess is something in IIS has gone awry.

You have ensured that World Wide Web Publishing Service is running?



--
Dave Anderson

Unsolicited commercial email will be read at a cost of $500 per message. Use
of this email address implies consent to these terms.



Re: Unable to browse default website by Huwy

Huwy
Wed Aug 06 10:30:35 CDT 2008

yes it is.

"Dave Anderson" <NPQRWPDWZGSP@spammotel.com> wrote in message
news:OHy7zL99IHA.4892@TK2MSFTNGP05.phx.gbl...
> Huwy wrote:
>>> What happens if you use the IP Address?
>>
>> Same problem. It's definately not a DNS/firewall issue. My
>> guess is something in IIS has gone awry.
>
> You have ensured that World Wide Web Publishing Service is running?
>
>
>
> --
> Dave Anderson
>
> Unsolicited commercial email will be read at a cost of $500 per message.
> Use of this email address implies consent to these terms.
>



Re: Unable to browse default website by David

David
Wed Aug 06 22:08:29 CDT 2008

At a high level -- if you do not see any entries in IIS log file, then
the request has not been processed by IIS and you need to look outside
of IIS for the cause.

Step-by-step. No shortcuts -- because bizarre, baffling situations
usually result from overlooking some detail:

1. The first thing you have to prove is that the client request
actually made it to the server. A network sniff run on the server will
prove whether the request is getting to the server and if so, in what
form. Please provide the raw HTTP bytes of the request.

2. After you prove the request actually got to the server running IIS,
we have to verify that the IIS process actually accepted and handled
the request. You do this by using NETSTAT.EXE -ano to verify that the
0.0.0.0:80 binding is listened by inetinfo.exe (IIS5/IIS5.1) or
svchost.exe which loads IISW3ADM.DLL (IIS6/IIS7) -- not just any
random svchost.exe. If you've played around with IPListenList or such
things in HTTP.SYS, make the appropriate adjustments to the actual
IP:Port binding values, but they still must be bound to the right
process I mentioned.

3. After proving that IIS indeed handles the request sent to the IP
used in step #1, you look at the ServerBindings property of all
Websites to determine which Website handles the request. Remember the
Website has to be Started and Running for requests to route to it, and
you cannot have duplicate ServerBindings active (this will cause an
Event Log detailing the duplication).

4. Once you know which IIS Website has the ServerBindings that match
the IP:Port:Host information obtained in step #1, you can lookup the
LogDirectory for the website to know where its logfiles are kept.

Now, assuming we are talking about IIS6 -- if you do not see a log
entry in #4 and you are sure of #2 and #3, then you want to look in
%windir%\System32\LogFiles\HTTPERR for failed requests and the
indicated reason why.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//




On Aug 6, 8:30=A0am, "Huwy" <cy...@mbyth.com> wrote:
> yes it is.
>
> "Dave Anderson" <NPQRWPDWZ...@spammotel.com> wrote in message
>
> news:OHy7zL99IHA.4892@TK2MSFTNGP05.phx.gbl...
>
>
>
> > Huwy wrote:
> >>> What happens if you use the IP Address?
>
> >> Same problem. It's definately not a DNS/firewall issue. My
> >> guess is something in IIS has gone awry.
>
> > You have ensured that World Wide Web Publishing Service is running?
>
> > --
> > Dave Anderson
>
> > Unsolicited commercial email will be read at a cost of $500 per message=
.
> > Use of this email address implies consent to these terms.- Hide quoted =
text -
>
> - Show quoted text -


Re: Unable to browse default website by Huwy

Huwy
Thu Aug 07 02:06:57 CDT 2008

Thanks for some excellent info.

In HTTPERR I get the following over and over...
2008-08-07 07:00:51 - - - - - - - - - 1_Connections_Refused -
2008-08-07 07:03:01 - - - - - - - - - 1_Connections_Refused -
2008-08-07 07:04:06 - - - - - - - - - 1_Connections_Refused -
2008-08-07 07:04:21 - - - - - - - - - 1_Connections_Refused -
2008-08-07 07:04:26 - - - - - - - - - 1_Connections_Refused -
2008-08-07 07:05:01 - - - - - - - - - 1_Connections_Refused -

Do you have any idea what might be causing this?

-H

"David Wang" <w3.4you@gmail.com> wrote in message
news:7929c373-ba9f-444b-bf85-4f92b7515a13@j1g2000prb.googlegroups.com...
At a high level -- if you do not see any entries in IIS log file, then
the request has not been processed by IIS and you need to look outside
of IIS for the cause.

Step-by-step. No shortcuts -- because bizarre, baffling situations
usually result from overlooking some detail:

1. The first thing you have to prove is that the client request
actually made it to the server. A network sniff run on the server will
prove whether the request is getting to the server and if so, in what
form. Please provide the raw HTTP bytes of the request.

2. After you prove the request actually got to the server running IIS,
we have to verify that the IIS process actually accepted and handled
the request. You do this by using NETSTAT.EXE -ano to verify that the
0.0.0.0:80 binding is listened by inetinfo.exe (IIS5/IIS5.1) or
svchost.exe which loads IISW3ADM.DLL (IIS6/IIS7) -- not just any
random svchost.exe. If you've played around with IPListenList or such
things in HTTP.SYS, make the appropriate adjustments to the actual
IP:Port binding values, but they still must be bound to the right
process I mentioned.

3. After proving that IIS indeed handles the request sent to the IP
used in step #1, you look at the ServerBindings property of all
Websites to determine which Website handles the request. Remember the
Website has to be Started and Running for requests to route to it, and
you cannot have duplicate ServerBindings active (this will cause an
Event Log detailing the duplication).

4. Once you know which IIS Website has the ServerBindings that match
the IP:Port:Host information obtained in step #1, you can lookup the
LogDirectory for the website to know where its logfiles are kept.

Now, assuming we are talking about IIS6 -- if you do not see a log
entry in #4 and you are sure of #2 and #3, then you want to look in
%windir%\System32\LogFiles\HTTPERR for failed requests and the
indicated reason why.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//




On Aug 6, 8:30 am, "Huwy" <cy...@mbyth.com> wrote:
> yes it is.
>
> "Dave Anderson" <NPQRWPDWZ...@spammotel.com> wrote in message
>
> news:OHy7zL99IHA.4892@TK2MSFTNGP05.phx.gbl...
>
>
>
> > Huwy wrote:
> >>> What happens if you use the IP Address?
>
> >> Same problem. It's definately not a DNS/firewall issue. My
> >> guess is something in IIS has gone awry.
>
> > You have ensured that World Wide Web Publishing Service is running?
>
> > --
> > Dave Anderson
>
> > Unsolicited commercial email will be read at a cost of $500 per message.
> > Use of this email address implies consent to these terms.- Hide quoted
> > text -
>
> - Show quoted text -



Re: Unable to browse default website by Huwy

Huwy
Thu Aug 07 04:12:22 CDT 2008

I've just found, what I assume is, your article...
http://blogs.msdn.com/david.wang/archive/2005/09/21/HOWTO-Diagnose-IIS6-failing-to-accept-connections-due-to-Connections-Refused.aspx

I will try a reboot tonight and test it from there. Thanks a lot again - big
help.

-H

"Huwy" <cymru@mbyth.com> wrote in message
news:%233uVIyF%23IHA.4816@TK2MSFTNGP06.phx.gbl...
> Thanks for some excellent info.
>
> In HTTPERR I get the following over and over...
> 2008-08-07 07:00:51 - - - - - - - - - 1_Connections_Refused -
> 2008-08-07 07:03:01 - - - - - - - - - 1_Connections_Refused -
> 2008-08-07 07:04:06 - - - - - - - - - 1_Connections_Refused -
> 2008-08-07 07:04:21 - - - - - - - - - 1_Connections_Refused -
> 2008-08-07 07:04:26 - - - - - - - - - 1_Connections_Refused -
> 2008-08-07 07:05:01 - - - - - - - - - 1_Connections_Refused -
>
> Do you have any idea what might be causing this?
>
> -H
>
> "David Wang" <w3.4you@gmail.com> wrote in message
> news:7929c373-ba9f-444b-bf85-4f92b7515a13@j1g2000prb.googlegroups.com...
> At a high level -- if you do not see any entries in IIS log file, then
> the request has not been processed by IIS and you need to look outside
> of IIS for the cause.
>
> Step-by-step. No shortcuts -- because bizarre, baffling situations
> usually result from overlooking some detail:
>
> 1. The first thing you have to prove is that the client request
> actually made it to the server. A network sniff run on the server will
> prove whether the request is getting to the server and if so, in what
> form. Please provide the raw HTTP bytes of the request.
>
> 2. After you prove the request actually got to the server running IIS,
> we have to verify that the IIS process actually accepted and handled
> the request. You do this by using NETSTAT.EXE -ano to verify that the
> 0.0.0.0:80 binding is listened by inetinfo.exe (IIS5/IIS5.1) or
> svchost.exe which loads IISW3ADM.DLL (IIS6/IIS7) -- not just any
> random svchost.exe. If you've played around with IPListenList or such
> things in HTTP.SYS, make the appropriate adjustments to the actual
> IP:Port binding values, but they still must be bound to the right
> process I mentioned.
>
> 3. After proving that IIS indeed handles the request sent to the IP
> used in step #1, you look at the ServerBindings property of all
> Websites to determine which Website handles the request. Remember the
> Website has to be Started and Running for requests to route to it, and
> you cannot have duplicate ServerBindings active (this will cause an
> Event Log detailing the duplication).
>
> 4. Once you know which IIS Website has the ServerBindings that match
> the IP:Port:Host information obtained in step #1, you can lookup the
> LogDirectory for the website to know where its logfiles are kept.
>
> Now, assuming we are talking about IIS6 -- if you do not see a log
> entry in #4 and you are sure of #2 and #3, then you want to look in
> %windir%\System32\LogFiles\HTTPERR for failed requests and the
> indicated reason why.
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //
>
>
>
>
> On Aug 6, 8:30 am, "Huwy" <cy...@mbyth.com> wrote:
>> yes it is.
>>
>> "Dave Anderson" <NPQRWPDWZ...@spammotel.com> wrote in message
>>
>> news:OHy7zL99IHA.4892@TK2MSFTNGP05.phx.gbl...
>>
>>
>>
>> > Huwy wrote:
>> >>> What happens if you use the IP Address?
>>
>> >> Same problem. It's definately not a DNS/firewall issue. My
>> >> guess is something in IIS has gone awry.
>>
>> > You have ensured that World Wide Web Publishing Service is running?
>>
>> > --
>> > Dave Anderson
>>
>> > Unsolicited commercial email will be read at a cost of $500 per
>> > message.
>> > Use of this email address implies consent to these terms.- Hide quoted
>> > text -
>>
>> - Show quoted text -
>
>