Koozali.org: home of the SME Server

smbpasswd database is corrupt

prob

smbpasswd database is corrupt
« on: October 26, 2003, 11:25:59 AM »
I have this error in the samba log.  It may have been caused by my recent upgrade from 5.6 to 6.0b3

Anyway, the problem now is that I can't log a Windows 2000 PC onto the E-smith server, the Windows message  is the "Specified user does not exist" after I give admin as the user with permission to add to PC to the server.


Thoughts?

Paul

Charlie Brady

Report bugs to smebugs@mitel.com (was Re: smbpasswd database
« Reply #1 on: October 26, 2003, 07:26:35 PM »
prob wrote:
 
> I have this error in the samba log.  It may have been caused
> by my recent upgrade from 5.6 to 6.0b3

As has been said here scores of times, report all malfunctions to smebugs@mitel.com. Be sure to apply all updates and follow the usual post-update procedure first.

Charlie

prob

Re: Report bugs to smebugs@mitel.com (was Re: smbpasswd data
« Reply #2 on: October 26, 2003, 09:02:04 PM »
noted Charlie, but I understand that the smbpasswd database can become corrupted for a variety of reasons (not just through an upgrade) and I was interested in any thoughts on how to fix it.

I see other users have had success in recovering the database from a backup, so I will try that.

Paul Robertson

Re: Report bugs to smebugs@mitel.com (was Re: smbpasswd data
« Reply #3 on: October 27, 2003, 11:09:48 AM »
Fixed the problem, here's how.

1. Looked in SAMBA log for machine I was logging in from and saw entrys saying that the machine name wasn't recognised.

2. Followed SAMBA howto by Darrell May at http://mirror.contribs.org/smeserver/contribs/dmay/mitel/howto/samba-howto.html and deleted the machine name entries for the 2 PC's in the network. I also saw reference in the log to an alternative name for one of the PC's I used when trying to join the domain which I also deleted

3. Rebooted the client PC and logged in successfully as a user. Unfortunately Windows had trouble with the roaming profile (new profile directory started with a 000 suffix) Pulled out the network cable and logged out (so e-smith server copy of the profile not corrupted), logged in as local administrator, and added user as a user on the domain (with admin rights which seems to be necessary)

4. Logged off and administrator and back on as user, success.


Life is good again.