Can't Connect Data Source in ODBC to SQL 2005 Server -- "SSL Security Error"

I have two servers, clustered, mirror images of each other, running Windows 2003 Server, IIS 6.0.

I have a DNS connection setup on BOTH servers going to a SQL 2000 / Win 2000 Server machine that needs to change and point to an entirely new database on a SQL 2005/Win 2003 Server.

Here is my problem:
Server A connects to the new server just fine, no problems whatsoever.
Server B gives me an error message after I change the servername, and enter in my username\pwd while setting up the DNS.  The error reads:

Connection failed:
SQLState: '01000'
[Microsoft][ODBC SQL Server Driver][TCP\IP Sockets]ConnectionOpen (SECCreateCredentials()).
Connection failed:
SQLState '08001'
SQL Server Error: 18
[Microsoft][ODBC SQL Server Driver][TCP\IP Sockets] SSL Security error

There are no error messages in the log files on computer manager or IIS.
Nothing is being written to the trace log file when I enable tracing in the Client Network Utility.
There are no SSL certs installed on either server.
The port number is correct.
All 4 servers involved are in the same domain.
I'm using the correct username/password and it has been verified that the SQL Server permissions are setup correctly (and confirmed b/c Server A can connect and run fine).
I can open a command prompt and telnet to the SQL Server as well as ping it from my IIS web server.

Any suggestions / recommendations are appreciated!  

It seems the problem has to be on the Web Server side since Server A is connecting OK, I just don't know where to look next.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Seems strange since you've got it working on the one server...

A few questions:
1. Do you have client tools (2005 management studio or 2000 query analyser) installed on Server A? If so, can you connect to the SQL server using this (of course using the same credentials you're using in the connection setup)?
2. "I have a DNS connection setup", I'm guessing you mean DSN not DNS can you confirm? Do you use a specific tool for doing this setup or just the std MS ODBC data source administrator?
3. Since you refer to the username/password I assume you're using SQL mode authentication, please confirm.
4. Are the two connections connecting to the same database on the server and are you using the same username/pwd on both?
Sorry, on seeing that again, question 1 should be: o you have client tools (2005 management studio or 2000 query analyser) installed on Server B? If so, can you connect to the SQL server using this (of course using the same credentials you're using in the connection setup)?
LuckyDuck5281Author Commented:

1. No, I do not have these tools installed.
2. I do mean DSN, sorry about that... I was typing too fast apparently  I am using the std MS ODBC Data source administrator
3. Yes, SQL mode authentication is used.
4. Yes, each Web Server is trying to go after the same Database.  This has never been an issue in the past or in other clustered web environments that we have set up the same/similar.  The same username/pwd is being used each time.

Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

David ToddSenior DBACommented:

If using DSN, and you using user or system DSN?

In other words, duplicate DSN's can exist - one in system, another in user, etc.

Make sure that there isn't a DSN of the same name that is still pointing to the old system - in one of the other DSN categories.

LuckyDuck5281Author Commented:
We called MS on this one... after two week sof troubleshooting there was a registry key missing.
David ToddSenior DBACommented:

Glad to hear that its working.


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
What was the registry key?
Jonathan LizanoCommented:
I have the same problem, with another versions of SQL, but the same diagnostic...
Anyone have the registry key that was missing?
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server 2005

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.