Paul,
I think in this case the first step would be to enable the "time taken"
field in the IIS logs settings. Next step would be to parse the logs with
the IIS6 resource kit tool called LogParser.exe. You can verify whether the
problem occurs on IIS or outside IIS. A long time-taken will show up if the
problem is on the IIS machine. Below is a sample query that you can use
with the log parser. For additional information on the LogParser tool
please see the LogParser documentation.
logparser.exe "SELECT COUNT(time-taken) AS time-taken-count,
AVG(time-taken) AS time-taken-avg, MAX(time-taken) AS time-taken-max,
MIN(time-taken) AS time-taken-min, cs-uri-stem FROM ex031010.log TO Avg.txt
GROUP BY cs-uri-stem ORDER BY AVG(time-taken) DESC" -i:w3c -o:w3c -q

n
Thanks,
Brian