similar to: Cannot change SID on NTUSER.DAT file

I'm trying to move some roaming profiles from Domain A to B. All of the profiles are from XP SP3. The originating machine is Debian 5/AMD64, samba 3.4.5 from Debian packages. The destination machine is Ubuntu 9.10, but x86. From everything I've read and found online, `profiles` is supposed to work for XP with no problems. When I attempt to do a SID change on NTUSER.DAT, I get

Hi. Current host OS: CentOS5.9 Current client OS: Windows XP (all the latest stuff) Current Samba: 3.6.6-0.129.el5 Ever since 3.4 I am having problems with the "/usr/bin/profiles" binary, it does NOT allow me to change a SID within a registry file. However, using an older version of the binary (3.0.33-3.29.el5_5.1) it does. If I execute the following command (note the last 4 digits on

Hi list, I'm getting a lot of these on a CTDB cluster serving files to Windows clients: [2016/06/24 08:53:55.555485, 1] ../librpc/ndr/ndr.c:578(ndr_pull_error) ndr_pull_error(11): Pull bytes 4 (../librpc/ndr/ndr_basic.c:150) [2016/06/24 08:53:55.555506, 1] ../source3/locking/share_mode_lock.c:141(parse_share_modes) ndr_pull_share_mode_lock failed: Buffer Size Error [2016/06/24

On Tue, Jul 26, 2016 at 12:24:01PM +0100, Alex Crow wrote: > Hi list, > > I'm getting a lot of these on a CTDB cluster serving files to Windows > clients: > > [2016/06/24 08:53:55.555485, 1] ../librpc/ndr/ndr.c:578(ndr_pull_error) > ndr_pull_error(11): Pull bytes 4 (../librpc/ndr/ndr_basic.c:150) > [2016/06/24 08:53:55.555506, 1] >

Hi folks, I am trying to set up a domain/forest in VirtualBox server. My setup: * # uname -a FreeBSD bsd1dc.ad001.osipov.eu 10.3-RELEASE-p4 FreeBSD 10.3-RELEASE-p4 64 bit * Samba 4.4.5 from Ports tree # samba-tool -V 4.4.5 * Python 2 from Ports tree # python2 --version Python 2.7.12 Installation went smoothly but during domain provisioning Python fails with a segmentation fault

On Samba 4.12.0, I receive the error "ndr_pull_uint32: ndr_pull_error(Buffer Size Error): Pull bytes 4 (../../librpc/ndr/ndr_basic.c:152) at ../../librpc/ndr/ndr_basic.c:152" when opening the DNS Manager in MMC. This jumped out at me from the log-level 10 output (I'm happy to send the full logs but would rather do that somewhere more private): /dnsserver: Found DNS zone

Hi Michael, I'm facing the same problem, samba 4.4.x is apparently broken on FreeBSD for now. Here's a link to the bug https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=209787 For now the port maintainer seem out of ideas to fix this. You seems more skilled then me on freebsd, maybe you can help him on this bug :) DS On 07/20/2016 02:17 AM, Michael Osipov wrote: > Hi folks,

I'm working on building a CTDB/Samba cluster on AIX 7.1 with the latest levels to replace an older one running CTDB 1.0.113 and Samba 3.6.1. I have the new servers up and running and they seem to work, but I'm worried about some messages in the logs. I run with log level 1 on the servers so that the connection details are logged. On the old cluster there were only connection/closed

On Wed, 2020-03-04 at 18:07 +0000, Alex MacCuish via samba wrote: > On Samba 4.12.0, I receive the error "ndr_pull_uint32: > ndr_pull_error(Buffer Size Error): Pull bytes 4 > (../../librpc/ndr/ndr_basic.c:152) at > ../../librpc/ndr/ndr_basic.c:152" > when opening the DNS Manager in MMC. > > This jumped out at me from the log-level 10 output (I'm happy to >

We normally do this via attachments to bugzilla bugs restricted to the samba developers group. Start by filing a bug about this. Andrew Bartlett On Sat, 2020-03-14 at 22:30 +0000, Alex MacCuish via samba wrote: > No worries Andrew. I haven't upgraded all servers yet so it's not urgent! > > Is there a secure place I can upload my logs for when there's time to > take a

No worries Andrew. I haven't upgraded all servers yet so it's not urgent! Is there a secure place I can upload my logs for when there's time to take a look? Cheers Alex On 05/03/2020 23:21, Andrew Bartlett via samba wrote: > On Wed, 2020-03-04 at 18:07 +0000, Alex MacCuish via samba wrote: >> On Samba 4.12.0, I receive the error "ndr_pull_uint32: >>

If you can see: Privacy: Make attachment and comment private (visible only to members of the samba-devel group) then tick that, otherwise I'll have to make the bug private first and then lock the attachment and re-publish the bug.. On Sun, 2020-03-15 at 23:03 +0000, Alex MacCuish via samba wrote: > I opened bug 14310 (https://bugzilla.samba.org/show_bug.cgi?id=14310). > Are

I opened bug 14310 (https://bugzilla.samba.org/show_bug.cgi?id=14310). Are attachments I upload there already restricted or do I have to do that myself? Alex On 14/03/2020 22:38, Andrew Bartlett via samba wrote: > We normally do this via attachments to bugzilla bugs restricted to the > samba developers group. Start by filing a bug about this. > > Andrew Bartlett > > On Sat,

Adding a section of a debug level 5 log at the end that looks like it might have some usefull information. > This problem shows up on both Linux and Solaris. I am going to show > the logs from a Fedora 2.6.25-14.fc9.i686 machine. > > We are using 'security = domain' with a Windows 2000 domain controller. > We are setting 'password server = starfish2' dispite the

Hi Alex I've had the same DNS manager issue. I've opened a bug (https://bugzilla.samba.org/show_bug.cgi?id=14310) and reported on the mailing list (https://lists.samba.org/archive/samba/2020-March/228772.html) No fix yet. On 18/03/2020 15:43, Alex via samba wrote: > Rowland, > > I've encountered an issue with connecting to the samba DC's DNS service from DNS >

Rowland, I've encountered an issue with connecting to the samba DC's DNS service from DNS Manager tool (under Windows). It says "Active Directory service is not available". While digging into it, I've found the samba rpc worker throws an error: [pid 18398] geteuid() = 0 [pid 18398] write(3, "[2020/03/18 18:36:21.694834, 2]

Hello Alex, Thanks for your reply! Hope, Andrew will find some time soon and fix it. > I've had the same DNS manager issue. I've opened a bug > (https://bugzilla.samba.org/show_bug.cgi?id=14310) and reported on the > mailing list (https://lists.samba.org/archive/samba/2020-March/228772.html) > No fix yet. > On 18/03/2020 15:43, Alex via samba wrote: >> Rowland,

Hello, I am stuck with a error when setting password for a couple of specific users. This error makes impossible to set the password for the affected users. In Windows I get an operation error but the samba-tool output is more informative: samba-tool user setpassword user2 --newpassword= New Password: ndr_pull_error(11): Pull bytes 2 (../librpc/ndr/ndr_basic.c:103) ERROR: Failed to set

OK, I've traced this a little further on now. I think I have followed the trail via the following items that call or refer to each other in turn: - python samba-tool ntacl sysvolreset - source3/smbd/pysmbd.c: SMB_VFS_FSET_NT_ACL( fsp, security_info_sent, sd); - source3/include/vfs_macros.h:#define SMB_VFS_FSET_NT_ACL smb_vfs_call_fset_nt_acl - source3/smbd/vfs.c:NTSTATUS

Hello List, I'm receiving several of these messages in my samba log file. I'm not entirely sure what the errors are referencing either. I'm under the assumption DNS related. ndr_pull_error(11): Pull bytes 1 (../librpc/ndr/ndr_basic.c:81) ../librpc/rpc/dcerpc_util.c:264: ERROR: pad length mismatch. Calculated 44 got 0 I have 3 sites with 2 DC's