similar to: accessing foreign AD users to NT domain

On 24/08/2020 15:02, Piviul via samba wrote: > Hi all, I'm planning to migrate a NT domain to a AD domain. Someone > suggested me to create a new AD domain, Who was this 'someone' ? I ask because the correct way of doing this is to run 'samba-tool domain classicupgrade', we even have a wikipage:

Rowland penny via samba ha scritto il 25/08/20 alle 12:21: > [...] > Try adding 'nltm auth = yes' to the smb.conf, it defaulted to 'no' at 4.5.0 thanks Rowland I have tried to change ntlm auth to yes but AD users continue to have problems connecting to the shares... Piviul

Marco Gaiarin via samba ha scritto il 28/08/20 alle 09:53: > Mandi! L.P.H. van Belle via samba > In chel di` si favelave... > >> And i dont change registry keys to "make things work".. > > A light blink in my head. Louis, you have keeped WINS server (in old or > new domain)? Your client use it? > > When i had, as you, two domain (NT and AD), the NT

Rowland penny via samba ha scritto il 25/08/20 alle 18:20: > [...] > Even though your users may have the same username in AD as in the > NT4-style domain, they are different users, so a few thoughts. You have > 'map to guest = bad user', so I take it you must have 'guest ok = yes' > set in the shares (you haven't shown us the shares), in effect there is no

Mandi! Rowland penny via samba In chel di` si favelave... > Who was this 'someone' ? [...] > Yes, stop listening to spurious people who have never done the upgrade and > follow our documentation ;-) I'm 'someone'! ;-) And, as you know, i've correctly migrated/merged 4 NT domains in an AD domain some year ago, following also hint from this list. ;-) > I

No, the point is.. User verfications Computer verification And Authentication. These are 3 different things. The differences, in terms. NTLM KERBEROS DNS-lookups and how this all works together. But i only type with lots of errors, this is better to read ;-) https://docs.microsoft.com/en-us/windows-server/security/windows-authentication/credentials-processes-in-windows-authentication I

Per chi vuole guardare il log generato aggiungo una piccola legenda: ZIZI (192.168.70.3) ? il server samba, win7pro-v01 (192.168.64.12) ? il client win7; inoltre il dominio AD si chiama CSATEST mentre il dominio NT (anche se non compare nei logs) si chiama DOMINIOCSA. Piviul

Rowland penny via samba ha scritto il 27/08/20 alle 15:49: > On 27/08/2020 14:19, Piviul via samba wrote: >> >>> >>> Microsoft is enforcing more securitybut it's Microsoft that develop >>> NetBIOS and LLMNR and if it's enforcing >> security should enforce these protocols or remove them from their OS >> isn't it? > > Microsoft

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

L.P.H. van Belle via samba ha scritto il 26/08/20 alle 15:41: > [...] > Thats exacly what i see. > This: net use g: \\IP\share /persistent:yes > > Used COMPUTERNAME\username at REALM Or DOM\USER at COMPUTERNAME > And not not DOM\user at REALM > Thats what i mean, and if you look good in your logs you see this also. yes I've seen it but if you say "Your not sending

I have a small installation which includes 2 servers one is the PDC which handles logins and stores profiles.and also handles email and some minor Apache stuff. There is also a member server which handles most of the file sharing. These servers have been in service since around 2006 running Ubuntu but are on their third motherboards, third set of drives and their 6th LTS version of Ubuntu.

Rowland penny via samba ha scritto il 24/08/20 alle 17:39: > [...] > As far as I am aware, SMBv1 is still readily available on Win7, but from > Samba 4.11.0, it is now disabled on Samba, so if you must use SMBv1, you > will need to set: > > client min protocol = NT1 > > server min protocol = NT1 > > in smb.conf ok, the samba server I'm using as test has

Mandi! Rowland penny via samba In chel di` si favelave... > You have 'allow trusted domains = No' in 'global' and from 'man smb.conf': I've had not noted that. I can confirm that my working setup had NOT 'allow trusted domains = No'. -- dott. Marco Gaiarin GNUPG Key ID: 240A3D66 Associazione ``La Nostra Famiglia''

Rowland penny via samba ha scritto il 27/08/20 alle 16:43: > [...] > Netbios is intrinsically tied to SMBv1 and? LLMNR (Link-Local Multicast > Name Resolution) is also connected in a way, it allows name resolutions > without a nameserver. So, if you are using it, I personally wouldn't, > ever heard of MITM ? Just to understand a little more... NetBIOS with a wins server

On 26/08/2020 08:07, Piviul via samba wrote: > I've send this message yesterday but I've not received it from > samba at lists.samba.org: I try to send it again... > > Piviul > > -------- Messaggio Inoltrato -------- > Oggetto: Re: [Samba] accessing foreign AD users to NT domain > Data: Tue, 25 Aug 2020 13:05:35 +0200 > Mittente: Piviul <piviul at

That is because.. Your not sending the DOMAIN\username but COMPUTER\username, so access denied. I know its something like that in the backgrond, but i dont code "Windows" ;-) So, this is the only part i use: net use g: \\server.fqdn.tld\share /persistent:yes /user:NT4DOM\%username% net use k: \\server.fqdn.tld\share /persistent:yes /user:ADDOM\%username% Stop using :

Hello i have a problem after classicupgrade on ubuntu 14.04/samba 4.3.11 i know this version is not supported, sorry no way for the moment to do ubuntu upgrade... before migration netbios name in smb.conf (irisserv) did not match dns hostname (noordo) so AD was provisionned but with irisserv and there are no servicePrincipalName in irisserv ldap entry... is there a way to fix this? Thank

Hi Rowland, Fair comment. This is not a new domain and we are migrating to AD. The box in question runs Samba 3.6 (PDC and a physical box) and as such we are not able to directly migrate it. We are adding a Samba 4 box (a VM) , to which will become the new PDC . This box will then be used to migrate to AD. The Samba 3 box will converted as a file server. The confusion in smb.conf is possibly

Thu, 16 Jul 2020 08:15:06 +0100 Rowland penny via samba <samba at lists.samba.org>: > On 15/07/2020 22:17, RhineDevil wrote: > > Wed, 15 Jul 2020 21:49:12 +0100 Rowland penny via samba <samba at lists.samba.org>: > >> On 15/07/2020 21:30, RhineDevil wrote: > >>> Wed, 15 Jul 2020 21:08:44 +0100 Rowland penny via samba <samba at lists.samba.org>: >

I've currently got a Ubuntu 18.04 server running Samba?4.7.6 with an NT4 domain that I'd like to migrate to an AD.? I've found the following link but am struggling to match up the steps with the Ubuntu install.?? https://wiki.samba.org/index.php/Migrating_a_Samba_NT4_Domain_to_Samba_AD_(Classic_Upgrade) I've also found this post that creates a Samba AD on Ubuntu 18.04 from scratch