Prev: iis 7 in vista and databases
Next: URLSCAN 3.1 FOR Windows 2008
From: Robert on 3 Aug 2010 19:41
Hi all.

Why if I stop an individual web site can still access to it?

Using IIS 6.0 on windows SBS 2003.

What I'm doing is enter IIS Mngr. right click on the site and choose
stop. After that, the site description changes to "<mysite> (Stopped)"
but I still can enter to it (log in and navigate) .

The sites are asp.net apps.

So how can I stop a web site?

thanks in advance.

Robert.
From: Brian Cryer on 5 Aug 2010 10:57
"Robert" <roberto.figueroa(a)gmail.com> wrote in message
news:c4a01c45-9615-4297-abf8-f2ece6767a4b(a)g21g2000prn.googlegroups.com...
> Hi all.
>
> Why if I stop an individual web site can still access to it?

More than likely what you are browsing to and what you are stopping are not
the same website. The other possibility is that your browser is caching
things - but if that were the case then you should "web site unresponsive"
type messages from the browser once you try to interact with the site.

> Using IIS 6.0 on windows SBS 2003.

Just tried it to be sure before posting (2003 Standard not SBS, but
otherwise same set-up).
--
Brian Cryer
http://www.cryer.co.uk/brian

From: Robert on 5 Aug 2010 20:00
On Aug 5, 9:57 am, "Brian Cryer" <not.here(a)localhost> wrote:
> More than likely what you are browsing to and what you are stopping are not
> the same website.

Well I have double-checked this and the problem still happens..

This sites are also registered in the ASPDefaultPool (under
Application Pool folder)

I also have found this behavior:

If I try to access by the port the site doesn't respond (ej.
http://myserver.com:8585) but if I access by URL (ej http://myserver.com/myapp)
is when the site is responding

If I stop the "Default Web Site" none site responds, neither by the
port nor the url

thanks again.

From: Brian Cryer on 6 Aug 2010 04:39
"Robert" <roberto.figueroa(a)gmail.com> wrote in message
news:e78f8851-2a87-4e8c-bd74-15f443280416(a)m35g2000prn.googlegroups.com...
> On Aug 5, 9:57 am, "Brian Cryer" <not.here(a)localhost> wrote:
>> More than likely what you are browsing to and what you are stopping are
>> not
>> the same website.
>
> Well I have double-checked this and the problem still happens..
>
> This sites are also registered in the ASPDefaultPool (under
> Application Pool folder)
>
> I also have found this behavior:
>
> If I try to access by the port the site doesn't respond (ej.
> http://myserver.com:8585) but if I access by URL (ej
> http://myserver.com/myapp)
> is when the site is responding
>
> If I stop the "Default Web Site" none site responds, neither by the
> port nor the url

I would guess that http://myserver.com/myapp falls under the default web
site (on the assumption that http://myserver.com is your default website),
and that http://myserver.com:8585 is a different site under IIS. So this
implies that you have the same site twice under IIS - each accessible via
different routes. So, to you they might be the same site but to IIS they are
different. Do you see what I mean?
--
Brian Cryer
http://www.cryer.co.uk/brian

 | 
Pages: 1
Prev: iis 7 in vista and databases
Next: URLSCAN 3.1 FOR Windows 2008