[Samba] Re: samba 3.0.23a Cannot join network

[Sean R. Hanson]

I had the same problem after upgrading to 3.0.23a.  I have one samba PDC 
running a basic setup back to the smbpasswd file, and one that runs 
OpenLDAP.  The former did exactly as yours, and I ended up rolling back 
to version 3.0.23.  On the latter, the smb process refused to run, 
reporting that it could not contact the database.  I ended up having to 
remove all the database files and reinstall fresh files.  Luckily, that 
one is not in production mode yet, but it will be later this year.
In the log for the machine you are trying to join, I'm sure you'll have 
something like:

passdb/pdb_smbpasswd.c:build_sam_account(1202)
  build_sam_account: smbpasswd database is corrupt!  username COMPUTER$ 
with uid ### is not in unix passwd database!

The previous version has not troubles.  I'm not sure where the trouble lies.
Overall, this upgrade was a nightmare and I'm waiting for some more time 
to troubleshoot the symptoms.

Sean Hanson
Information System Support Specialist
Marmot Library Network


>>> Subject:
>>> [Samba] samba 3.0.23a Cannot join network
>>> From:
>>> mrosamba at eastgranby.k12.ct.us
>>> Date:
>>> Wed, 2 Aug 2006 16:30:40 -0400 (EDT)
>>> To:
>>> samba at lists.samba.org
>>>
>>> To:
>>> samba at lists.samba.org
>>>
>>>
>>> Today, I updated our samba PDC from 3.0.22-1.fc5 to 3.0.23a-1.fc5.1 and I
>>> can no longer add XP Pro PC's to the domain.  I am still using the
>>> smbpasswd support.  Prior to this update(this morning), I had no problem
>>> adding PC's to the domain.  The message that I get at the client is "The
>>> user name cannot be found".  I see that the passwd file has been updated
>>> with the machine name and the smbpasswd file has also been updated with
>>> the machine name.  However, in the entry in the smbpasswd file, there is
>>> no password information in either password field.  I would expect that the
>>> second password field would have a password in it.
>>>
>>> The first two entries were created with 22 while the last was created with
>>> 23a with the error message at the client.
>>>
>>> crxp15$:2109:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:5C3C18C8FA7E287A00EC5120384D0F8E:[W
>>>          ]:LCT-44D0ED49:
>>> crxp16$:2110:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:6ED17F35BD8C6E658C376829E5516156:[W
>>>          ]:LCT-44D0ED83:
>>> TEGX260XPXX$:2111:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX:[DW
>>>         ]:LCT-00000000:
>>>
>>>
>>> I ended up bringing down the server and bringing up it's backup (it's
>>> summer and no one is at school right now) which still had 3.0.22-1.fc5 on
>>> it and had no problem with the PC joining the domain.  The smb.conf file
>>> has not changed for several months.  Also, selinux is in permissive mode
>>> on 23a.
>>>
>>> Any help is appreciated.
>>>
>>> Mark Orenstein
>>> East Granby, CT, USA School System
>>>
>>>
>>>       
>>>