similar to: Samba4 alpha 19 confusion

Hello After running upgade provision : [root at dc1 source4]# scripting/bin/upgradeprovision -s /usr/local/samba/etc/smb.conf I got error message : Traceback (most recent call last): File "scripting/bin/upgradeprovision", line 36, in ? import ldb ImportError: No module named ldb and ...bin/python/ldb.so not exist in source4 Actually no bin directory in source4 Is this

Hi! I have recently upgraded samba4 to the latest GIT build. I have run upgradeprovision according to upgrading-samba4.txt instructions. All seems to be well, but when i try to access Group Policy Objects from gpmc utility on windows i get the following error message: --------------------------- Group Policy Management --------------------------- The permissions for this GPO in the SYSVOL folder

OK, there has got to be a way to work with this thing other than wiping the Domain every time an error pops up. Trying to resolve problems I did a git upgrade and: setup# /usr/local/samba/sbin/upgradeprovision Which provided the unhelpful: Found 3 domain controllers, for the moment upgradeprovision is not able to handle upgrade on domain with more than one DC, please demote the other(s)

Version 4.0.0alpha18-GIT-e75c436 Ubuntu 11.10 Built now with make clean ./configure.developer make make install samba -i -d3 gives this: ldb: unable to stat module ${PREFIX}/modules/ldb : No such file or directory ldb_wrap open of privilege.ldb samba: using 'standard' process model Unknown process model 'standard' my $PREFIX should be /usr/local/samba I think. The path is

Hi All, Does anyone know if there's a Samba 4 to Samba 4 migration process? Sounds weird, but it has a logical reason: I've a several-year-old S4 implementation, from an early Alpha (10 I think?) that hasn't been in the best of shape of late - when S4 4.0.0 arrived, I accidentally upgraded using my normal "git pull; ./configure; make; make install" procedure and instead of

I have the latest samba4 4.2 git running on centos6.4 but when I originally provisioned it I didn't include the --use-rfc2307 for AD posix attributes. I'd like to map certain AD users to unix users so should I do a samba-tool upgradeprovision --use-rfc2307 to add this option?

On Sun, 08 Apr 2018 13:34:52 +0200 Kris via samba <samba at lists.samba.org> wrote: > W dniu 2018-04-08 12:49, Rowland Penny via samba napisał(a): > > On Sun, 08 Apr 2018 12:31:26 +0200 > > Kris via samba <samba at lists.samba.org> wrote: > > > >> I should try this command sooner. Now I have made full backup and > >> something is missing: >

Originally I had a Win 2003 DC. I added a samba 4.0.0 DC to the domain, allow full replication to take place and then transferred all the roles to the samba 4.0.0 dc. Finally I removed the Windows DC from the domain. Everything has been working well. Today I upgraded from samba 4.0.0 to 4.0.3 and ran samba_upgradeprovision --full. Initially this was failing in update_present throwing an exception

We are proud to a announce another alpha release of Samba 4.0, alpha 20 THIS IS A SECURITY RELEASE for CVE-2012-2111, which impacts on users running the smbd file server from Samba4 alpha releases, but not users running the AD Domain Controller. What's new in Samba 4 alpha20 ============================= Samba 4.0 will be the next version of the Samba suite and incorporates all the

Hi Version 4.0.0alpha18-GIT-bfc7481 We are having problems in keeping this build up. samba -i is the only way we can keep samba up. samba and samba -i -M single fail under load e.g. when 2 clients log in at the same time. The samba processes are not killed. Our test resources are limited. Are there any minimum requirements? Thanks Steve

Hi After upgrading to Version 4.0.0alpha18-GIT-24ed8c5 on Ubuntu 11.10, Samba 4 no longer looks in the keytab for my nfs server entry: mount -t nfs4 foo bar --o sec=krb5 Kerberos: AS-REQ nfs/hh3.hh3.site at HH3.SITE from ipv4:192.168.1.3:53213 for krbtgt/HH3.SITE at HH3.SITE Kerberos: UNKNOWN -- nfs/hh3.hh3.site at HH3.SITE: no such entry found in hdb The nfs entry is in the keytab: klist -ke

I have a install of samba4 that I have been using on my home network for testing with one PDC and BDC on the local network and a 3rd BDC located on another network with IPSEC tunnel between the two networks. The problem I have is all 3 servers are running different versions on the samba4 code I would like to get all the system on the same code level. Do any of you know an easy way to

I don't know exactly, but there were problems with indexes ( as the user said ). We did not try with the current release and our manager wants to go back to Microsoft :-( Our samba version is 4.7.5. I've been able to go one step further. We first were not able to join a Windows 2008 R2 as a domain controller because it was asking for adprep. I found the missing datas in the ldap and added

We are proud to a announce another alpha release of Samba 4. What's new in Samba 4 alpha11 ============================= Samba 4 is the ambitious next version of the Samba suite that is being developed in parallel to the stable 3.x series. The main emphasis in this branch is support for the Active Directory logon protocols used by Windows 2000 and above. Samba4 alpha11 follows on from the

Hello, I try to add a new dc to my domain, but the sysadmin installed the main dc left misconfigured dns zones that I can not remove. ¿Is it possible to provision the domain again using new samba as main dc Keeping users and passwords Of the previous dc? The current main dc runs samba 4.4. Best regards, Santiago. -- Santiago Londoño Mejía Analista de Infraestructura t. (574) 605 25

Hi everyone Version 4.0.0alpha19-GIT-40a4aea openSUSE 12.1 with bind9.8.1-SP + samba dlz I just ran make install over the top of a working build from a week ago. Everything seems to work but I get this during startup from d3: <snip> WARNING: no socket to connect to <snip> Failed to listen on 192.168.1.3:53 - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED Failed to bind to 192.168.1.3:53 TCP -

We are proud to a announce another alpha release of Samba 4.0, alpha 19 THIS IS A SECURITY RELEASE for CVE-2012-1182, which impacted on Samba4 as well. What's new in Samba 4 alpha19 ============================= Samba 4.0 will be the next version of the Samba suite and incorporates all the technology found in both the Samba4 alpha series and the stable 3.x series. The primary additional

We are proud to a announce another alpha release of Samba 4.0, alpha 21 What's new in Samba 4 alpha21 ============================= Samba 4.0 will be the next version of the Samba suite and incorporates all the technology found in both the Samba4 alpha series and the stable 3.x series. The primary additional features over Samba 3.6 are support for the Active Directory logon protocols used by

On 27/02/17 08:05, Tom Robinson via samba wrote: > On 17/02/17 07:58, Andrew Bartlett via samba wrote: >> On Fri, 2017-02-17 at 07:48 +1100, Tom Robinson via samba wrote: >>> Anyone? >> Can you please post a gdb backtrace --full? >> >> > Hi, > > I replied last week with a full backtrace but I didn't see my post come through. The email was only >

On Fri, 2017-02-17 at 07:48 +1100, Tom Robinson via samba wrote: > Anyone? Can you please post a gdb backtrace --full? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 862 bytes Desc: This is a digitally signed message part URL: