similar to: Private Key Unavailable After Domain Password Change

Hi All, Attempting to do a classicupgrade and getting this error: *Adding groups* *Importing groups* *Committing 'add groups' transaction to disk* *Adding users* *Importing users* *Adding users to groups* *Committing 'add users to groups' transaction to disk* *ERROR(<type 'exceptions.ValueError'>): uncaught exception - zero length field name in format* * File

On Sun, 16 Sep 2018 10:51:25 -0400 Bill Baird via samba <samba at lists.samba.org> wrote: > I ran the same thing with 4.8.5 and it work without any issues: > > Adding groups > Importing groups > Committing 'add groups' transaction to disk > Adding users > Importing users > Committing 'add users' transaction to disk > Adding users to groups >

On Sun, 16 Sep 2018 11:28:56 -0400 Bill Baird <Bill.Baird at phoenixmi.com> wrote: > Python is 2.6, but why wouldn't it throw an error during > configure/make? No, the python code isn't compiled. > > I'm using Amazon Linux. Would you like to raise a bug report ? Here: https://bugzilla.samba.org/ Rowland > > On Sun, Sep 16, 2018 at 11:22 AM Rowland Penny

I have dsdb_password_audit:5 & dsdb_password_json_audit:5 enabled, but I don't get the message I included. I instead get an audit log that a password was changed...but not by who. Was hoping to get more info in a single log entry, so I can track who on my staff is doing password resets and setup email alerts via my logging system. On Fri, Sep 14, 2018 at 12:49 PM Andrew Bartlett

Is there a way to translate the userSid into a human readable format, so I don't have to look it up each time? For now, my workaround for now is to set my log level to 5, but then turn lots of stuff down to 1 manually. Like this: log level = 5 tdb:1 printdrivers:1 lanman:1 smb:1 rpc_parse:1 rpc_srv:1 rpc_cli:1 passdb:1 sam:1 auth:1 winbind:1 vfs:1 idmap:1 quota:1 acls:1 locking:1 msdfs:1

Hi All, Is there a built-in command to get a list of all expired accounts, or output a list of all users and expiration date? All the scripts I find seem to be PowerShell scripts that relay on some "Web Service" that I don't have or do one user at at time. Or if anyone has a script they are willing to share, that would be greatly appreciated. I'm primarily looking for a way to

Hi All, I'm prepping for a classicupgrade and noticed that if I set log level = 5, I get a log like this when we update a password for a user: *kpasswd_samdb_set_password: DOMAIN\username(S--x-x-x-xxx-xxx-xxxx) is changing password of username at domain* I can't seem to figure out what debug class I need to enable to still get this alert, but still set my default logging to 1. Thanks

Just saw that, as well. After running the commands to enable SMB2 & SMB3 and rebooting...no luck. Will keep searching for other registry settings. On Tue, Apr 19, 2016 at 3:27 PM, lingpanda101 at gmail.com < lingpanda101 at gmail.com> wrote: > On 4/19/2016 3:24 PM, Bill Baird wrote: > > When I search for "smb2", I get nothing in my log file for the NT1 limited >

I'm seeing the exact same behavior in my environment (NT4 PDC, not AD). I had to downgrade samba get systems working again. The full error message is: "The trust relationship between this workstation and the primary domain failed". Did you have any luck finding a solution?

*testparm -v | grep "client min protocol"* client min protocol = CORE On Tue, Apr 19, 2016 at 2:50 PM, lingpanda101 at gmail.com < lingpanda101 at gmail.com> wrote: > On 4/19/2016 2:43 PM, Bill Baird wrote: > > I am accessing the new member server. All my other servers are still on > 3.6.x. > > Both settings are set to "default". > > Will look at

When I search for "smb2", I get nothing in my log file for the NT1 limited system. If it is a workstation issue, that would be great. I'll search around for what settings to change. Maybe SMB2 was inadvertently disabled. Thanks for all of your help on this! On Tue, Apr 19, 2016 at 3:20 PM, lingpanda101 at gmail.com < lingpanda101 at gmail.com> wrote: > On 4/19/2016 3:11

I am accessing the new member server. All my other servers are still on 3.6.x. Both settings are set to "default". Will look at logs now. Thanks! On Tue, Apr 19, 2016 at 2:39 PM, lingpanda101 at gmail.com < lingpanda101 at gmail.com> wrote: > On 4/19/2016 2:08 PM, Bill Baird wrote: > >> Hi All, >> >> I just setup a new server and added it to my domain

Hi All, Just curious if anyone is currently using Xen 3on any of the new Intel Xeon processors that support the VT-x extentions. With the VT-x (or AMD's Pacifica) you can run unmodified guest operating systems...so we are looking into buying a new server to run a few virtual machines of CentOS & a few with Windows. If anyone has done this, I would love to hear about their

Hi All, I am running Samba 3.6 in PDC mode (i know, i know...AD upgrade is in the works). The most recent update for CentOS 6 (samba-3.6.23-30.el6_7.x86_64) appears to have caused issues and I was forced to downgrade back to samba-3.6.23-25.el6_7.x86_64. When 3.6.23-30 is installed, users running Windows 7 x64 receive the following error when trying access shares: "The trust relationship

Hi All, Our users started having issues late last week when trying to change their passwords. They receive the following message: "The system detected a possible attempt to compromise security. Please ensure that you can contact the server that authenticated you." Client computers are running Windows 7 Ultimate & Enterprise x64. We are still running (I know, I know) and NT4-style

That does indeed show "default". For logs, I tested with my system and a system that gets SMB2. Any tips for what I might be looking for? Early on in the logs, I see this for the NT1 system (no mentions of smb2 anywhere) [2016/04/19 14:48:37.738460, 3, pid=21479, effective(0, 0), real(0, 0)] ../source3/smbd/negprot.c:395(reply_nt1) using SPNEGO [2016/04/19 14:48:37.738476, 3,

Python is 2.6, but why wouldn't it throw an error during configure/make? I'm using Amazon Linux. On Sun, Sep 16, 2018 at 11:22 AM Rowland Penny via samba < samba at lists.samba.org> wrote: > On Sun, 16 Sep 2018 10:51:25 -0400 > Bill Baird via samba <samba at lists.samba.org> wrote: > > > I ran the same thing with 4.8.5 and it work without any issues: > >

I ran the same thing with 4.8.5 and it work without any issues: Adding groups Importing groups Committing 'add groups' transaction to disk Adding users Importing users Committing 'add users' transaction to disk Adding users to groups Committing 'add users to groups' transaction to disk On Sun, Sep 16, 2018 at 10:29 AM Bill Baird <Bill.Baird at phoenixmi.com> wrote:

Hi All, I just setup a new server and added it to my domain last week and it has been working well. We are running a NT4-style Samba PDC for our domain controller. This server is running the CentOS packages for Samba 4.2.10-6 as a domain member. My issue is that I have one Windows 7 workstation that will only auto-negotiate to the NT1 protocol. If I run smbstatus, all of my other workstations use

Just to follow up, the fix for us was to add "client ipc signing = auto" to our smb.conf configuration file. On Wed, Apr 13, 2016 at 1:17 PM, Bill Baird <bill.baird at phoenixmi.com> wrote: > FYI: https://lists.samba.org/archive/samba/2016-April/199013.html > > On Wed, Apr 13, 2016 at 12:53 PM, Bill Baird <bill.baird at phoenixmi.com> > wrote: > >>