similar to: join W10-PCs to NT4-based samba-domain?

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

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

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

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

Am 2016-11-25 um 12:10 schrieb Stefan Kania via samba: > Am 25.11.2016 um 10:12 schrieb Stefan G. Weichinger via samba: >> >> Just a general question ahead: >> >> I have various issues with Samba-4.2.10 on Debian 8.6 (in combination >> with NT4-based domain and Win10pro-clients). >> > Windows 20 is NOT supporting NT-style Domains anymore, no matter which

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 understanding is that if the clients communicate with the new AD DC, they will

Hi, I resolved NMBD errors, but still same error in windows 10 pro, Could please suggest any changes in windows 10 PC. Applied registry changes suggested by samba wiki but no improvement. I am able to join windows 7 clients without error. Regards, Ram On Mon, May 16, 2016 at 8:11 PM, Ram Prasad Bikkina <parvathiprasadb at gmail.com> wrote: > Hi Gaiseric, > > Thank you for

[see also my thread started here https://social.technet.microsoft.com/Forums/en-US/b653e756-f966-4f8f-9d13-f19a88d4cc5e/w10-pro-1903-and-samba-with-roaming-profiles-quotwe-cant-sign-in-to-your-accountquot?forum=win10itprogeneral] Hello, since the upgrade from W10 pro 1809 to 1903 roaming users can still logon, but they are 'greeted' with the message: "We can't sign in to your

NT4-PDC: # net groupmap list Domain Users (S-1-5-21-2940660672-4062535256-4144655499-513) -> users Domain-Admins (S-1-5-21-2940660672-4062535256-4144655499-512) -> root Klienten (S-1-5-21-2940660672-4062535256-4144655499-1010) -> klienten User pl13 is member of group "Domain Users": # pdbedit -Lv pl13 Unix username: pl13 NT username: Account Flags: [U ]

The issue does not seem to be connected to SMB1. It can be installed and it still won't authenticate. Something has been changed to force authentication to AD/DNS either solely or as a first step. The translation of the netbios name never happens even if the computer can resolve the name. Given that the authentication thru netbios resolution seems to get grandfathered in provided the domain

A couple of other issues to keep in mind... Aside from the fact that the errors suggest your W10 box is trying to join an AD domain, W10 also defaults to a protocol of SMB 3.3 which Samba 3.x does not support. If you resolve the issue wherein W10 thinks it is joining an AD domain, there's a strong possibility (if not certainty) you will then see errors in the log of the W10 box indicating

Am 2016-12-01 um 15:41 schrieb Rowland Penny via samba: > Have you altered /etc/resolv.conf, on the DC, to use its own ip as the > first nameserver ? That change seems to have fixed it! I added that now to network config for the VM. klist ok now step by step ;-) thanks

Hi, i have a LDAP+Kerberos+nfs+samba server and Windows 7 workstation joined to domain now i have some new workstation to join samba AD, but unable to join them i try and try many solution, but no success need some help

On Fri, 9 Dec 2016 11:11:56 +0100 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > From: "Stefan G. Weichinger via samba" <samba at lists.samba.org> > To: samba at lists.samba.org > Subject: Re: [Samba] Samba on Debian 8; NT4 domain, win10 > Date: Fri, 9 Dec 2016 11:11:56 +0100 > Reply-To: "Stefan G. Weichinger"

If this is an NT4-style domain, then DNS is not essential. Things like SRV records aren't relevant since a lot of the NT4 is back from the NetBios days. It looks like your Win 10 machine thinks it is trying to join an AD domain. Windows clients machines typically are using DNS to resolve server names to IP addresses. However DNS does not provide info on locating PDC's

I've been running Samba 4 in NT4 Domain mode for a few years, and it's been working fine with Windows 7 PCs. I now need to join a new Windows 10 PC to the domain, but I'm not having any success! When I try to join the domain, the Windows 10 PC says "An Active Directory Domain Controller could not be contacted...." I've tried a few things, including:- Setting

Am 2016-11-26 um 12:04 schrieb Rowland Penny via samba: > How have you tried to upgrade and what problems did you have ? I will have to retry that now with current releases etc, my tests were months ago and I couldn't exactly tell the points now. As far as I remember something around the groups failed. I will set up a debian-test-VM (same as the current NT4-PDC) and retry the

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 for joining a domain within Windows 10 now specifically says to "Join an Active Directory Domain," and no attempt to join

Am 2016-11-28 um 15:03 schrieb Rowland Penny via samba: > On Mon, 28 Nov 2016 14:22:00 +0100 > "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > >> >> NT4-PDC: >> >> # net groupmap list >> Domain Users (S-1-5-21-2940660672-4062535256-4144655499-513) -> users >> Domain-Admins

I am testing an upgraded NT4-domain: debian VM, samba 4 ... classic upgrade through I assigned the IP of the future server already, and I want to adjust the DNS-entries. Current NT4-DC is called "server.my.tld", so I got all the kerberos related DNS-entries with "server" Future ADS-DC should be called "dc.my.tld" : is there an easier way to do that then going