recieving error: Serivce Unavailable Internal-Reason 132

recieving error: Serivce Unavailable Internal-Reason 132

am 16.02.2005 20:45:02 von RonNiederer

I'm running IIS 5.0 and serving a website. When accessing the website via
the internet the client is recieving a page with the message "Serivce
Unavailable Internal-Reason 132". Looking at the web servers logs there is
no record of the client trying to fetch a page. Also, the page appears to
load without error when loaded from our private network.

Any idea what this error means and what could cause it? I suspect it might
be a firewall issue but not sure since port 80 and 443 are passed through.

Re: recieving error: Serivce Unavailable Internal-Reason 132

am 16.02.2005 22:44:54 von someone

IIS does not send such response text, and if you see no evidence of the 500
in the web server logs, then something else between the client and server is
sending that response.

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Ron Niederer" wrote in message
news:52B2D7AC-F8E0-46A1-9CD3-4B489911A285@microsoft.com...
I'm running IIS 5.0 and serving a website. When accessing the website via
the internet the client is recieving a page with the message "Serivce
Unavailable Internal-Reason 132". Looking at the web servers logs there is
no record of the client trying to fetch a page. Also, the page appears to
load without error when loaded from our private network.

Any idea what this error means and what could cause it? I suspect it might
be a firewall issue but not sure since port 80 and 443 are passed through.

Re: recieving error: Serivce Unavailable Internal-Reason 132

am 17.02.2005 12:17:33 von Kristofer Gafvert

Hi,

Does this happen for all Internet users? This message could be generated
by a proxy server, but it is unlikely that all your Internet users use the
same proxy server.

It seems however to be something in between IIS and the client (since the
request never made it to IIS per your explanation). So it could be a
proxy, or reverse proxy. A firewall usually does not generate these kind
of errors (but could of course).


--
Regards,
Kristofer Gafvert
www.gafvert.info - My Articles and help
www.ilopia.com


Ron Niederer wrote:

> I'm running IIS 5.0 and serving a website. When accessing the website
via
> the internet the client is recieving a page with the message "Serivce
> Unavailable Internal-Reason 132". Looking at the web servers logs there
is
> no record of the client trying to fetch a page. Also, the page appears
to
> load without error when loaded from our private network.
>
> Any idea what this error means and what could cause it? I suspect it
might
> be a firewall issue but not sure since port 80 and 443 are passed
through.

Re: recieving error: Serivce Unavailable Internal-Reason 132

am 17.02.2005 17:17:01 von RonNiederer

the plot thinkings...

The problem exists for all internet users proxied or not. I have determined
that the problem disappears if I check "Use Anonymous login". This tells me
that the problem is at the IIS server since changing a server setting
eliminated the error, even though the activity log shows no activity. This
observations lead me to ask: When using "non-anonymous logins" does IIS use
ports other then port 80 for the authentication?

I also found through experimentation that if I define a host header the
problem will surface.

My current work around for the problem was to allow anonymous logon but use
NTFS permisisons on all the web content. Still currious as to why either of
these settings when going through a firewall cuase the error.



"Kristofer Gafvert" wrote:

> Hi,
>
> Does this happen for all Internet users? This message could be generated
> by a proxy server, but it is unlikely that all your Internet users use the
> same proxy server.
>
> It seems however to be something in between IIS and the client (since the
> request never made it to IIS per your explanation). So it could be a
> proxy, or reverse proxy. A firewall usually does not generate these kind
> of errors (but could of course).
>
>
> --
> Regards,
> Kristofer Gafvert
> www.gafvert.info - My Articles and help
> www.ilopia.com
>
>
> Ron Niederer wrote:
>
> > I'm running IIS 5.0 and serving a website. When accessing the website
> via
> > the internet the client is recieving a page with the message "Serivce
> > Unavailable Internal-Reason 132". Looking at the web servers logs there
> is
> > no record of the client trying to fetch a page. Also, the page appears
> to
> > load without error when loaded from our private network.
> >
> > Any idea what this error means and what could cause it? I suspect it
> might
> > be a firewall issue but not sure since port 80 and 443 are passed
> through.
>

Re: recieving error: Serivce Unavailable Internal-Reason 132

am 18.02.2005 04:44:43 von someone

I think your firewall or some network device upstream from IIS is the
problem.


> I have determined that the problem disappears if
> I check "Use Anonymous login". This tells me that
> the problem is at the IIS server since changing a server
> setting eliminated the error, even though the activity
> log shows no activity

I have to disagree with your conclusion that the problem is at the IIS
server because it does not match reality:
1. IIS does not send back the following response: "Serivce Unavailable
Internal-Reason 132".
2. IIS web site log file does not show the request. Either we have a
security vulnerability in IIS not logging requests, or you are looking at
the wrong web site log file, or something else upstream from IIS is sending
back a cached response.


> I also found through experimentation that if I define a host header
> the problem will surface.

This suggests that some network device upstream from IIS is not doing the
right thing. It doesn't know how to forward that info to the web server
correctly.


> My current work around for the problem was to allow anonymous
> logon but use NTFS permisisons on all the web content.

Your workaround is probably not what you wanted to do. If you allow
anonymous logon, then IIS always uses the configured anonymous user account
to access web content -- what you set for NTFS permissions for any given
user is irrelevant -- if the configured anonymous user has access, everyone
has access regardless of who they are. Remember, giving anonymous logon
amounts to never authenticating.


> Still currious as to why either of these settings when going through
> a firewall cuase the error.

This probably indicates that your firewall is the problem, not IIS. The
only thing I can think of is that if you do *not* enable "Use Anonymous
login", then IIS will require users to login by first sending a 401.2
response. Perhaps the firewall is translating 401 responses into "Serivce
Unavailable Internal-Reason 132" . Have you looked up firewall
documentation for what "Reason 132" means?


You see no problems from the Private network because such traffic probably
does not go through the firewall. This is a clearer indication that the
firewall or such network device is the problem, not IIS -- because you have
proven IIS is functioning correctly already.

--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Ron Niederer" wrote in message
news:68D9A65D-6B47-4F28-8B5B-5E173872B5A0@microsoft.com...
the plot thinkings...

The problem exists for all internet users proxied or not. I have determined
that the problem disappears if I check "Use Anonymous login". This tells me
that the problem is at the IIS server since changing a server setting
eliminated the error, even though the activity log shows no activity. This
observations lead me to ask: When using "non-anonymous logins" does IIS use
ports other then port 80 for the authentication?

I also found through experimentation that if I define a host header the
problem will surface.

My current work around for the problem was to allow anonymous logon but use
NTFS permisisons on all the web content. Still currious as to why either of
these settings when going through a firewall cuase the error.



"Kristofer Gafvert" wrote:

> Hi,
>
> Does this happen for all Internet users? This message could be generated
> by a proxy server, but it is unlikely that all your Internet users use the
> same proxy server.
>
> It seems however to be something in between IIS and the client (since the
> request never made it to IIS per your explanation). So it could be a
> proxy, or reverse proxy. A firewall usually does not generate these kind
> of errors (but could of course).
>
>
> --
> Regards,
> Kristofer Gafvert
> www.gafvert.info - My Articles and help
> www.ilopia.com
>
>
> Ron Niederer wrote:
>
> > I'm running IIS 5.0 and serving a website. When accessing the website
> via
> > the internet the client is recieving a page with the message "Serivce
> > Unavailable Internal-Reason 132". Looking at the web servers logs there
> is
> > no record of the client trying to fetch a page. Also, the page appears
> to
> > load without error when loaded from our private network.
> >
> > Any idea what this error means and what could cause it? I suspect it
> might
> > be a firewall issue but not sure since port 80 and 443 are passed
> through.
>