samba - May 2018 - Windows 10 Client - Samba 3 Server - NT4 Style PDC

I suggest reading this: 
https://support.microsoft.com/en-us/help/4034314/smbv1-is-not-installed-by-default-in-windows

Imo, the longer you wait with samba AD the harder it gets to get things running.
You could better spend you time on settting up and migrating to AD the keep
putting time in a dying product.

But thats my optinion. 

Greetz, 

Louis

 
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens 
> Marco Shmerykowsky PE via samba
> Verzonden: donderdag 24 mei 2018 15:46
> Aan: samba at lists.samba.org
> Onderwerp: Re: [Samba] Windows 10 Client - Samba 3 Server - 
> NT4 Style PDC
> 
> Interesting.
> 
> All my windows 10 machines are version 1803.  However, the ones
> that are connect properly joined the domain prior to the 1803
> update.
> 
> I've rolled back one machine to 1703 and now I at least get a
> prompt for username & password.  It still doesn't connect to
> the domain, but it is different behavior.
> 
> --
> 
> Marco J. Shmerykowsky, PE, F.ASCE
> marco at sce-engineers.com
> 
> -----------------------------------------
>     Shmerykowsky Consulting Engineers
>       Structural Analysis & Design
>      102 West 38th Street, 2nd Floor
>          New York, New York 10018
> Tel. (212) 719-9700 Fax. (212) 719-4822
>        http://www.sce-engineers.com
> -----------------------------------------
> 
> On 5/24/2018 2:06 AM, Henry Jensen via samba wrote:
> > 
> > 
> > Am 24. Mai 2018 05:44:04 MESZ schrieb Marco Shmerykowsky 
> via samba <samba at lists.samba.org>:
> > 
> >> I have an old setup that serves my purposes, but which 
> I'll move over
> >> to a more modern Samba4 setup at some point.  I know it's old,
> >> deprecated etc.
> >>
> >> In any case, at the moment I'm having a problem with two
Windows 10
> >> machines connecting to the domain I set up.
> > 
> > 
> > Which version of Windows 10? I also have problems joining a 
> Windows 10 1803 machine to a NT style domain. W10 1709 
> machines can join, with 1803 it seems Windows explicitly 
> looks for an AD DC.
> > 
> > Additionally I have enabled SMBv1 (which isn't enabled by 
> default since 1709) but to no avail.
> > 
> > It seems, with 1803 Microsoft closed that door for good.
> > 
> > Since I am using OpenLDAP as backend I ended up using 
> pGina[0] to allow domain users to log on onto that machine at 
> least, which works, but you lose all Windows domain specific 
> features like roaming profiles, logon scripts, etc.
> > 
> > I am in the process of migrating to Samba AD and I think 
> many more people are - the time for NT style domains is up.
> > 
> > Regards,
> > 
> > Henry
> > 
> > [0] https://mutonufoai.github.io/pgina/
> > 
> 
> ---
> This email has been checked for viruses by AVG.
> https://www.avg.com
> 
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
> 
>

smbv1 is installed via "Add programs / features".

nbtstat -c on version 1703 returns codes <1C> (ie Domain
Controller/Netlogon Server)and <1B> (ie Domain Master Browser)
for the netbios domain name.

Still getting a "specified domain does not exist or could not be
contacted error".

with respect to upgrading, I agree,  However futzing with one new
machines vs. dealing with an active network are two different things.
At the moment I do nto have the time to plan, test and rollout an
upgrade and risk the productivity of my employees.

Also, on the topic of an upgrade, are there any good books out there?
I have the "Official Samba-3 howto & Reference Guide."  Would be
nice
to have a book that covers the new stuff.  The wiki has content, but
it is not as convenient as a hardcopy book for my eyes.


