similar to: Samba 3.0.22 NT4 joined trusting AD

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.

How many entries ? TDB Database is limited 250 users. -- Rodolphe ---------- Message transf?r? ---------- From: "Hoogstraten, Ton" <Ton.Hoogstraten@ingram.nl> To: <samba@lists.samba.org> Date: Sun, 3 Jun 2007 16:08:06 +0200 Subject: [Samba] Samba/Winbind slow with Active Directory Hi all, I'm looking for answers regarding a problem I'm having with Samba. Since a

Background: We are migrating from our NT4 domain, to a new Windows2003 Active Directory domain, so our Linux samba server is joined the the NT4 domain where most the users live. But we are now starting to migrate (Using MS built in Migration tool) users from the NT4 domain to the Active Directory. Once the users are migrated they are not able to access shares on samba 3 file server The samba 3

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, all! In the end I want to make Squid authorize users via NT4 domain. I have Samba 3.0.10 (further named PROXY) and NT4SP3 PDC (named CONTROL). # net rpc join -U admin Password: (I enter) Joined domain: REGENT.CENTER. It seems to be OK, but the following record appears in PDC's system log: Event ID: 5723 Source: NETLOGON Type: Error Description: The session setup from the computer

Hello! It seems, that Vista SP1 and Server 2008 cannot join an NT4/Samba-domain. Vista once could join before SP1, if one did some modifications to the system (LAN Manager authentication level, Encryption of secure channel). But these workarounds do not seem to work with SP1 anymore. Microsoft points out that joining NT4-domains with Vista SP1 and Server 2008 is not supported/tested

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

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

On Mon, 18 Jun 2018 17:12:51 -0500 David Whitney via samba <samba at lists.samba.org> wrote: > Greetings! > > I have a brand new Windows 10 Pro box, Version 1703, Build > 15063.1155, and made the two registry mods (DNSNameResolutionRequired > and DomainCompatibilityMode) to enable it to join an old-style NT4 > Samba domain (Version 4.3). However, I note that the dialog

Dear Friends: I am trying to join a Suse 9.1 Server running Samba 3.07 to an NT4 Domain. One part I am confused about is the command "net rpc join -U" ... is the username to be used with this command the name of an administrator on the NT4 PDC? Does that administrator need to be an user on the Samba Server and a member of the "root" group? I successfully join using

Hi all, Set-up: Local NT4-RESOURCE domain which the Samba server is a member off. One NT4-ADMIN domain with users accounts and one W2K domain with some other user accounts. A one way trust from NT4-ADMIN to NT4-RESOURCE and a one way trust from W2K to NT4-RESOURCE. Samba version 2.0.7 running on Solaris 2.6. According to the NT admins, the W2K domain is in native mode, but they still use

On Mon, 15 May 2017 14:11:54 +0200 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > Am 2017-05-15 um 14:06 schrieb Rowland Penny via samba: > > > Windows doesn't support joining Windows 7 to an NT4-style domain, so > > they definitely won't support windows 10. > > Well, I joined Win7 to NT4-domain back then ... (reg-hack, but

On 05/15/17 08:06, Rowland Penny via samba wrote: > On Mon, 15 May 2017 13:25:03 +0200 > "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > >> As you may remember I went through a classic-upgrade a few months ago. >> >> I have a second domain to migrate and I am again/still scared to >> attack that ;-) >> >> As I

I'm a longtime Samba user and admin (since 1.7) and I thought I had seen just about everything until Active Directory 2003 (native mode) completely took out our Samba user authentication (each server auth=domain to an AD 2000 domain). We have Samba running on a variety of servers (AIX, HP, Linux) and need to be able to provide our users with the ability to access their appropriate shares

I'm currently building a Samba3-based domain (DomA) that has a trust relationship with an existing production NT4 domain (DomB). DomA uses an LDAP backend. The LDAP server is local on the PDC and is dedicated to such use. DomA runs Samba 3.5.6 on Debian 6.0. DomB is an old-timer: NT4 domain that's running for ages. The trust relationship has been established: DomA trusts DomB. Clients

Am 2017-05-15 um 14:06 schrieb Rowland Penny via samba: > Windows doesn't support joining Windows 7 to an NT4-style domain, so > they definitely won't support windows 10. Well, I joined Win7 to NT4-domain back then ... (reg-hack, but anyway) > You may find a way around this lack of Microsoft support, you may also > find that a subsequent Windows update stops it working

Uninstalling MS16-101 fixed our issue. https://technet.microsoft.com/library/security/MS16-101 I ran "wusa /uninstall /kb:3167679", rebooting, and now we are back to normal. On Wed, Aug 17, 2016 at 1:43 PM, Bill Baird <bill.baird at phoenixmi.com> wrote: > Hi All, > > Our users started having issues late last week when trying to change their > passwords. They

On Mon, 15 May 2017 13:25:03 +0200 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > > As you may remember I went through a classic-upgrade a few months ago. > > I have a second domain to migrate and I am again/still scared to > attack that ;-) > > As I prepare my test VM and try to remember all those details the > customer has

Hi all, I'm looking for answers regarding a problem I'm having with Samba. Since a year our Samba fileserver is part of out worldwide corporate Active Directory. Before that Samba was part of our local NT4 domain. Since the change to Active Directory the Samba server became slower and sometimes does not respond at all to share requests. I need to find a solution to reduce the time

Hello all, We have Samba (2.2.5) running on three servers, each in a different subnet. One of them is a PDC (domain master = yes). The Samba PDC is also the NIS master. The smbpasswd is replicated using rsync to the other machines that act as Samba BDCs (domain master = no). They are also NIS slave servers. The smbpasswd synchronization takes place automatically every time smbpasswd is updated,