If smbpasswd already has an entry for UsEr, then smbpasswd -a uSeR with a new password will overwrite the UsEr entry rather than creating a new one for uSeR. Demonstrated: [root@err samba]# cat smbpasswd mark:500:7AF3DE1E1D6C5927B8FCC6137C839435:F5B57AF6A5E35726D5087508AD5D5969:[U ]:LCT-44F6FA94: [root@err samba]# smbpasswd -a Mark New SMB password: Retype new SMB password: [root@err samba]# cat smbpasswd mark:500:B267DF22CB945E3EAAD3B435B51404EE:36AA83BDCAB3C9FDAF321CA42A31C3FC:[U ]:LCT-44F6FBD7: [root@err samba]# cat /dev/null > ./smbpasswd [root@err samba]# smbpasswd -a Mark New SMB password: Retype new SMB password: Added user Mark. [root@err samba]# cat smbpasswd Mark:501:B267DF22CB945E3EAAD3B435B51404EE:36AA83BDCAB3C9FDAF321CA42A31C3FC:[U ]:LCT-44F6FBFA: [root@err samba]# smbpasswd -a mark New SMB password: Retype new SMB password: [root@err samba]# cat smbpasswd Mark:501:6B9C36DEAC41F541AAD3B435B51404EE:973AFC7D700ADB85BECD0ABB59F690B7:[U ]:LCT-44F6FC6C:
Mark, This is by design since Windows usernames are case insensitive.