On 5/24/2018 10:21 AM, L.P.H. van Belle via samba wrote:
> I suggest reading this:
>
https://support.microsoft.com/en-us/help/4034314/smbv1-is-not-installed-by-default-in-windows
> 
> Imo, the longer you wait with samba AD the harder it gets to get things
running.
> You could better spend you time on settting up and migrating to AD the keep
putting time in a dying product.
> 
> But thats my optinion.
> 
> Greetz,
> 
> Louis
> 
>   
> 
>> -----Oorspronkelijk bericht-----
>> Van: samba [mailto:samba-bounces at lists.samba.org] Namens
>> Marco Shmerykowsky PE via samba
>> Verzonden: donderdag 24 mei 2018 15:46
>> Aan: samba at lists.samba.org
>> Onderwerp: Re: [Samba] Windows 10 Client - Samba 3 Server -
>> NT4 Style PDC
>>
>> Interesting.
>>
>> All my windows 10 machines are version 1803.  However, the ones
>> that are connect properly joined the domain prior to the 1803
>> update.
>>
>> I've rolled back one machine to 1703 and now I at least get a
>> prompt for username & password.  It still doesn't connect to
>> the domain, but it is different behavior.
>>
>> --
>>
>> Marco J. Shmerykowsky, PE, F.ASCE
>> marco at sce-engineers.com
>>
>> -----------------------------------------
>>      Shmerykowsky Consulting Engineers
>>        Structural Analysis & Design
>>       102 West 38th Street, 2nd Floor
>>           New York, New York 10018
>> Tel. (212) 719-9700 Fax. (212) 719-4822
>>         http://www.sce-engineers.com
>> -----------------------------------------
>>
>> On 5/24/2018 2:06 AM, Henry Jensen via samba wrote:
>>>
>>>
>>> Am 24. Mai 2018 05:44:04 MESZ schrieb Marco Shmerykowsky
>> via samba <samba at lists.samba.org>:
>>>
>>>> I have an old setup that serves my purposes, but which
>> I'll move over
>>>> to a more modern Samba4 setup at some point.  I know it's
old,
>>>> deprecated etc.
>>>>
>>>> In any case, at the moment I'm having a problem with two
Windows 10
>>>> machines connecting to the domain I set up.
>>>
>>>
>>> Which version of Windows 10? I also have problems joining a
>> Windows 10 1803 machine to a NT style domain. W10 1709
>> machines can join, with 1803 it seems Windows explicitly
>> looks for an AD DC.
>>>
>>> Additionally I have enabled SMBv1 (which isn't enabled by
>> default since 1709) but to no avail.
>>>
>>> It seems, with 1803 Microsoft closed that door for good.
>>>
>>> Since I am using OpenLDAP as backend I ended up using
>> pGina[0] to allow domain users to log on onto that machine at
>> least, which works, but you lose all Windows domain specific
>> features like roaming profiles, logon scripts, etc.
>>>
>>> I am in the process of migrating to Samba AD and I think
>> many more people are - the time for NT style domains is up.
>>>
>>> Regards,
>>>
>>> Henry
>>>
>>> [0] https://mutonufoai.github.io/pgina/
>>>
>>
>> ---
>> This email has been checked for viruses by AVG.
>> https://www.avg.com
>>
>>
>> -- 
>> To unsubscribe from this list go to the following URL and read the
>> instructions:  https://lists.samba.org/mailman/options/samba
>>
>>
> 
>

Hai, 

Yes, i get it, thats the same everywhere.
And i know that problem also, but then i really suggest get people in to
helpout. Believe me, you will be running into problems and get even less time
the longer you wait.

Base on this : 
> specified domain does not exist or could not be contacted error".
Try \\ip it that works wait 5-15 min then try the nbtstat again. 

Not working, change the firewall settings in windows from public to private. 
And\or enable network detection in windows and try again. 


Greetz, 

Louis


> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens 
> Marco Shmerykowsky PE via samba
> Verzonden: donderdag 24 mei 2018 16:45
> Aan: samba at lists.samba.org
> Onderwerp: Re: [Samba] Windows 10 Client - Samba 3 Server - 
> NT4 Style PDC
> 
> smbv1 is installed via "Add programs / features".
> 
> nbtstat -c on version 1703 returns codes <1C> (ie Domain
> Controller/Netlogon Server)and <1B> (ie Domain Master Browser)
> for the netbios domain name.
> 
> Still getting a "specified domain does not exist or could not be
> contacted error".
> 
> with respect to upgrading, I agree,  However futzing with one new
> machines vs. dealing with an active network are two different things.
> At the moment I do nto have the time to plan, test and rollout an
> upgrade and risk the productivity of my employees.
> 
> Also, on the topic of an upgrade, are there any good books out there?
> I have the "Official Samba-3 howto & Reference Guide."  Would
be nice
> to have a book that covers the new stuff.  The wiki has content, but
> it is not as convenient as a hardcopy book for my eyes.
> 
> 
> On 5/24/2018 10:21 AM, L.P.H. van Belle via samba wrote:
> > I suggest reading this:
> > 
> https://support.microsoft.com/en-us/help/4034314/smbv1-is-not-
> installed-by-default-in-windows
> > 
> > Imo, the longer you wait with samba AD the harder it gets 
> to get things running.
> > You could better spend you time on settting up and 
> migrating to AD the keep putting time in a dying product.
> > 
> > But thats my optinion.
> > 
> > Greetz,
> > 
> > Louis
> > 
> >   
> > 
> >> -----Oorspronkelijk bericht-----
> >> Van: samba [mailto:samba-bounces at lists.samba.org] Namens
> >> Marco Shmerykowsky PE via samba
> >> Verzonden: donderdag 24 mei 2018 15:46
> >> Aan: samba at lists.samba.org
> >> Onderwerp: Re: [Samba] Windows 10 Client - Samba 3 Server -
> >> NT4 Style PDC
> >>
> >> Interesting.
> >>
> >> All my windows 10 machines are version 1803.  However, the ones
> >> that are connect properly joined the domain prior to the 1803
> >> update.
> >>
> >> I've rolled back one machine to 1703 and now I at least get a
> >> prompt for username & password.  It still doesn't connect
to
> >> the domain, but it is different behavior.
> >>
> >> --
> >>
> >> Marco J. Shmerykowsky, PE, F.ASCE
> >> marco at sce-engineers.com
> >>
> >> -----------------------------------------
> >>      Shmerykowsky Consulting Engineers
> >>        Structural Analysis & Design
> >>       102 West 38th Street, 2nd Floor
> >>           New York, New York 10018
> >> Tel. (212) 719-9700 Fax. (212) 719-4822
> >>         http://www.sce-engineers.com
> >> -----------------------------------------
> >>
> >> On 5/24/2018 2:06 AM, Henry Jensen via samba wrote:
> >>>
> >>>
> >>> Am 24. Mai 2018 05:44:04 MESZ schrieb Marco Shmerykowsky
> >> via samba <samba at lists.samba.org>:
> >>>
> >>>> I have an old setup that serves my purposes, but which
> >> I'll move over
> >>>> to a more modern Samba4 setup at some point.  I know
it's old,
> >>>> deprecated etc.
> >>>>
> >>>> In any case, at the moment I'm having a problem with
two
> Windows 10
> >>>> machines connecting to the domain I set up.
> >>>
> >>>
> >>> Which version of Windows 10? I also have problems joining a
> >> Windows 10 1803 machine to a NT style domain. W10 1709
> >> machines can join, with 1803 it seems Windows explicitly
> >> looks for an AD DC.
> >>>
> >>> Additionally I have enabled SMBv1 (which isn't enabled by
> >> default since 1709) but to no avail.
> >>>
> >>> It seems, with 1803 Microsoft closed that door for good.
> >>>
> >>> Since I am using OpenLDAP as backend I ended up using
> >> pGina[0] to allow domain users to log on onto that machine at
> >> least, which works, but you lose all Windows domain specific
> >> features like roaming profiles, logon scripts, etc.
> >>>
> >>> I am in the process of migrating to Samba AD and I think
> >> many more people are - the time for NT style domains is up.
> >>>
> >>> Regards,
> >>>
> >>> Henry
> >>>
> >>> [0] https://mutonufoai.github.io/pgina/
> >>>
> >>
> >> ---
> >> This email has been checked for viruses by AVG.
> >> https://www.avg.com
> >>
> >>
> >> -- 
> >> To unsubscribe from this list go to the following URL and read the
> >> instructions:  https://lists.samba.org/mailman/options/samba
> >>
> >>
> > 
> > 
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
> 
>

FWIW; I connected to the domain on the rolled back 1703 machine.
It wasn't connecting due to spelling errors on my end when setting
the various keys (Damn those post 40 eye/vision things - don't
get older kiddies).

Base on my experiences then, if you're connected to the NT4
style domain prior to the 1803 update, then you'll stay
connected.  On all my 1803 machines, the domain connection
was established prior to the update.  Everything still works.

So... the 1803 update is the culprit & a warning sign to
prepare an update to the samba server before MS does something
else.



