I want to capture all IIS traffic (from and to) "on the server." I don't know how to make that clearer. :]
It is a dev server.
I hate to phrase it this way, but I want Fiddler to do what Wireshark "just does." I realize Wireshark is not a proxy. The proxy part of Fiddler can be a real challenge at times. (I know you've commented on so many people saying "I followed the instructions, but it just doesn't work." Today, that became me.) If I want Fiddler to do (far better) what any browser's dev toolbar "just does," Fiddler is fairly easy to set up. If I want Fiddler to "serve me" as a server-side developer, the proxy is a real hassle--due to Microsoft's choices, no fault of Fiddler's, but I still feel the pain. I can't find a single document online that has working instructions (for my current setup), partly because there are so many variables, for the proxy to deal with. Fiddler "version" (2 v. 4), OS version, IIS version, AppPool account, other AppPool settings (Load User Profile), directory permissions, bitness (32- or 64-), various file proxy settings (ignore local--understanding local, loopback, override, machinename, restarting services, lions, tigers, bears--oh my), etc. I think a full flow-chart would look like a worse version of the old Florida voters' ballot joke (http://0.tqn.com/d/politicalhumor/1/S/L/_/florida_confusing_ballot.jpg). Ugh. Have I mentioned that Wireshark just works? You know I love Fiddler. I don't want Wireshark packets; I want Fiddler sessions. Can I get a WinPcap Fiddler option?! :]
I'm now on Windows 8.1, with Hyper-V, which makes my machine's IP come from a virtual network, even though I'm the host OS. Good grief. I did this so easily in previous OS versions. Now, nothing works. I can't get my ASP.Net app to break when I set an invalid proxy address. Again, not Fiddler's fault, but I'm only dealing with it because Fiddler is a proxy.