title: WCF client getting a TimeoutException (and I AM closing my connections)
body: <p>Here's the thing...
  I've been working on this issue for a long time now with no luck</p>
  
  <p>I have a WCF service hosted on IIS (I also tried in a console host and I get the same behavior) which I call thru my scvutil created proxy, and the service fails to respond after a few (very few calls).</p>
  
  <p>But, here are a few clues:<br>
  1- It only happens on the testing environment (not with the services hosted on my dev machine), figures!<br>
  2- I call the service asynchronously (client.MyServiceAsync)<br>
  3- this is the trickiest one... if I run fiddler to see what's going on, the client works and never fails, unitl of course, I close fiddler (without even restarting the client)</p>
  
  <p>I have no clue so far what's going on. I started to think maybe the server (a Win2003) has some kind of "defender" which blocks further connections, could that be possible? Please trust me when I say I do close the clients after every call, actually after I get the response from the server since I'm using ascynchronous calls.</p>
  
  <p>Any tip or advice would be more than appreciated.
  regards,</p>
  
  <p>Edit: I thought this could be usefull info:
  I have enabled tracing at both ends with no luck.<br>
  At the server side I see the connections coming and going... and at some point there are no more connection coming in. While at the client side I see connection working until one of them throws a TimeoutException... that's all I get</p>