[Samba] Fail to create samba user Q01

[Zouming]

Hi folks

   I face a problem when creating a samba user, Here is the detail:

(1)     Phenomenon

I have created a linux user q01, Q01, and samba user q01,and then, when I created the samba user Q01,I ran into a problem:

I use “smbpasswd –a Q01” to create samba user Q01, command line returned successfully, but in fact the samba user has not been created.

I can not query the user with the “pdbedit –L”



(2)     Analysis

I set samba level = 10,and I saw some problems from log.The following is part of the log information whe I excute “smbpasswd –a Q01”:





db_open_ctdb: opened database 'g_lock.tdb' with dbid 0x4d2a432b

db_open_ctdb: opened database 'passdb.tdb' with dbid 0x3ef19640

tdbsam_open: successfully opened /var/lib/samba/private/passdb.tdb

pdb_set_username: setting username q01, was

pdb_set_domain: setting domain ONESTOR, was

pdb_set_nt_username: setting nt username , was

pdb_set_full_name: setting full name , was

Home server: onestor

pdb_set_homedir: setting home dir \\onestor\q01<file:///\\onestor\q01>, was

pdb_set_dir_drive: setting dir drive , was NULL

pdb_set_logon_script: setting logon script , was

Home server: onestor

pdb_set_profile_path: setting profile path \\onestor\q01\profile<file:///\\onestor\q01\profile>, was

pdb_set_workstations: setting workstations , was

ctdbd_control: Sending ctdb packet

ctdbd_control: Sending ctdb packet

ctdbd_control: Sending ctdb packet

ctdbd_control: Sending ctdb packet

ctdbd_control: Sending ctdb packet

ctdbd_control: Sending ctdb packet

db_open_ctdb: opened database 'g_lock.tdb' with dbid 0x4d2a432b

db_open_ctdb: opened database 'account_policy.tdb' with dbid 0x2ca251cf

account_policy_get: name: password history, val: 0

pdb_set_user_sid: setting user sid S-1-5-21-1-1-1-1005

pdb_set_user_sid_from_rid:

setting user sid S-1-5-21-1-1-1-1005 from rid 1005

account_policy_get: name: maximum password age, val: -1

Finding user q01

Trying _Get_Pwnam(), username as lowercase is q01

Get_Pwnam_internals did find user [q01]!





I made a number of attempts when I created a samba user that contains uppercase letters,such as Q03, which displays the log information as follows:



db_open_ctdb: opened database 'g_lock.tdb' with dbid 0x4d2a432b

db_open_ctdb: opened database 'passdb.tdb' with dbid 0x3ef19640

tdbsam_open: successfully opened /var/lib/samba/private/passdb.tdb

pdb_getsampwnam (TDB): error fetching database.

Key: USER_q03

Finding user Q03

Trying _Get_Pwnam(), username as lowercase is q03

Trying _Get_Pwnam(), username as given is Q03

Get_Pwnam_internals did find user [Q03]!

pdb_set_username: setting username Q03, was

pdb_set_full_name: setting full name , was

pdb_set_domain: setting domain ONESTOR, was

Home server: onestor

pdb_set_profile_path: setting profile path \\onestor\Q03\profile<file:///\\onestor\Q03\profile>, was

Home server: onestor

pdb_set_homedir: setting home dir \\onestor\Q03<file:///\\onestor\Q03>, was

pdb_set_dir_drive: setting dir drive , was NULL





why does q03 appear in log when I create user Q03

therefore, it will fail to create an account if the new account name is just case-sensitive difference with the existing account name.

I expect to be familiar with samba code, please tell me the reason for the problem and how to modify it. Looking forward to you reply





Thanks

Best regards!



-------------------------------------------------------------------------------------------------------------------------------------
本邮件及其附件含有杭州华三通信技术有限公司的保密信息，仅限于发送给上面地址中列出
的个人或群组。禁止任何其他人以任何形式使用（包括但不限于全部或部分地泄露、复制、
或散发）本邮件中的信息。如果您错收了本邮件，请您立即电话或邮件通知发件人并删除本
邮件！
This e-mail and its attachments contain confidential information from H3C, which is
intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender
by phone or email immediately and delete it!