September 02, 2010     |
Network Toaster
SQL Security Forums
Note: SQLSecurity.com does not allow nor require registration due to privacy concerns for users. SQLSecurity.com is open and anonymous for all. Please report any abuse or profanity.
Subject: Encrypted Multiprotocols connections
Prev Next

Author Messages
Sid

10/17/2001 6:51 PM Quote Reply Alert 
I've configured SQL Server 7 to use the encrypted Multiprotocols library. I've also configured an IIS Web server to connect using Multiprotocol encryption. When a client is querying a DB on SQL server thru the website, a TCP/IP connections is open between the IIS Web server and the SQL server. Once the client disconnect, the TCP/IP connection is left open. The connection remain open until I stop the SQL Server Service. I've also, tried setting the connection time-out in IIS to 30 seconds and disabled the "HTTP Keep Alive" setting, which had no effect on the SQL connections. What other application is managing the client connection beside IIS? Is there a timeout setting for Multiprotocols in SQL Server 7?
Chip Andrews

10/18/2001 4:02 PM Quote Reply Alert 
This behavior is do to ADO and SQL Server interactivity - not IIS. IIS talks to SQL Server through ADO (assuming this is your mechanism) and ADO attempts to keep the connection open for pooling purposes. If you want to change this behavior then consult your connectivity documentation or see this article for a starting point: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmdac/html/pooling2.asp

Forums > Discussions > SQL Server Security > Encrypted Multiprotocols connections

Quick Reply
Username:  
Subject:  
Body:
 



ActiveForums 3.6
Copyright 1999 by Chip Andrews   |  Privacy Statement  |  Terms Of Use