You are correct. This is most likely a specific client issue but not a
server-side indexing service or IIS one.
To expose more detailed error info of the problem, you can run webfetch on
the problematic client to trace the rawdata of http request/response.
HOW TO: Use Wfetch.exe to Troubleshoot HTTP Connections
To use, please input:
Auth: (in case the site is anonymous enabled, just use Anonymous, otherwise
please specify proper user credential)
Press Go! to issue a http request to the server and check what response is
returned. I think the trace should slow us with some clue. Please feel free
to paste the whole log data here and I will be glad to help on checking it.
Have a good day.
Microsoft Online Community Support
Get notification to my posts through email? Please refer to:
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at:
This posting is provided "AS IS" with no warranties, and confers no rights.