From what I can tell, this is happening when the internal connection object is being created in SqlConnection (you would get this using enterprise library or not, I believe).
There are two things I would check. First is the obvious, are you disposing of all of your connections properly? Even though you are using connection pooling, you still must call Dispose on all of your connections when you are done using them so they are returned to the pool. If not, you could be looking at a starvation issue.
If you are disposing of your connections properly, then I would look at the connection between that machine and the SQL Server, it would seem maybe you have connection problem there.
casperOne
2009-02-17 17:30:18