12-11-04 08:36 AM
Ok. Then another possibility could be due to the recycling of the worker
process. Try disabling all Application Pool recycling and see what happens.
Best way to do this is:
1. Create a new ApplicationPool for all ASP.Net applications
2. Assign this ApplicationPool to all ASP.Net applications
3. Configure this ApplicationPool to never recycle, idle timeout, etc. Only
enable the Private Memory based recycling based on 60% of RAM
--
//David
IIS
http://blogs.msdn.com/David.Wang
This posting is provided "AS IS" with no warranties, and confers no rights.
//
<john_murray_sp@hotmail.com> wrote in message
news:1102668876.960932.83640@z14g2000cwz.googlegroups.com...
Thanks for the reply David.
A couple of points:
1) There is no proxy - clients are connected directly to the server.
2) The Integrated Authentication is working (in general). This is
occurring randomly - i.e. the user hits the site, (is authenticated no
problem), starts using the site, no problem, then, at times, is
prompted with a logon dialog. Happens on different pages and different
times.
3) Sometimes it is a 401.1 error.
thanks,
john
[ Post a follow-up to this message ]
|