Koozali.org: home of the SME Server

Fun with NT machine accounts and smbpasswd

Offline Q-Ball

  • 1
  • +0/-0
Fun with NT machine accounts and smbpasswd
« on: January 04, 2011, 07:57:44 AM »
So, after recently cloning a machine to eliminate a certain restarting problem, I needed to change the name of the machine to avoid a duplicate name on the network.

My problem is this.  When trying to change the cloned machine's name back to what it was originally, the server would reject the name change- the name had been used previously from the last installation.

Trying to fix the issue apparently made it worse.  I cannot even change the name of the machine in question to something that hasn't been used before (A device attached to the system is not functioning.)

Analysis of a logfile (messages) indicates that the smbpasswd database has been corrupted (however the users and machines below the machine account in question can still log in)- a portion of the file is this (trying to rename the machine at this point).

I tried this (http://forums.contribs.org/index.php?topic=32869.0 - Error there is already a system account of that name)
I tried to make the machine account visible and deleting it from the server-manager, and also tried that from the command-line- which apparently corrupted the database.

Jan  3 22:14:27 serverone smbd[4990]: [2011/01/03 22:14:27, 0] passdb/pdb_smbpasswd.c:build_sam_account(1252)
Jan  3 22:14:27 serverone smbd[4990]:   build_sam_account: smbpasswd database is corrupt!  username LABNINE$ with uid 5053 is not in unix passwd database!
Jan  3 22:14:27 serverone smbd[4990]: [2011/01/03 22:14:27, 0] rpc_server/srv_samr_nt.c:set_user_info_21(3249)
Jan  3 22:14:27 serverone smbd[4990]:   set_user_info_21: failed to rename account: NT_STATUS_UNSUCCESSFUL

Server version is 7.5.1.  Clients are Windows XP SP3.
Is this error easily rectifiable or will it require a server rebuild?
Any ideas?

Offline bunkobugsy

  • *
  • 306
  • +4/-0
Re: Fun with NT machine accounts and smbpasswd
« Reply #1 on: January 04, 2011, 10:32:27 PM »
I don't recall ever succeding renaming a machine that is already joined in domain, some similar error.
The obvious is to remove it (restart), rename it (restart) and then join it again (then restart again).
However, afaik, old machine account won't be deleted, but didn't realy care.

You should open a bug, maybe something good will come from it (or rather something bad disappear)