http://blogs.msdn.com/drnick/archive/2008/06/10/tracing-network-calls.aspxMany common networking problems can be diagnosed by tracing System.Net events. This is often much easier than setting up packet captures or other software, particularly if you're working on a production machine. Since tracing is a part of the framework,enCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/drnick/archive/2008/06/10/tracing-network-calls.aspx#8590196Tue, 10 Jun 2008 20:21:23 GMT91d46819-8472-40ad-a661-2c78acb4018c:8590196Nicholas Allen's Indigo Blog<p>I want to receive messages that contain a transaction and forward those messages to another service.</p> http://blogs.msdn.com/drnick/archive/2008/06/10/tracing-network-calls.aspx#8597967Sat, 14 Jun 2008 20:25:02 GMT91d46819-8472-40ad-a661-2c78acb4018c:8597967Stanislav Dvoychenko<p>Thanks for reminding about this. I put some screenshots from the ServiceTraceViewer together to show what is logged by System.Net, System.Net.Sockets and System.Net.Cache. Hopefuly it gives an idea of what source to look for what data.</p> <p><a rel="nofollow" target="_new" href="http://plainoldstan.blogspot.com/2008/06/integrating-tracing-on-network-events.html">http://plainoldstan.blogspot.com/2008/06/integrating-tracing-on-network-events.html</a></p> <p><a rel="nofollow" target="_new" href="http://plainoldstan.blogspot.com/2008/06/reviewing-events-from-systemnetcache.html">http://plainoldstan.blogspot.com/2008/06/reviewing-events-from-systemnetcache.html</a></p>