I get sc-win32-status 121 "The semaphore timeout period has been reached" in our IIS logs. sc-bytes shows 0 and time-taken is 20-200 seconds, even for a simple jpg. Is it possible to use ADPlus to trap the 121 exception and use windbg for instance to locate which component is generating it?