Hi, we have a C# web application with SQL Server 2005 as backend database. we have not disabled connection pooling in the connection string, so by default the connection pooling should be working. we are properly opening and closing the connections. But we have noticed large number of sleeping processes(Awaiting Command) with the oldest connection sleeping is some 5 months back. Is there any configuration setting in SQL 2005 for auto-close of sleeping processes or disallow the process in sleeping state for long duration? We are getting the following for connections to the server now : SQL connection get returned error. Message:An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - Only one usage of each socket address (protocol/network address/port) is normally permitted.) SQLState : ErrorCode :  Is this due to the sleeping connections?