similar to: Trusting Multiple Domains NT4 and a AD Domain

Hi, I'm currently working on getting our site migrated from a NT4 domain into an AD domain. 2-way trusts have been established. The idea is that with SID history users in the AD domain can access their files on the samba 3.0.22 server in the NT4 domain. This works for an unknown time interval. with the AD account I can access the shares through the sid history in the NT4 domain joined samba

Hi, I'm currently working on getting our site migrated from a NT4 domain into an AD domain. 2-way trusts have been established. The idea is that with SID history users in the AD domain can access their files on the samba server in the NT4 domain. This works for an unknown time interval. with the AD account I can access the shares through the sid history in the NT4 domain joined samba server.

hi all, thanks to Rowland advice, I checked the net trustdom way to establish trust between domains. In my setup I have a samba-4.7.4 NT4 domain named TRUSTING which needs to have a trusting (outgoing)[1] with samba-4.7.4 AD domain named ATENEOAD. As far as I know it is very similar to: https://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/InterdomainTrusts.html#id2620849 I added the

Hi, we currently run one samba v3.0 domain "DOMAIN30" with WinXP domain members and Win7/8 accessing the file server without domain membership. Then we run a second samba v3.5 domain "NEWDOMAIN" with WinXP/7/8 domain members. Which was migrated from a NT4 PDC to samba 3.0 and to v3.5 eventually. Neither domain has anything fancy about it: users and joined workstations,

I presently have a Samba server (3.0.21b) set up as a member server in an NT4 domain (with a real Windows NT4 PDC). We are migrating to an Active Directory domain (with a real Windows 2003 domain controller). We have set up a two-way trust between the old NT4 domain "CLUNKY" and the new ADS domain "SLEEK" (aka sleek.local). The Samba server is a member of the CLUNKY domain

Hello, Thanks to the assistance from Samba devs, I managed to upgrade existing Samba 3 (NT4) domain to Samba 4 (they are co-existing in the same network, while services/computers are being migrated to AD). The sequence of actions was - run "classic upgrade" against local OpenLDAP-based replica of existing NT4 domain - extract from Samba 3 domain LDAP dump Posix attributes for users

I'm certain i'm just missing something and haven't hit the right search terms yet, however, the terms I've been trying all lead to others with the same problems and no solutions at all. My network is quite legacy, but has been working: nt4 PDC and BDC several samba file servers, various revisions DOS, Win95, Win98, NT4, 2k, xp clients I have an ubuntu 9.04 32bit samba 3.3.2

W dniu 2019-09-16 o?16:30, Rowland penny via samba pisze: > On 16/09/2019 15:04, L.P.H. van Belle via samba wrote: >> Well it was worth checking.. We just dont know what you already >> checked.. now I setup the Ubuntu Server 18.04.3 LTS + http://apt.van-belle.nl/ + https://github.com/thctlo/samba4/blob/master/full-howto-Ubuntu18.04-samba-AD_DC.txt#L268 + i changed krb (default

On version 2.0 using "security = domain" and "include = globals.%m" I could specify what PDC to use depending on client name. This was a neat arrangement to integrate legacy NT4 domains - I asked the remote admins to add the samba server to their domain, and ran "smbpasswd -j <various> -r <various pdc's>" to end up with multiple machine.sid's in

Well, I'm attempting to migrate my old NT4-based domain to Samba3. I've got Samba set up with an LDAP backend, I've extended my NDS schema, and I've got users in this new domain set up successfully and authenticating. I've decided that the best, most seamless way to migrate my domain is to create a new domain which will run alongside the old domain. A two-way trust

Well it was worth checking.. We just dont know what you already checked.. Then all i can say now is, or a different OS, or try Vincent's his packages. I see that is should support AD-DC, but I really dont know. I only do debian/ubuntu. At least it looks like it. (from : http://nova.polymtl.ca/~coyote/dist/samba/samba-4.10.8/RHEL7/SPECS/samba-v410x.spec ) %description dc The samba-dc

Hi all, I need to start looking into the problems/solutions of migrating from an NT4 Domain to Active Directory, where the NT Server is already in a 2-way trust with a Samba PDC. Hopefully, I'll have test NT, AD and Samba servers setup next week to start playing with, but in the mean time, I have some questions. 1 When a WinNT server gets migrated to Active directory, and that NT

On 2020-08-24 08:45, Rowland penny via samba wrote: > On 24/08/2020 14:09, K.R. Foley wrote: >> Regarding the statement "they will ignore the PDC" above, is there >> really no way to undo that? > > Only by not letting your clients contact the AD DC. > > One of the first things that the migration to AD script does is to > obtain the SID from the NT4-style

On 24/08/2020 03:59, K. R. Foley via samba wrote: > Hi, > > We have an older Samba3 NT4 domain, which uses a TDB backend. We have > a variety of different versions of Windows clients. We need to migrate > to a Samba 4 AD domain. I have successfully tested the classic upgrade > on a new server in an isolated network, but I had to work through some > issues along the way. My

Hi Marco, > I've lurked (and posted) on that list by some month, getting many > vaulable informations, but still i've many doubts. > > Most of my doubt i think came from the fact that 'AD' (generally) a is > a very complex beast, and if samba in NT4 mode fit very well in a UNIX > environment (and mind ;), samba in AD mode forced me to think in some >

On 2020-08-24 02:21, Rowland penny via samba wrote: > On 24/08/2020 03:59, K. R. Foley via samba wrote: >> Hi, >> >> We have an older Samba3 NT4 domain, which uses a TDB backend. We have >> a variety of different versions of Windows clients. We need to migrate >> to a Samba 4 AD domain. I have successfully tested the classic upgrade >> on a new server in

Hi Folks, I have upgraded from samba 3.0.28 to 3.0.28a and now users aren't able to connect to the samba share. Winbind is logging this message: [2008/03/25 15:07:12, 5] passdb/secrets.c:get_trust_pw_clear(720) get_trust_pw_clear: could not fetch clear text trust account password for domain DOMAIN the samba box is joined in an old nt4 domain. Then there is a trust to a windows 2003

Hi, I am finally biting the bullet and migrating our NT4 domain to Samba. I am using the following guide: http://vermeulen.ca/linux-windows-nt.html I installed a fresh copy of FC11 and installed samba 3 through yum. Hostname of the linux machine is LEONIDAS. the DOMAIN name is GENOME1. I created an account on the NT4 domain for a backup DC under the server name LEONIDAS. testparm returns that

All, I'm looking for a little bit of advice on migrating to an AD backend. We currently have 2 Domains (from a company merger) - one on NT4 DC, one on Samba DC. The 2 domains trust each other. We need to move to a single domain, and standardise on username format etc. The decision has been made to use Win2K3/AD as the backend. The AD is to be setup from scratch - user, groups, settings

W dniu 2019-09-12 o?22:17, Rowland penny via samba-technical pisze: > On 12/09/2019 20:37, Bart?omiej Solarz-Nies?uchowski via > samba-technical wrote: >> Dear List, > Sorry but this is the wrong list, it should have been the samba > mailing list, not samba-technical, I have cc'ed the samba list, please > reply there. >> >> I need to migrate my Samba NT4