Chris
Thu Feb 02 12:45:18 CST 2006
This is a multi-part message in MIME format.
------=_NextPart_000_00AB_01C62895.C74C6AB0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
If you can I would create a two seperate sites which only does the =
authentication portion to help determine the problem.
You would create a one application pool for this and set one of the new =
sites to use the new pool and the other site to use the old pool.
You could then unfortunitly wait until it fails and then test using the =
new sites. This could help determine if it is related to IIS application =
pools.
If you go down the Ethereal route then putting it on the server would be =
best but if it is a very busy server you may get too much traffic to =
identify one request. It won't help on the client since the client sent =
the request and then is just waiting for the ressponse (60 seconds)
You recyle an application pool not really the site.=20
The application pool will recycle by default under these conditions.
Every 1740 Minutes which is 29 Hours.
If the site gets no requests for 20 minutes then it will also shut down =
the Worker Process. (Gets created again on the next request)
Check the settings for the application pool to see if any of it has been =
re-configured.
This is quite tricky to isolate the problem because we need to determine =
if the problem is with the domain controllers taking a long time to =
respond or IIS is hanging but you could also put in some trace code into =
your application (easy if .NET) more work if asp or some other language.
Another option is to run the IIS Debug Diagnostics tool which can pickup =
hangs.
See this article for more details:
http://www.microsoft.com/technet/community/columns/insider/default.mspx#E=
NEAC
--=20
Cheers
Chris Crowe [IIS MVP 1997 -> 2006]
http://blog.crowe.co.nz
------------------------------------------------
"SW" <SW@discussions.microsoft.com> wrote in message =
news:FDB4C5EE-A253-4C93-90A2-07EC06FF422A@microsoft.com...
>I have used ethereal before so maybe I will try that. We have 3 DC's 2 =
on=20
> our local site one a couple of miles away at our DR site. I have =
configure=20
> the AD sites/subnets to queries are always answered to the nearest DC.
>=20
> The site will either take 2 seconds all the time or when it's slow it =
will=20
> always take around 60 seconds. It's either black or white then is =
never a=20
> time where it's maybe 5 seconds then 40 seconds, it's always the same.
>=20
> 1.) Would you place the Ethereal on the IIS server or the client?
> 2.) I have never recyled the site, can you help with this?
>=20
> Thanks in advance
>=20
> "Chris Crowe [MVP 1997 -> 2006]" wrote:
>=20
>> You are probably better to put a packet sniffer in place when you get =
these=20
>> requests to try to determine if the problem is within the IIS Machine =
or the=20
>> network domain controller answering the query. I use a product called =
>> Ethereal. www.ethereal.com and it is free
>>=20
>> Is the LDAP query going to a local domain controller? Are you =
specifying the=20
>> domain should process your query? or a specific domain controller? or =
Global=20
>> catalog server?
>>=20
>> I have seen issues before on a mis configured network that requests =
that=20
>> should be answered locally were answered by a remote server in China =
for the=20
>> same domain.
>>=20
>> Does it every return in 2 seconds when previously it was taking 1 =
minute=20
>> without you recycling the site? So does it fluterate or is it fast =
and then=20
>> just gets slower or is fast and the just slow?
>>=20
>> --=20
>>=20
>> Cheers
>>=20
>> Chris Crowe [IIS MVP 1997 -> 2006]
>>
http://blog.crowe.co.nz
>> ------------------------------------------------
>>=20
>>=20
>> "SW" <SW@discussions.microsoft.com> wrote in message=20
>> news:51DCF948-13DB-4E06-BBBD-5E479D645CA2@microsoft.com...
>> > We have a Windows 2003 server running the IIS 6. It runs 4 =
Internal=20
>> > websites
>> > and one of them is a logon page that authenticates our usernames to =
our AD
>> > server.
>> > Sometimes this logon page takes a minute to log in sometimes 2 =
seconds. I
>> > find if I restart this one out of the 4 websites the hole thing =
speeds up.
>> > What settings in the website can I focus on or what perfomance =
counters=20
>> > can I
>> > run to find out what's happening?=20
>>=20
>>=20
>>
------=_NextPart_000_00AB_01C62895.C74C6AB0
Content-Type: text/html;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable
=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8">
<META content=3D"MSHTML 6.00.2900.2802" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DArial size=3D2>If you can I would create a two =
seperate sites=20
which only does the authentication portion to help determine the=20
problem.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>You would create a one application pool =
for this=20
and set one of the new sites to use the new pool and the other site to =
use the=20
old pool.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>You could then unfortunitly wait until =
it fails and=20
then test using the new sites. This could help determine if it is =
related to IIS=20
application pools.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>If you go down the Ethereal route then =
putting it=20
on the server would be best but if it is a very busy server you may get =
too much=20
traffic to identify one request. It won't help on the client since the =
client=20
sent the request and then is just waiting for the ressponse (60=20
seconds)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>You recyle an application pool not =
really the site.=20
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>The application pool will recycle by =
default under=20
these conditions.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Every 1740 Minutes which is 29 =
Hours.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>If the site gets no requests for 20 =
minutes then it=20
will also shut down the Worker Process. (Gets created again on the next=20
request)</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Check the settings for the application =
pool to see=20
if any of it has been re-configured.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>This is quite tricky to isolate the =
problem because=20
we need to determine if the problem is with the domain controllers =
taking a long=20
time to respond or IIS is hanging but you could also put in some trace =
code into=20
your application (easy if .NET) more work if asp or some other=20
language.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Another option is to run the IIS Debug =
Diagnostics=20
tool which can pickup hangs.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>See this article for more =
details:</FONT></DIV>
<DIV><FONT face=3DArial size=3D2> </DIV><A=20
href=3D"
http://www.microsoft.com/technet/community/columns/insider/defaul=
t.mspx#ENEAC">
http://www.microsoft.com/technet/community/columns/insider/=
default.mspx#ENEAC</A>
<DIV><BR>-- <BR><BR>Cheers</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Chris Crowe [IIS MVP 1997 -> =
2006]<BR></FONT><A=20
href=3D"
http://blog.crowe.co.nz"><FONT face=3DArial=20
size=3D2>
http://blog.crowe.co.nz</FONT></A><BR><FONT face=3DArial=20
size=3D2>------------------------------------------------</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>"SW" <</FONT><A=20
href=3D"mailto:SW@discussions.microsoft.com"><FONT face=3DArial=20
size=3D2>SW@discussions.microsoft.com</FONT></A><FONT face=3DArial =
size=3D2>> wrote=20
in message </FONT><A=20
href=3D"news:FDB4C5EE-A253-4C93-90A2-07EC06FF422A@microsoft.com"><FONT =
face=3DArial=20
size=3D2>news:FDB4C5EE-A253-4C93-90A2-07EC06FF422A@microsoft.com</FONT></=
A><FONT=20
face=3DArial size=3D2>...</FONT></DIV><FONT face=3DArial size=3D2>>I =
have used=20
ethereal before so maybe I will try that. We have 3 DC's 2 on =
<BR>> our=20
local site one a couple of miles away at our DR site. I have =
configure=20
<BR>> the AD sites/subnets to queries are always answered to the =
nearest=20
DC.<BR>> <BR>> The site will either take 2 seconds all the time or =
when=20
it's slow it will <BR>> always take around 60 seconds. It's =
either=20
black or white then is never a <BR>> time where it's maybe 5 seconds =
then 40=20
seconds, it's always the same.<BR>> <BR>> 1.) Would you place the =
Ethereal=20
on the IIS server or the client?<BR>> 2.) I have never recyled the =
site, can=20
you help with this?<BR>> <BR>> Thanks in advance<BR>> <BR>> =
"Chris=20
Crowe [MVP 1997 -> 2006]" wrote:<BR>> <BR>>> You are =
probably better=20
to put a packet sniffer in place when you get these <BR>>> =
requests to try=20
to determine if the problem is within the IIS Machine or the =
<BR>>>=20
network domain controller answering the query. I use a product called=20
<BR>>> Ethereal. </FONT><A href=3D"
http://www.ethereal.com"><FONT =
face=3DArial=20
size=3D2>www.ethereal.com</FONT></A><FONT face=3DArial size=3D2> and it =
is=20
free<BR>>> <BR>>> Is the LDAP query going to a local domain=20
controller? Are you specifying the <BR>>> domain should process =
your=20
query? or a specific domain controller? or Global <BR>>> catalog=20
server?<BR>>> <BR>>> I have seen issues before on a mis =
configured=20
network that requests that <BR>>> should be answered locally were =
answered=20
by a remote server in China for the <BR>>> same =
domain.<BR>>>=20
<BR>>> Does it every return in 2 seconds when previously it was =
taking 1=20
minute <BR>>> without you recycling the site? So does it fluterate =
or is=20
it fast and then <BR>>> just gets slower or is fast and the just=20
slow?<BR>>> <BR>>> -- <BR>>> <BR>>> =
Cheers<BR>>>=20
<BR>>> Chris Crowe [IIS MVP 1997 -> 2006]<BR>>> </FONT><A =
href=3D"
http://blog.crowe.co.nz"><FONT face=3DArial=20
size=3D2>
http://blog.crowe.co.nz</FONT></A><BR><FONT face=3DArial =
size=3D2>>>=20
------------------------------------------------<BR>>> =
<BR>>>=20
<BR>>> "SW" <</FONT><A =
href=3D"mailto:SW@discussions.microsoft.com"><FONT=20
face=3DArial size=3D2>SW@discussions.microsoft.com</FONT></A><FONT =
face=3DArial=20
size=3D2>> wrote in message <BR>>> </FONT><A=20
href=3D"news:51DCF948-13DB-4E06-BBBD-5E479D645CA2@microsoft.com"><FONT =
face=3DArial=20
size=3D2>news:51DCF948-13DB-4E06-BBBD-5E479D645CA2@microsoft.com</FONT></=
A><FONT=20
face=3DArial size=3D2>...<BR>>> > We have a Windows 2003 server =
running the=20
IIS 6. It runs 4 Internal <BR>>> > websites<BR>>> =
> and=20
one of them is a logon page that authenticates our usernames to our=20
AD<BR>>> > server.<BR>>> > Sometimes this logon page =
takes a=20
minute to log in sometimes 2 seconds. I<BR>>> > find if I =
restart=20
this one out of the 4 websites the hole thing speeds up.<BR>>> =
> What=20
settings in the website can I focus on or what perfomance counters =
<BR>>>=20
> can I<BR>>> > run to find out what's happening? =
<BR>>>=20
<BR>>> <BR>>></FONT></BODY></HTML>
------=_NextPart_000_00AB_01C62895.C74C6AB0--