similar to: Moving users from a Samba 3.6 to 4.9 (tdb)

Le Thu, 8 Oct 2020 13:09:37 -0300 Elias Pereira <empbilly at gmail.com> ?crivait: > > On Thu, Oct 8, 2020 at 12:20 PM Emmanuel Florac via samba < > > samba at lists.samba.org> wrote: > > > > Hello, > > > > I have an old 3.6 server to be replaced with a new 4.9 one. They are > > standalone, using tdbsam backend. > > > > I copied

Le Thu, 8 Oct 2020 17:37:38 +0100 Rowland penny via samba <samba at lists.samba.org> ?crivait: > On 08/10/2020 17:25, Emmanuel Florac via samba wrote: > > But it's not a domain, no LDAP, no AD. Just a standalone server, > > migrating to another standalone server. Should I do something using > > Samba tool? > > No, samba-tool is only used with AD. > >

Le Fri, 9 Oct 2020 13:02:22 +0100 Rowland penny via samba <samba at lists.samba.org> ?crivait: > Restart smbd and winbind and see how you go on. > No dice. I've edited the smb.conf, stopped the services, copied the old tdb again (account_policy.tdb group_mapping.tdb passdb.tdb registry.tdb secrets.tdb share_info.tdb winbindd_idmap.tdb); started the services and... #

Le Thu, 8 Oct 2020 18:31:38 +0100 Rowland penny via samba <samba at lists.samba.org> ?crivait: > You do not normally run winbind on standalone server, so I think you > need to post the [global] portion of your old smb.conf, so we can > find out just what you are running. Here is the old one: [global] name resolve order = wins lmhosts host bcast passwd chat =

Hi everyone, we plan on setting up a Samba 4.x based AD. We have a couple of ancient to old systems running samba 3.0.24 to 3.5.7 and 3.6.24. Is there any problem to integrate those old systems as member of a Samba 4-driven AD? -- ------------------------------------------------------------------------ Emmanuel Florac | Direction technique | Intellique

Le Sat, 18 Feb 2017 20:17:12 +0000 Rowland Penny via samba <samba at lists.samba.org> écrivait: > Only change I made before installing Samba, was to comment the > '127.0.1.1' line in /etc/hosts Tried again with your smb.conf and minimal changes, and it gets worse: [2017/02/20 14:42:19.048133, 0] ../lib/util/fault.c:78(fault_report)

On Sat, 18 Feb 2017 17:41:06 +0100 Emmanuel Florac <eflorac at intellique.com> wrote: > > OK, but getent and id return with error (id: no such user, getent: > return code 2). On the systems I've previously set up similarly > (Wheezy/Samba 3.6), id and getent work. > Is this before or after you tried my proposed smb.conf ? > > > > > > I've found

Le Sat, 18 Feb 2017 13:10:36 +0000 Rowland Penny via samba <samba at lists.samba.org> écrivait: > idmap config *:backend = tdb > idmap config *:range = 2000-9999 > idmap config SAMDOM : backend = rid > idmap config SAMDOM : range = 10000-999999 > You mean TESTAD instead of SAMDOM, don't you? --

Actually it isn't part of AD at all. We are using FreeIPA and Samba. We just finally figured this out with the help of some folks at Red Hat. It turned out there was a bug in one of the libraries that came along with sssd (sssd-libwbclient I believe). Their suggestion to use winbind and the version of the same library that came with it seems to have solved our problem instantly. It

On Sat, 18 Feb 2017 18:31:16 +0100 Emmanuel Florac <eflorac at intellique.com> wrote: > Le Sat, 18 Feb 2017 17:03:33 +0000 > Rowland Penny via samba <samba at lists.samba.org> écrivait: > > > On Sat, 18 Feb 2017 17:41:06 +0100 > > Emmanuel Florac <eflorac at intellique.com> wrote: > > > > > > > > OK, but getent and id return with

Hi everyone, I have the exact same problem as this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=772154 But the Samba version is different and much newer (Debian Wheezy 2:4.1.17+dfsg-1~bpo70+1). B asically many errors appear about non existing usershares. These fake usershares are just the user name, but truncated of the last character. process_usershare_file: stat of

Le Fri, 11 Aug 2017 11:55:03 +0100 Rowland Penny via samba <samba at lists.samba.org> écrivait: > If you are going to upgrade, you might as well go for the highest > version you can, this will probably mean using Louis's packages. > > Samba is a rapidly changing program, a new minor version is released > every 6 months (approx) and the changes are significant. > >

I've got a Debian/Jessie Samba 4.2.14 running as an AD member. ADC is a Windows2008R2 server. Join worked without problem. # net ads testjoin Join is OK wbinfo -u and wbinfo -g work perfectly and provides a list of users and groups from the AD as expected. wbinfo -i <user> works too: # wbinfo -i TESTAD\\testuser

Le Mon, 28 Aug 2017 16:45:16 +0200 Reindl Harald via samba <samba at lists.samba.org> écrivait: > Am 28.08.2017 um 16:29 schrieb Rowland Penny via samba: > > These are your non-default lines: > > > > server signing = mandatory > > and i bet that one has the major performance impact > __________________________ > > quote from microsoft: >

hello, I need to extract user passwords from a samba 4.7.x and import them into new samba 4.10.x, any suggestions? thanks in advance.

Le Thu, 10 Aug 2017 18:46:12 +0100 Rowland Penny via samba <samba at lists.samba.org> écrivait: > 4.2.x is EOL as far as Samba is concerned, there have been a lot of > changes since 4.2.* came out. > > Can I suggest you go here: http://apt.van-belle.nl/ > > You can get a much more recent version there, 4.6.7 OK I'll try it, but that doesn't really explain why

Hai, Ok, so you have 3 the same machines and only one is slow. Thats important info. Did anything special happen with this server. For example 2 servers got a new install and this one had an upgrade (or sort of upgrade) from the "old" server? Or you configured the new server in an other (ad site) and moved it to the new location. In tring to figure out, where what happend, so we

On Mon, 28 Aug 2017 15:51:42 +0200 "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > Hai, > > Thank you for reporting this back. Very welkom and good to heard you > fixed it. > > > It would be interesting to know which parameters absolutely > > kill performance this way! > > Yes, that would be great to know which parameters

Our fileserver (running RHEL 7.4) has suddenly stopped allowing access to network shares through Samba. It is running Samba 4.6.2. When someone tries to mount a shared folder it prompts them for a username and password which fails even when the password is correct, rather than using their valid Kerberos ticket as it has in the past. Anyone here has a similar experience or suggestions as to

On Sat, 18 Feb 2017 13:50:52 +0100 Emmanuel Florac via samba <samba at lists.samba.org> wrote: > Le Sat, 18 Feb 2017 13:20:52 +0100 > Emmanuel Florac via samba <samba at lists.samba.org> écrivait: > > > I've added > > idmap config * : backend = tdb > idmap config * : range = 10000-30000 > > to smb.conf, and now 'wbinfo -i