Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

This is on Windows Server 2003 Running IIS.

I have an ASP.NET 2.0 website which is also hosting some web services. When the site makes a webservice call to itself (localhost), I get back a 404: Bad Request.

I would like to see the actual request coming into IIS, but I can't think of a way to do it. Wireshark doesn't work since it's localhost, Fiddler is useless. I can't modify/redeploy code, but I can reset the machine if I need to.


share|improve this question
up vote 1 down vote accepted

I tracked it down by looking at the IIS error log in systemroot\System32\LogFiles\HTTPERR. There I saw that the cause of the 400 was HOSTNAME. From there I determined that localhost was being resolved to a different IP address than the one on which IIS was listening.

share|improve this answer

You can install and run NetMon on the server. It ain't the greatest thing in the world but it will let you see your traffic.

share|improve this answer
this will work for localhost requests? – MStodd Aug 3 '12 at 19:49

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.