similar to: Samba4 Android port and Python auth modules

On Thu, Jan 15, 2015 at 10:40:00PM +0000, Kaye, John wrote: > Hello All, > > First post. Just ported Samba4 to a native Android/ARM platform -- quite a bit more work than Samba3. Moved to Samba4 to pick up AD support. > > The smb and nmb daemons fire up and appear to operate correctly, at least as good as Samba3. However, when trying to use samba-tool to create/list users, etc. I

Hello, i try to upgrade a NT4-PDC to AD. OS: Debian 10.1 Samba: 4.9.5-Debian read https://wiki.samba.org/index.php/Migrating_a_Samba_NT4_Domain_to_Samba_AD_(Classic_Upgrade) scp -r /var/lib/samba/private/ /var/lib/samba/samba3tdb/ scp /etc/samba/smb.conf /var/lib/samba/samba3tdb/ samba-tool domain classicupgrade --dbdir=/var/lib/samba/samba3tdb/ --realm=samdom.example.com

Following the wiki replication guide precisely I got to this step. [root at smb4-2 ~ (master)]# rsync -XAavz --delete-after smb4-1.brockley.harte-lyne.ca:/var/db/samba4/sysvol/ /var/db/samba4/sysvol/ receiving file list ... done ./ brockley.harte-lyne.ca/ . . . brockley.harte-lyne.ca/scripts/ sent 142 bytes received 1,683 bytes 3,650.00 bytes/sec total size is 182 speedup is 0.10 [root at

Hello, I am using Samba 4.0.5 and got this kind of error messages in samba.log (loglevel 2). While this happens getent passwd shows no domain users, but everyone could reach all of the shares. Any idea what could cause this kind of error messages? [2013/11/21 15:53:15.736390, 1] ../source3/smbd/sesssetup.c:276(reply_sesssetup_and_X_spnego) Failed to generate session_info (user and group

Hi I'm still exploring the R programming universe, so if this is being asked in the wrong place, or in the wrong way (e.g. too verbose or lacking in crucial detail or in the wrong format) please let me know I am trying to understand when the version constraints for packages which appear in the Imports field of a DESCRIPTION file are checked. Along the way I've hit a snag

I've been trying to run samba4 alpha11 on a FreeBSD 8.1 system as a domain controller but I'm having trouble starting the cldapd server. For some reason it won't bind to the specified address or interface whatever I specify in smb.conf. I managed running the provision script without any trouble but I have no clue how to solve this problem in order to start the samba server. bitrot#

Many thanks Duncan for the quick response. A bug is a relief in a way. I've been digging my way deeper into this (and learning more as I go) for several days now - but it is a diversion from (a diversion from) my main goal :-( Is there somewhere specific I should report or log the bug or will that happen from this mailing-list automatically? (I have seen the Bug Tracking link on the

Hi everyone After almost 2 days up-time with Samba 4, it failed again. This time it simply will not restart. The krb5.conf had got corrupted. I replaced it with this one from /usr/local/samba/private /etc/krb5.conf [libdefaults] default_realm = HH3.SITE dns_lookup_realm = false dns_lookup_kdc = true It starts up OK: samba -i -d 3 lpcfg_load: refreshing parameters from

Hi, I am finally revisiting my sysvol share (GPOs haven't been working for me for quite some time) and trying to get permissions sorted properly on it. For many years, "samba-tool ntacl sysvolreset" has always failed for me with errors that I have been unable to solve. Previously I have used guidance from Louis and got things working, but my sysvol is currently in a broken state.

Then I don't know what caused it. I had no problems prior to the upgrade, and the upgrade was done without errors.. Unfortunately, no, I don't have backups. 'sam.ldb' is still there, though, and so are the databases unter 'sam.ldb.d'. Yes, I tried restarting Samba, even rebooted the server but to no avail. Here are the results from running samba in the shell: lpcfg_load:

Hi Duncan The difference is that in your call to loadNamespace, the versionCheck list has 3 components (name, op and version), whereas the documentation only mentions 2 (op and version). loadNamespace 'works' for me provided I add a third component to the list (even a nonsense one). What I haven't yet had the fortitude to do is track down through the code to see what the arguments

On 14/02/15 19:45, Steve Ankeny wrote: > answers below > > On 02/14/2015 02:10 PM, Rowland Penny wrote: >> On 14/02/15 18:05, Steve Ankeny wrote: >>> answers below >>> >>> On 02/14/2015 08:22 AM, Rowland Penny wrote: >>> >>> I've made that change with no change in the results. I've also >>> started 'winbind'

Hello to the Samba Mailing List, This is my first post, so please, should I commit any faux pas, nudge me in the right direction and I will adjust accordingly. I'm experiencing a complete failure of the PDC in a Samba 4 AD Domain I've deployed for a client. Samba failed a few days ago and I've been unable to resolve the issue on my own. Google searches are leading me in circles,

On Wed, 17 Jul 2019 at 17:58, Rowland penny via samba <samba at lists.samba.org> wrote: > > On 17/07/2019 17:43, Kris Lou via samba wrote: > > I had thought that the conventional wisdom was that ntacl sysvolreset > > should be mostly avoided once relative stability achieved and additional > > GPO's created. > > > >

On 15/06/15 14:01, L.P.H. van Belle wrote: > and just a comment.. > > when i look at : > http://inverse.ca/ubuntu-nightly/dists/trusty/trusty/binary-amd64/Packages > /search for : 2:4.1.18+dfsg-3~inverse1 > Replaces: libpam-winbind (<< 2:3.6.5-2), samba (<= 2.2.3-2), winbind (<< 2:3.5.11~dfsg-3), winbind4 > => winbind4.. > > this all is build agains the

Hi Duncan, Many thanks (yet again). With the hint given by your earlier email (viz that currently loadNamespace expects a 3rd component called name in the list that is used for the versionCheck argument) I had another look at what was going on with my toy examples yesterday evening. I'm still working on my issue, but thus far I have: 1) Confirmed that internal calls to loadNamespace

I have a "Samba | SOGo | OpenChange" server running in VMware. I get the following message when running 'apt-get upgrade' -- The following packages have been kept back: libldb-dev libldb1 libmapi0 libmapiproxy0 libmapistore0 libnss-winbind libpam-winbind libsmbclient libwbclient0 openchangeproxy openchangeserver python-ldb python-ocsmanager python-samba samba

On 10/10/2015 09:05 AM, Rowland Penny wrote: > On 10/10/15 13:44, Steve Ankeny wrote: >> I have an existing Samba-AD-DC built from Inverse packages, >> v.4.1.18+dfsg-3~inverse1 >> >> I have OpenChangeServer installed on that machine, v.2.4-zentyal6 >> >> When I start OpenChange, it "shuts down" my Samba-AD-DC so that no >> one can login.

Hello guys, It is possible to work with the "dns-backend = SAMBA_INTERNAL" in Samba4 NT4 style? I followed the link below, but there was some errors. https://wiki.samba.org/index.php/Changing_the_DNS_backend Errors: *# samba_upgradedns --dns-backend=SAMBA_INTERNAL* *lpcfg_load: refreshing parameters from /etc/samba/smb.conf* *params.c:pm_process() - Processing configuration file

Hi I got some strange issues on my samba4.0.1 install yesterday. It happened a while after updating my xubuntu server 13.04 not 13.10. Everything seems to be working fine except shares. Kerberos authentication seem to function properly, also DNS works fine but shares seem semi-broken. I can't mount any shares on my Windows box, including netlogon, profiles. I have one share that is