[Samba] smbclient with lanman auth=no unable to connect

[Andrew Bartlett]

On Wed, 2004-03-17 at 03:12, Dion Sasmito wrote:
> Follow up,
> 
> Putting security = user, smbclient works. It uses NT1 (I assume).
> Changing it back to security = share, smbclient doesn't work. saying
> NT_STATUS_WRONG_PASSWORD
> 
> Maybe it's the order of things (protocol negotiation) that smbclient and smbd
> that's causing this ? 
> Or is this meant to be like this, because it's share level ?
> ie.
> ...
>  security = share
>  lanman auth = no
>  min protocol = NT1
> ...
>  [private]
> ...
>    valid users = somebody
> ...
> 
> then smbclient //fileservertest/private -U somebody
> doesn't work ?

share-level authentication uses only LM passwords.

Andrew Bartlett

-- 
Andrew Bartlett                                 abartlet at pcug.org.au
Manager, Authentication Subsystems, Samba Team  abartlet at samba.org
Student Network Administrator, Hawker College   abartlet at hawkerc.net
http://samba.org     http://build.samba.org     http://hawkerc.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.samba.org/archive/samba/attachments/20040321/212ffbc1/attachment.bin