Topic: windows 10 pro can't join sme9.1 domain

[globalsi]

lol ok.
no, nothing interesting in the events viewer but i'll verify next week (I have no more the computer with me this evening).

[ReetP]

ROTFLMAO.....

[janet]

globalsi

.... mmm .... what is ROTFLviewer ? 

Hmmm, if you can post here then you can use google search
http://lmgtfy.com/?q=ROTFLMAO

[globalsi]

lol ok.
no, nothing interesting in the events viewer but i'll verify next week (I have no more the computer with me this evening).

I confirm after another try today with another W10 computer : nothing in the windows events logs

[globalsi]

on the W10 computeur, the C:\windows\debug\dcdiag.txt contains (translated from french):

The following error occurred while the request to the DNS SRV resource record (Service Location) to locate an Active Directory domain controller for the domain MYDOMAIN.LOC:
The error was: "DNS name does not exist."
(Error code 0x0000232B RCODE_NAME_ERROR)

The request was for the SRV record for _ldap._tcp.dc._msdcs.MYDOMAIN.LOC

The causes of this error may be:

- The DNS SRV records required to locate an Active Directory domain controller for the domain are not registered in DNS. These recordings are saved automatically by a server when an Active Directory domain controller is added to the field. They are updated by the Active Directory domain controller at set intervals. This computer is configured to use DNS servers with the following IP addresses:

192.168.69.2

- One or more of the following zones do not include delegation to its child zone:

MYDOMAIN.LOC
LOC
. (Root zone)

192.168.69.2 is the ip address of SME9.1

[Stefano]

you're trying to join an AD domain, not a NT style.. I guess you already installed the .reg files..

anyway, please take a look here: https://wiki.samba.org/index.php/Required_settings_for_NT4-style_domains#Windows_10:_There_Are_Currently_No_Logon_Servers_Available_to_Service_the_Logon_Request

[globalsi]

Stefano, thank you for yours responses.

you're trying to join an AD domain, not a NT style.. I guess you already installed the .reg files..

yes, reg files are already installed.

anyway, please take a look here: https://wiki.samba.org/index.php/Required_settings_for_NT4-style_domains#Windows_10:_There_Are_Currently_No_Logon_Servers_Available_to_Service_the_Logon_Request

Thank you for the link but I think this is not for my situation :

After you have successfully joined Windows 10 to your Samba NT4 domain, you fail to log on and receive the error:

but my W10 computers can't join the NT domain...

Did someone manage to join native Win10 to SME9.1 domain ? (in forums, i've only saw junctions with Win10 updated from Win7 or Win8)

I'll compare reg parameters between my W7 and W10....

[globalsi]

mmmhh... no, I won't change anything if you already have other machines joined

the only way to make things work is to debug and solve your issue.. is there anything interesting/relevant in event ROTFLviewer?

mmmm... you were right.
I've found this on google about W10 and samba 2.6.23 (SME9.1 samba version) : https://lists.samba.org/archive/samba/2016-May/200082.html
The problem seem to be the period (.) in the workgroup name 

Any tips for changing it (knowing that I already have other machines joined) ?

[Stefano]

you can't..

the only solution is to unjoin all your clients from domain, change domain/netbios name (see above), rejoin all your machines and copy all your user's profiles onto the new ones.. a nightmare.. good luck

[globalsi]

...
I was afraid of that 
...

[janet]

globalsi

Keep your trusted DOMAIN  name short eg 8 characters, upper case letters only, no periods or other punctuation type characters, & no suffix or prefix or URL style names etc
eg
OFFICE
See
 https://support.microsoft.com/en-au/kb/909264

Which in part says:
However, periods should not be used in Microsoft Windows 2000 or in later versions of Windows.

[globalsi]

you can't..

the only solution is to unjoin all your clients from domain, change domain/netbios name (see above), rejoin all your machines and copy all your user's profiles onto the new ones.. a nightmare.. good luck

I made some laboratory tests.

The windows worgroup/domain/netbios name is MYDOMAIN.LOC and there is a machine as member.
If I rename both netbios and domain to MYDOMAIN, I just need to unjoin and rejoin the machine from the domain. The profile loaded is the same

I'll try on production next week and do a feed back.

[globalsi]

Hi,
some news about my problem....

I have up-to-date my SME (9.2).
I rename domain/netbios name from MYDOMAIN.LOC to MYDOMAIN (and reboot)
But a fresh W10Pro (version 1703) still can't join the domain 
W7Pro can reach this domain.
In the W10 logs, i can see some errors 4097 : The machine DESKTOP attempted to join the domain MYDOMAIN but failed. The error code was 1355.

Any ideas about this problem ?

[janet]

globalsi

Really you need to detune Windows 10 to suit NT (Windows NT/2000) style DOMAINS
& check that your Windows 10 machines can "see" the SME 9.x server.

See these for clues

https://msdn.microsoft.com/en-us/library/windows/desktop/ms681385(v=vs.85).aspx

http://microsoft.public.metadirectory.narkive.com/cEXBXnTq/failed-connection-error-code-1355

https://wiki.contribs.org/Windows_10_Support

https://www.google.com.au/search?q=Windows+10+error+code+1355&ie=utf-8&oe=utf-8&client=firefox-b&gfe_rd=cr&dcr=0&ei=hEnmWfrVA_LDXvHGoZgH

[ReetP]

Stefano...

Priceless

Have a