Bug 4333 - Workstation under NT40 can't join Samba domain
Summary: Workstation under NT40 can't join Samba domain
Status: RESOLVED FIXED
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: Domain Control (show other bugs)
Version: 3.0.23c
Hardware: x86 Linux
: P3 normal
Target Milestone: none
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-01-11 05:12 UTC by Alexandr
Modified: 2007-01-11 05:35 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexandr 2007-01-11 05:12:50 UTC
We have Samba domain on LDAP.
After updating samba from version 3.0.13 to 3.0.23 NT4 SP6a workstation can't join to domain with message: "Not possible to change registration information in domain. This user have not permissions to create or change registration information" (this is not a quotation, but translation), but Win 2000 sp6 can join without problem. This problem checked on 2.0.23a, 2.0.23b, 2.0.23c.
On Samba version 3.0.13 all works fine. This machine is already in database.

In debug messages I've found this:

Requested \PIPE\samr
api_rpcTNP: samr op 0x3a - created /tmp/in_samr_58.3.prs
api_rpcTNP: rpc command: SAMR_SET_USERINFO
api_rpc_cmds[22].fn == 0x81408e0
000000 samr_io_q_set_userinfo 
    000000 smb_io_pol_hnd pol
*******************
prs_mem_get: reading data of size 2 would overrun buffer by 1 bytes.
api_samr_set_userinfo: Unable to unmarshall SAMR_Q_SET_USERINFO.
api_rpcTNP: samr: SAMR_SET_USERINFO failed.
free_pipe_context: destroying talloc pool of size 526
process_complete_pdu: DCE/RPC fault sent on pipe lsass
set_incoming_fault: Setting fault state on pipe samr : vuid = 0x64

But in old Samba there is no any faults.
Comment 1 Björn Jacke 2007-01-11 05:35:17 UTC
I'm quite sure http://viewcvs.samba.org/cgi-bin/viewcvs.cgi?view=rev&rev=18369 fixed this. You'll have to apply that patch yourself or wait for the next 3.0 release. If it doesn't help, please reopen this bug.