On 5/24/2018 11:11 AM, L.P.H. van Belle via samba wrote:
> Hai,
> 
> Yes, i get it, thats the same everywhere.
> And i know that problem also, but then i really suggest get people in to
helpout. Believe me, you will be running into problems and get even less time
the longer you wait.
> 
> Base on this :
>> specified domain does not exist or could not be contacted error".
> Try \\ip it that works wait 5-15 min then try the nbtstat again.
> 
> Not working, change the firewall settings in windows from public to
private.
> And\or enable network detection in windows and try again.
> 
> 
> Greetz,
> 
> Louis
> 
> 
> 
>> -----Oorspronkelijk bericht-----
>> Van: samba [mailto:samba-bounces at lists.samba.org] Namens
>> Marco Shmerykowsky PE via samba
>> Verzonden: donderdag 24 mei 2018 16:45
>> Aan: samba at lists.samba.org
>> Onderwerp: Re: [Samba] Windows 10 Client - Samba 3 Server -
>> NT4 Style PDC
>>
>> smbv1 is installed via "Add programs / features".
>>
>> nbtstat -c on version 1703 returns codes <1C> (ie Domain
>> Controller/Netlogon Server)and <1B> (ie Domain Master Browser)
>> for the netbios domain name.
>>
>> Still getting a "specified domain does not exist or could not be
>> contacted error".
>>
>> with respect to upgrading, I agree,  However futzing with one new
>> machines vs. dealing with an active network are two different things.
>> At the moment I do nto have the time to plan, test and rollout an
>> upgrade and risk the productivity of my employees.
>>
>> Also, on the topic of an upgrade, are there any good books out there?
>> I have the "Official Samba-3 howto & Reference Guide." 
Would be nice
>> to have a book that covers the new stuff.  The wiki has content, but
>> it is not as convenient as a hardcopy book for my eyes.
>>
>>
>> On 5/24/2018 10:21 AM, L.P.H. van Belle via samba wrote:
>>> I suggest reading this:
>>>
>> https://support.microsoft.com/en-us/help/4034314/smbv1-is-not-
>> installed-by-default-in-windows
>>>
>>> Imo, the longer you wait with samba AD the harder it gets
>> to get things running.
>>> You could better spend you time on settting up and
>> migrating to AD the keep putting time in a dying product.
>>>
>>> But thats my optinion.
>>>
>>> Greetz,
>>>
>>> Louis
>>>
>>>    
>>>
>>>> -----Oorspronkelijk bericht-----
>>>> Van: samba [mailto:samba-bounces at lists.samba.org] Namens
>>>> Marco Shmerykowsky PE via samba
>>>> Verzonden: donderdag 24 mei 2018 15:46
>>>> Aan: samba at lists.samba.org
>>>> Onderwerp: Re: [Samba] Windows 10 Client - Samba 3 Server -
>>>> NT4 Style PDC
>>>>
>>>> Interesting.
>>>>
>>>> All my windows 10 machines are version 1803.  However, the ones
>>>> that are connect properly joined the domain prior to the 1803
>>>> update.
>>>>
>>>> I've rolled back one machine to 1703 and now I at least get
a
>>>> prompt for username & password.  It still doesn't
connect to
>>>> the domain, but it is different behavior.
>>>>
>>>> --
>>>>
>>>> Marco J. Shmerykowsky, PE, F.ASCE
>>>> marco at sce-engineers.com
>>>>
>>>> -----------------------------------------
>>>>       Shmerykowsky Consulting Engineers
>>>>         Structural Analysis & Design
>>>>        102 West 38th Street, 2nd Floor
>>>>            New York, New York 10018
>>>> Tel. (212) 719-9700 Fax. (212) 719-4822
>>>>          http://www.sce-engineers.com
>>>> -----------------------------------------
>>>>
>>>> On 5/24/2018 2:06 AM, Henry Jensen via samba wrote:
>>>>>
>>>>>
>>>>> Am 24. Mai 2018 05:44:04 MESZ schrieb Marco Shmerykowsky
>>>> via samba <samba at lists.samba.org>:
>>>>>
>>>>>> I have an old setup that serves my purposes, but which
>>>> I'll move over
>>>>>> to a more modern Samba4 setup at some point.  I know
it's old,
>>>>>> deprecated etc.
>>>>>>
>>>>>> In any case, at the moment I'm having a problem
with two
>> Windows 10
>>>>>> machines connecting to the domain I set up.
>>>>>
>>>>>
>>>>> Which version of Windows 10? I also have problems joining a
>>>> Windows 10 1803 machine to a NT style domain. W10 1709
>>>> machines can join, with 1803 it seems Windows explicitly
>>>> looks for an AD DC.
>>>>>
>>>>> Additionally I have enabled SMBv1 (which isn't enabled
by
>>>> default since 1709) but to no avail.
>>>>>
>>>>> It seems, with 1803 Microsoft closed that door for good.
>>>>>
>>>>> Since I am using OpenLDAP as backend I ended up using
>>>> pGina[0] to allow domain users to log on onto that machine at
>>>> least, which works, but you lose all Windows domain specific
>>>> features like roaming profiles, logon scripts, etc.
>>>>>
>>>>> I am in the process of migrating to Samba AD and I think
>>>> many more people are - the time for NT style domains is up.
>>>>>
>>>>> Regards,
>>>>>
>>>>> Henry
>>>>>
>>>>> [0] https://mutonufoai.github.io/pgina/
>>>>>
>>>>
>>>> ---
>>>> This email has been checked for viruses by AVG.
>>>> https://www.avg.com
>>>>
>>>>
>>>> -- 
>>>> To unsubscribe from this list go to the following URL and read
the
>>>> instructions:  https://lists.samba.org/mailman/options/samba
>>>>
>>>>
>>>
>>>
>>
>> -- 
>> To unsubscribe from this list go to the following URL and read the
>> instructions:  https://lists.samba.org/mailman/options/samba
>>
>>
> 
>