We figured out that when using windows 7 as an smb client against an third party smb server, the ansi and unicode passwords are the same. The ansi password has the same value as the unicode password. Unfortunately we need the correct value of the smb.ansi_password. We configured the usage of LM and NTLM responses. With Windows XP, the values of the ansi and unicode password (for the same password with the same challenge key!) are different - the ansi password is correct. Is there any way how one can configure windows 7 so that the right ansi password is passed ? Thanks in advance, Toni

I did some more researching on this topic. (Interesting links: http://ubiqx.org/cifs/SMB.html#SMB.8 , http://download.microsoft.com/download/a/e/6/ae6e4142-aa58-45c6-8dcf-a657e5900cd3/%5BMS-SMB%5D.pdf ) The terms ansi and unicode password are only used by smb packet tracking tool (ethereal, wireshark). The internal names for this terms are CaseInsensitivePassword (ansi) and CaseSensitivePassword (unicode) where the CaseInsensitivePassword field should contain the value of the LmChallengeResponse field from the AUTHENTICATE_MESSAGE and the CaseSensitivePassword field the value of the NtChallengeResponse. Well.. that explains much more. That would mean, that instead of the LmChallengeResponse the NtChallengeResponse is passed with windows 7. Can one confirm this behaviour? Is this a bug? Thanks in advance, Toni

Hi, Considering this is a development related question, it is recommended that you go to our MSDN forum for help: Microsoft Developer Network Forums Home Hope this helps. Thanks.Nicholas Li - MSFT

Hi, I have the same problem with a Windows 7 client trying to join a samba 2.x DC. Any solution so far? Thanks in advance, Thomas