TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to [EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems! ----------------------------------------------------------------------------
Sharon, There is a gotcha with multi-protocol encryption that I ran into - it did not work! I messed around until I hit upon a registry key which seemed to do the trick. Below is an exercise from our Advanced RealSecure class where we take them through enabling encryption. The exercise is written to deal with RS but you can do the same for SSD. This is not supported so use at your own risk (you can always take it out if you have problems. Cheers John Gay ISS X-force Education To remove TCP/IP and add multi-protocol encryption: 1. From the Windows Start menu, select Programs->Microsoft SQL Server->Server Network Utility. 2. In the SQL Server Network Utility dialog, select TCP/IP and click Disable. 3. Select Named Pipes and click Disable. 4. Select Multiprotocol and click Enable. 5. Select Multiprotocol and click the Properties button. 6. Enable the Enable encryption checkbox and click OK. 7. Click OK. 8. To save the changes, click OK. 9. Select Start->Run and in the Open field type regedit. Click OK. 10. In the Registry Editor window, open the folders HKEY_LOCAL_MACHINE->SOFTWARE->Microsoft->MSSQL Server->MSSQL Server->RPCNetlib. 11. Double-click the Security value name. 12. In the Edit String dialog, in the Value data field, type Encrypt. 13. Click OK. 14. Close the Registry Editor window. 15. In the systems tray, right-click the SQL Service Manager. Stop and then restart the SQL Service. This part was written for Event Collector to Database information but would apply to anyone who communicates to the SSD ISSED DB. 1. Close the RealSecure Console. 2. From the Windows Start menu, select Programs->Administrative Tools->Data Sources (ODBC). 3. Click the System DSN tab. 4. Select RSNTAsset60 and click Configure. 5. In the first Microsoft SQL Server DSN Configuration dialog, click Next. 6. In the next Microsoft SQL Server DSN Configuration dialog, click Client Configuration. 7. Enable the Multiprotocol radio button and click OK. 8. In the next Microsoft SQL Server DSN Configuration dialog, click Next. 9. In the next Microsoft SQL Server DSN Configuration dialog, click Next. 10. In the next Microsoft SQL Server DSN Configuration dialog, click Finish. 11. In the ODBC Microsoft SQL Server Setup dialog, click Test Data Source. 12. If configured properly, you will receive "TEST COMPLETED SUCCESSFULLY!" message. Click OK. 13. Click OK. 14. Repeat steps 3-6 to verify that Multiprotocol is enabled for both RSNTEvent60 and RSNTEventCollector. -----Original Message----- From: Kucyk, Sharon L To: '[EMAIL PROTECTED]' Sent: 7/29/02 4:17 PM Subject: Encrypted Protocol for SQL Server 2000 TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to [EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems! ------------------------------------------------------------------------ ---- I recently installed SafeSuite Decisions on a Windows 2000 platform using SQL Server 2000. I tried to set up secure communications using Multiprotocol, enabling encryption, but was not able to get this to work. I set the protocol under the SQL Server Network Utility, then tried to set up the client's ODBC connection for Multiprotocol with strong encryption. The connection failed when tested. I was told that Multiprotocol is not supported for SQL Server 2000. I need to enable encryption as I cannot have clear text being sent through the network. Does anyone know how to set up secure communication for SQL Server 2000? Sharon Kucyk
