Windows Authentication

Question

Good Morning,

First sorry, this is my second post about the same subject, the first time I didn't post the question in the right forum ! :(

Here is the scenario, on my Domain network I have a Sql server 2008 installed on a Windows 2008 server R2. I have an application who is using DBLIBRARY APIS (NTWDBLIB.DLL), I know it's OLD ! :). If I launch the software from a Windows XP pro or Windows Vista I can connect to the SQL SERVER 2008 remotly with the Windows authentication mode, If I lunch the software from a Windows 7 computer DBOPEN() always return error 2 (server not found). If I set a SQL user and try to commect in SQL authentication mode it's working on ALL computer.

So my question is do I have to do something special in my Windows 7 computer to get Windows authentication work ? or wich version of NTWDBLIB.DLL work with Windows 7, I think the problem come from inpersonnation but I'm not sure !

Thanks for any clue !

Sylvain

Answer 1

 Here is additionnal information if it can help. This is what I have in the LOG of my Sql server when I tried to connect from my Windows 7 PC in Windows authetication mode:

First MEssage:

Date  3/23/2010 11:37:28 AM
Log  SQL Server (Current - 3/23/2010 11:35:00 AM)

Source  Logon

Message
Error: 17836, Severity: 20, State: 17.

Second message:

Date  3/23/2010 11:37:28 AM
Log  SQL Server (Current - 3/23/2010 11:35:00 AM)

Source  Logon

Message
Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library. [CLIENT: 192.168.0.131]

Hope someone can give me a clue :)

Best regards,

Sylvain

Answer 2

I'm currently running into the same issue.  Did you ever find a fix for this?

Answer 3

I was able to resolve this situation by changing the security policy of the Windows 7 machine.  If you open the policy editor, you can go to local policies > security > network security: LAN Manager.  By default windows 7 uses NTLMv2, which I don't think is supported by either SQL 2005 or Windows 2003.  Anyway, change that to allow LM and NTLM and you should be good!