The Samba-Bugzilla – Bug 3813
User and Server Manager Broken
Last modified: 2006-06-08 07:12:29 UTC
After upgrading from 3.0.6 to 3.0.22, Windows user and server manager no longer function. Upon executing, a messagebox pops up stating "The stub received bad data". My current setup uses LDAP as the backend.
Created attachment 1921 [details]
Ethereal capture of user manager events.
Created attachment 1922 [details]
Samba log level 10 of user manager events.
Your log file and your ethereal trace don't seem to match. For example in Frame 217 of ethereal there is a SAMR querydisplayinformation call where the smb mid is 14272. In the logfile however I can not find smb_mid=14272. Are both really taken from the same sequence of events?
They were not taken from the same sequence of events. I did the ethereal capture first, and then the smb logs at a separate time. I will rerun and capture both at the exact same time.
Created attachment 1936 [details]
Concurrent ethereal capture
This ethereal capture was taken at the sames time as the srvfarm1.log level 10.
Created attachment 1937 [details]
Concurrent Samba log level 10
Log level 10 taken at the same time as the usermanager.ethereal capture.
In line 30513 of you logfile you see we search for
ou=People,dc=astroshapes,dc=com,"dc=astroshapes, dc=com"], filter => [(&(uid=*)(objectclass=sambaSamAccount))]
and it seems your ldap server does not seem to return anything from that search. Do you have your users under ou=People,dc=astroshapes,dc=com? Can you try to
ldapsearch -b ou=People,dc=astroshapes,dc=com -x '(&(uid=*)(objectclass=sambaSamAccount))' and make sure this returns your users?
On the same server that is the Samba domain controller, I run:
]# ldapsearch -b ou=People,dc=astroshapes,dc=com -x '(&(uid=*)(objectclass=sambaSamAccount))'
# filter: (&(uid=*)(objectclass=sambaSamAccount))
# requesting: ALL
<- SNIP ->
# search result
result: 0 Success
# numResponses: 180
# numEntries: 179
It seems to return all of the users. I also doesn't appear to give any errors, either. Anything else I can try?
Can you attach a sniff of the traffic between your ldap server and your Samba server?
I made a capture and the results showed what was wrong! In my smb.conf file, I had:
ldap machine suffix = ou=Computers,dc=astroshapes,dc=com
ldap user suffix = ou=People,dc=astroshapes,dc=com
ldap suffix = dc=astroshapes,dc=com
This worked in older versions of samba. Now, what was happening was it was appending the the "ldap suffix" to the "ldap user suffix" so the dn looked like:
Simply commenting out the ldap machine suffix and ldap user suffix makes all of the problems go away!
Thanks for the help!