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 the DOMAIN\username but COMPUTER\username, so access denied." this is not true because I have only run the command "net use g: \\IP\share /persistent:yes">[...] > Which is going to be > 1) a problem in future. > 2) is a security risk > 3) users should not browse and should have drive mappings.. > But.. Im not controlling your network, you do, just my opinion.that's not so simple... some data are in official server but others don't. We have a lot of instruments that produce data that are stored in local PCs; some users have to access these data to control and elaborate results... any way thank you for the hint, I'll think about it...> The longer you wait with changing these setups, the more problems you will hit in the future. > Not because im saying this.. Because > > Microsoft is enforcing more securitybut it's Microsoft that develop NetBIOS and LLMNR and if it's enforcingsecurity should enforce these protocols or remove them from their OS isn't it? Any way I'll think about it. Thank you very much Piviul
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 ended support of NT4 servers over 15 years ago, but kept the client code, but it is now actively trying to remove it, hence new Windows 10 installs have SMBv1 turned off. You can never know just when they will totally remove it, but I am sure it will be removed. Samba is actively trying to remove SMBv1 and will deprecate it, along with NT4-style domains, possibly at 4.13.0, but if not, definitely at 4.14.0 To put it bluntly, NT4-style domains have a limited life left and it will probably be a toss-up who removes them first, Microsoft or Samba. Rowland
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 ended support of NT4 servers over 15 years ago, but kept the > client code, but it is now actively trying to remove it, hence new > Windows 10 installs have SMBv1 turned off. You can never know just when > they will totally remove it, but I am sure it will be removed.If I have well understood the article that Louis send in a previous message, to enforce security it is very important use FQDN to refers to samba server and don't use netBIOS or LLMNR names. I don't know samba very well so I don't know if NetBIOS is tied to SMBv1 protocol but I'm pretty sure that LLMNR isn't: so you don't agree with me if Microsoft should emforce security should enforce security on LLMNR protocol or remove it from his OS ? ...but perhaps I ignore something more... Best regards Piviul
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 cant hammer enough on.. DNS/RESOLVING MUST BE PERFECT A + PTR for the "real" registed server names. CNAME for aliasses. So much relies on this these days. When its not perfect well, something "just" wont work. And i run exacty what you want.. I have 3 separated domains. A samba NT4DOM (3.6.X) A Samba AD DOM 4.12.6 A Windows 2008R2 All my pcs and user login against the samba AD All other re-uses the user/passwords from the AD login. And i dont change registry keys to "make things work".. All defaults in the clients except what i push with GPO's. You know what you need todo.. Make it perfect again. Because in computer good is not good enough.. You want perfect, or as close you can be to perfect. Greetz, Louis> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Piviul via samba > Verzonden: donderdag 27 augustus 2020 16:24 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] accessing foreign AD users to NT domain > > 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 ended support of NT4 servers over 15 years ago, > but kept the > > client code, but it is now actively trying to remove it, hence new > > Windows 10 installs have SMBv1 turned off. You can never > know just when > > they will totally remove it, but I am sure it will be removed. > If I have well understood the article that Louis send in a previous > message, to enforce security it is very important use FQDN to > refers to > samba server and don't use netBIOS or LLMNR names. I don't know samba > very well so I don't know if NetBIOS is tied to SMBv1 > protocol but I'm > pretty sure that LLMNR isn't: so you don't agree with me if Microsoft > should emforce security should enforce security on LLMNR protocol or > remove it from his OS ? ...but perhaps I ignore something more... > > Best regards > > Piviul > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba > >