We've recently upgraded our existing SharePoint 2007 site to SharePoint 2010. We have a couple of internal and external sites that make use of the asmx web services provided by SharePoint.
We currently have an issue where after 8 - 10 hours all requests from the privileged account will start receiving 401.0 access denied errors from IIS7. A app pool recycle will solve the problem, and then 8 - 10 hours the same thing happens again. While one priviledged account is receiving 401's, other accounts will work for 8 - 10 hours.
See our IIS7 Logs below:
2011-09-26 00:00:45 10.45.25.x POST /_vti_bin/lists.asmx - 12345 - 10.45.25.x Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.237) 401 0 0 3
2011-09-26 00:00:45 10.45.25.x POST /_vti_bin/lists.asmx - 12345 0#.w|domain\account 10.45.25.x Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.237) 401 0 0 289
2011-09-26 00:02:45 10.45.25.x POST /_vti_bin/lists.asmx - 12345 - 10.45.25.x Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.237) 401 0 0 5
2011-09-26 00:02:45 10.45.25.x POST /_vti_bin/lists.asmx - 12345 0#.w|\ 10.45.25.x Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.237) 401 0 0 298
2011-09-26 00:05:06 10.45.25.x POST /_vti_bin/lists.asmx - 12345 - 10.45.25.x Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.237) 401 0 0 6
2011-09-26 00:05:06 10.45.25.x POST /_vti_bin/lists.asmx - 12345 0#.w|domain\account 10.45.25.x Mozilla/4.0+(compatible;+MSIE+6.0;+MS+Web+Services+Client+Protocol+4.0.30319.237) 401 0 0 296
We are calling these services on its own AAM (Port 12345) that is configured as a Intranet zone. Windows and Anonymous authentication are both enabled.