"David Morgan" <David....@BuzzSolutions.co.uk> wrote in message news:O2Cqu3PQBHA.1524@tkmsftngp05...
"Chris De Herrera, MS-MVP/Mobile Devices" <ch...@cewindows.net> wrote in message news:uqyKl9QQBHA.1860@tkmsftngp03...
Hi Brian
Yes I was, but unfortunately, now no NT 4 Workstations can connect to the W2K SQL Server 2K Machine.
I installed Certification Authority on the same server that is used for SQL Replication. Created a root certificate and then created a certificate from IIS Admin for the Default Website. Did the rootcert thing for my CA's Certificate. I was then able to replicate using SSL with no problems.
I am using W2K Pro. and was able to continue to connect the SQL Server in question for Enterprise Manager etc.
Unfortunately, my colleagues that are using NT Workstation are no longer able to. They get the following message:
A connection could not be established to [Server Name]
Reason: SSL Security Error
ConnectionWrite (SECEncryptData())..
Please verify SQL Server is running and check your SQL Server registration properties (by right-clicking on the [Server Name] node) and try again.
Having searched the news groups for this, I can only find one previous reference to this problem, (http://groups.google.com/groups?q=SECEncryptData()&hl=en&rnum=1&selm=OZLVeoBOAHA.298%40cppssbbsa05), unfortunately the guy never had a response.
I would be very grateful if you could shed any light on this issue now, as it does not just affect Ent Mngr, but any method of connecting to SQL Server using NT 4.0. (OLE-DB Connection String from VB 6 App!).
Kind regards
David Morgan
"Brian Sabino" <BrianS...@Microsoft.com> wrote in message news:uFAD83XQBHA.1544@tkmsftngp05...
"Kevin J. Boske" <kboske...@microsoft.com> wrote in message news:ey6cLqWQBHA.1584@tkmsftngp03...