similar to: Change Netbios name during classicupgrade?

On 16/10/2017 18:18, Rowland Penny wrote: > > 'workgroup' is not the netbios name, it is the NetBIOS domain name. > The workgroup should also not have a dot in it, 'DOMAIN.LAN' looks > suspiciously like a dns and realm name. > Indeed i lacked of precision, purpose of the post was more "change NetBIOS domain name during clasicupgrade". DOMAIN.LAN is the

Hi Rowland, Denis Thank you very much for your answers, It helped really a lot. And sorry for the delay of answer, was busy on other stuff. You advices don't lead me straight to the solution, but i get improvements, thanks to it. For now, whatever i can do to change the workgroup, It changes the Domain SID. Actually it's more subtle; Before change workgroup: #net getdomainsid

Well, let's try to be more precise about my issue and give some updates: I try to make a classicupgrade and meanwhile, change the Domain name during the process, which includes realm and NetBIOS domain name. I precisely meet difficulties with changing the NetBIOS domain name. What i've tried so far: 1) Change the NetBIOS domain name "workgroup" attribute on the old Samba 3

Hi, I'm going classicupgrade our samba3 to samba4 next weekend, and suddenly realised something: I intent to keep my samba3 PDC machine called 'filehost' as a member server, to only serve files. However, after classicupgrade my new (freshly installed) DC1 will of course have the netbios name from my 'old' samba3 machine. ('filehost') Meaning I end up with two

I have an old Centos5/Samba3.5 domain with LDAP backend that I am attempting to migrate to the latest Samba 4.2 on Centos 7.1. Samba in both cases has been installed using Sernet packages. I had successfully run the classicupgrade process, but in subsequent testing found that in the 3.5 domain all the computer accounts have the posixAccount class and therefore have a uidNumber.

Hello: First, sorry for my English. I'm testing samba4 rc5. I have compiled and installed samba4 and now I'm trying to simulate an upgrade from my samba3 site to my samba4 test installation. I have setup a isolated network and I have replicated server and clients, copied my samba3 ldap contents and tdb files. But, when I run samba-tool classicupgrade following to the docs,

Dear samba list after a classic upgrade i lose the printer drivers uploaded in NT Domain mode the drivers files are still present in print$ share but enumdrivers rpcclient command list no drivers... did i forgot a file in the dbdir during classicupgrade call or this data are not handled during classicupgrade ? Thanx

Hello, I'm talking about re-writing the classicupgrade HowTo since over a year now. :-) Now, after three rainy vacation days, it's finaly done: A complete and comprehensive re-write of the classicupgrade HowTo: https://wiki.samba.org/index.php/Samba_Classic_Upgrade_%28NT4-style_domain_to_AD%29 Some other mentionable documentation changes, I had done during the last week: *

I can see in the docs that a domain rename is not recommended/supported by Samba for an already provisioned domain. However, what I can't work out is if this is not possible during the classicupgrade step either? Does this make any difference, or would it present the same difficulties as renaming an already provisioned Samba AD? It case what I'm asking is not quite clear - I have a

Hi, I'm having trouble with the classic upgrade. We have three samba servers: Server1: CentOS 5/Samba 3.6 (with smbldap-tools) Server2: CentOS 6/Samba Version 4.2.14-SerNet-RedHat-23.el6 Server3: CentOS 7/Samba Version 4.2.14-SerNet-RedHat-23.el7 Server 1: CentOS 5/Samba 3.6 (with smbldap-tools) Serves our OpenLDAP backend for centralised authentication (LDAP replicated to two other servers

Hi, we might have encountered a possible python 3 bug in samba 4.11. We are using the sernet-samba packages. While the classicupgrade works on centos6 (using python 2) it fails on centos8 (using python3) with a classic python3 bug message: # samba-tool domain classicupgrade --dbdir=pdc-files/ --realm=ad.xxx.de --dns-backend=SAMBA_INTERNAL pdc-files/smb.conf INFO 2019-09-25 06:15:34,366 pid:12017

Hi Team, *I'm migrating to samba4 (samba 4.0.7) and doing "Upgrading In Place" **and running classicupgrade; *I have installed openldap-devel...as im migrating database from ldap.* * *while doing this am getting the following error message:* # /usr/local/samba/bin/samba-tool domain classicupgrade --dbdir=/samba-backup/ --use-xattrs=yes --realm=mydomain.com/samba-backup/smb.conf

Hi. We're trying to upgrade an old NT domain to AD. It's our second upgrade, and while the first was successfull this one has raised some issues for existing Windows 7 clients. If we disconnect the computer from the domain and join it back to the new S4 AD it works. Existing clients throws this error in Samba: Kerberos: AS-REQ b1rd42nbtmp648$@NT4DOMAIN from ipv4:10.0.0.42:49472 for krbt

On Mon, 5 Nov 2018 11:51:00 +0100 Corrado Ravinetto via samba <samba at lists.samba.org> wrote: > > > Il 05/11/2018 11:41, Rowland Penny via samba ha scritto: > > You might as well remove the line 'winbind use default domain = > > Yes', it does nothing on a DC. > > I would also add 'idmap_ldb:use rfc2307 = yes' > ok, i did it > > When

Hi all, Is this something I should report in bugzilla? In my smb3.conf I have vfs object = recycle full_audit crossrename and when doing a classicupgrade, I'm getting a segmentation fault. It doesn't finish. (tried 4.1.2, 4.1.3, 4.1.4) When removing the line, the classicupgrade finishes successfully. It's easy to get around, but wouldn't it be nicer not to crash..?

Hey everyone... I'm testing samba3 to samba4 migration and I'm having a problem with group migration. Basically, when I run classicupgrade, he keeps warning about group membership. I increase log level and it tells that the group that some users belongs to don't exist. Is there anyway to tell samba classicupgrade to import groups first and then do the rest? Kind regards, Bruno

> It looks like Domain Users does not have a gidNumber attribute, '100' > is the default ID set by Samba in idmap.ldb on a DC. can i change this id or is better if i change id in my userers/folders ?? > How did you carry out the classicupgrade and what from ? like wiki.samba.org suggest in classicupgrade and i used samba 4.9.1 compiled from source -- *Corrado Ravinetto *

Hello, I get the following error when performing a classicupgrade on rc6. This does not occur with rc4 or rc5. The command I am using is: samba-tool domain classicupgrade \ --dbdir=/root/import/var/lib/samba --use-xattrs=yes \ --realm=internal.testdom.com /root/import/etc/samba/smb.conf ERROR(<type 'exceptions.IndexError'>): uncaught exception - list index out of range File

Hi all. Problems resolved! I found the samba process that was increasing the memory after I ran the netstat from PID and I discovered that the process opened 88/464 tcp/udp port. After I ran tcpdump program in my DC server listening udp 88 port and I found many clients machines sending traffic a lot to my DC server. I blocked the ips from clients machines by iptables and the samba process

Hey Louis, thanks for the answer! That sounds like a viable route to go. Of course I'd prefer doing the classicupgrade and having the trust relationship still intact. It did work this way at some point during testing, that's why I find it hard to accept that I have to circumvent the problem like this. Did somebody else lose trust relationships after classicupgrade and found a way to