similar to: Samba Migration and AD integration

Hi Andrew, The realm infact has no dots, is this going be an issue? It is different to workgroup. The details did get "Lost in Redaction" Coming back to the DNS. When we did the domain migration , we used --dns-backend=BIND9_DLZ. My assumption was it will stick to the BIND_DLZ. Anyhow, when we use the default settings post migration, we are not able to DCPROMO the Server 2008R2 server.

I just tested Samba 4.9.2 on one of my DCs, previously running version 4.8.6. Immediately after install, I ran "samba-tool dbcheck" and got the following: Checking 511 objects ERROR(<type 'exceptions.UnicodeDecodeError'>): uncaught exception - 'ascii' codec can't decode byte 0xc3 in position 25: ordinal not in range(128)   File

Hello, we have 2 DC with Sernet Samba-packages 4.9.4 if we do a "samba-tool dbcheck" we get the following error: ---------- samba-tool dbcheck Checking 1631 objects ERROR(<type 'exceptions.UnicodeDecodeError'>): uncaught exception - 'ascii' codec can't decode byte 0xc3 in position 29: ordinal not in range(128) File

I decided to give Samba 4.9.x a new try as AD DC in one of my servers. It has been running version 4.8.9. I installed version 4.9.4 and when I ran samba-tool dbcheck I still obtained the following error message: ERROR(<type 'exceptions.UnicodeDecodeError'>): uncaught exception - 'ascii' codec can't decode byte 0xc3 in position 25: ordinal not in range(128)   File

On Tue, 2018-02-06 at 03:05 +0000, Praveen Ghimire via samba wrote: > Hi, > > We migrated from Samba 3 to 4 (4.6.7-Ubuntu) and added promoted a > Server 2008R2 as a Domain Controller. We've come across the following > issues and request some suggestions to resolve them > > > - The migration didn't generate DNS entries for the new > realm. We had to

Hi Louis, Am 28.02.2019 12:47, schrieb L.P.H. van Belle via samba: > Hai Stefan, > > See. > https://bugzilla.samba.org/show_bug.cgi?id=13616 > That's what I found, too. We did not do an update it's a fresh installation (migrate from samb3 with classicupgrade). I now did a "samba-tool dbcheck -v " and I see that the "ü" in the DN of a OU it's the

dpkg -l |grep ldb You want to see : libldb1 I think its 1.4.3 you will see, thats the version im having also atm. The bugnr is not in the release notes, so i expect this in the next release to be corrected. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Stefan Kania via samba > Verzonden: donderdag 28

Hi Rowland, Thank you. Yes to the first point. We are using Bind9 but to continue using it is not necessarily set in stone. If using Samba Internal DNS makes more sense then we can do that too. The question is do we need to do dns-upgrade and use Internal DNS, pre-migration? Then use internal dns during the classic migration? Also, I assume the bind9 service will have to stopped if infact we

On Mon, 2018-11-12 at 20:36 +0000, Noel Power wrote: > Hi > > On 09/11/2018 10:21, Andrew Bartlett wrote: > > On Fri, 2018-11-09 at 11:46 +0300, Taner Tas via samba wrote: > > > > I just tested Samba 4.9.2 on one of my DCs, previously running > > > > version 4.8.6. Immediately after install, I ran "samba-tool dbcheck" > > > > and got

Hi Guys, Setup: Versions: Samba: 4.6.7 Bind9: 9.10.3 Firewall disabled AD Provision: Migrated from samba 3 to 4 using classic upgrade. samba-tool domain classicupgrade --dbdir=/var/lib/samba.PDC/dbdir --realm=TEST.LOCAL --dns-backend=BIND9_FLATFILE /etc/samba.PDC/smb.PDC.conf The following was the section in regards to the upgrade Processing section

Hi Rowland, Sorry, migration using BIND9_DLZ gives the same result Not sure if the following from the migration is of a concern Could not add posix attrs for AD entry for sid=S-1-5-21-3936576374-1604348213-1812465911-3034, ((21, 'Element loginShell has empty attribute in ldb message ()!')) Could not add posix attrs for AD entry for sid=S-1-5-21-3936576374-1604348213-1812465911-3040,

Hello all; I use CentOS 7.5.1804 I update from samba-4.8.2 to samba-4.9.1 and finish with not errors, but when I run samba-tool dbcheck --cross-ncs I have the error: [root at gtmad ~]# samba-tool dbcheck --cross-ncs Checking 4087 objects ERROR(<type 'exceptions.UnicodeEncodeError'>): uncaught exception - 'ascii' codec can't encode character u'\xe9' in

An embedded and charset-unspecified text was scrubbed... Name: memory_profiler.txt URL: <http://lists.samba.org/pipermail/samba/attachments/20170330/f5d10ac9/memory_profiler.txt>

Hello, my domain is Dns domain = foo Realm = FOO Workgroup = FOO samba-tool dbcheck --cross-ncs --fix -v .... Checking object DC=foo ERROR(<type 'exceptions.ValueError'>): uncaught exception - unable to parse dn string File "/usr/lib/python2.7/dist-packages/samba/netcmd/__init__.py", line 175, in _run return self.run(*args, **kwargs) File

> I just tested Samba 4.9.2 on one of my DCs, previously running > version 4.8.6. Immediately after install, I ran "samba-tool dbcheck" > and got the following: > > Checking 511 objects > ERROR(<type 'exceptions.UnicodeDecodeError'>): uncaught exception - > 'ascii' codec can't decode byte 0xc3 in position 25: ordinal not in >

Hai Stefan, See. https://bugzilla.samba.org/show_bug.cgi?id=13616 I think thats you problem, at least simular. A left over from the python2 -> python3 conversion. I dont know it this one is in the sernet packages. Whats your ldb version? That should tell me more. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org]

I had the same problem, it was the DN of one of my OU? I remplaced the "ü" with a "ue" and everything was fine. Am 05.03.19 um 18:10 schrieb miguel medalha via samba: > I decided to give Samba 4.9.x a new try as AD DC in one of my servers. > It has been running version 4.8.9. I installed version 4.9.4 and when I > ran samba-tool dbcheck I still obtained the following

I build new version of talloc-2.1.6 (build from external tarball) and samba-4.3.6. But if I provision domain by command samba-tool domain provision --realm=test.alt --domain test --adminpass='Pa$$word' --dns-backend=SAMBA_INTERNAL --server-role=dc --use-rfc2307 --use-xattrs=yes I got error: Fixing provision GUIDs ERROR(runtime): uncaught exception - pytalloc_reference_ex() called for

Hello list, today I updated my samba domain to version 4.9, after everything went well, I ran the command ./samba-tool dbcheck and the error is the following, however everything else works perfect ... that could be happening???? ./samba-tool dbcheck Checking 903 objects ERROR(): uncaught exception - 'ascii' codec can't encode character u'xe1' in position 313: ordinal not in

Hi Rowland, I did that initially and that came with Failed to connect to ldap URL 'ldap://lin-pdc.lin - LDAP client internal error: NT_STATUS_BAD_NETWORK_NAME Hence I removed the whole ldap:// bit After your email I tried again but using ldap://localhost and it seems to have worked. Not sure what the issue is with the fqdn. I could run ldap queries when using fqdn. Regards, Praveen