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

[globalsi]

Hi Janet
Thank you for your answer.

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.

The W10 machines can see the SME9 server. They can reach the files samba shares if i give a username&password when the explorer ask me.
I think the SME server is configured in a classic way: it does dhcp, I did not specify any particular dns.
I have import the win10samba.reg
My domain name is short (i moved it from MYDOMAIN.LOCAL to MYDOMAIN) without "." or "-" or "_"....

In fact, the error is not the same as in the beginning of the topic.
If I set a false domain, i have immediately a message like "Cannot connect a AD for domain mydomainfoo"
If I set the good domain, i have new windows asking me the credentials. But after this step (nearly 1 minute), i have the message :

Code: [Select]

The following error occured attempting to join the domain "MYDOMAIN"
The specified domain either does not exist or could not be contacted.
...still trying to understand...

PS : the firewall is off on W10 and the type of network is set as "private".

[Daniel B.]

If you have a dot in your NT domain name, there's a trick: on win10, turn ipv6 off, switch to a fixed IP and don't set any DNS server. Now you can join the domain, and once it's done, switch back to DHCP (or fixed IP with a DNS)

[globalsi]

I HAD a dot in the NT domain name but no more now.
Maybe I can set it back to try.

[Daniel B.]

Well, best not to have one, so I'd advise to leave it as is. It was just in case

[janet]

globalsi

Have you configured Windows to use SME server ss the gateway & DNS server.

You really need to tell us more sbout your network, how SME server is configured & how the Windows workstation is configured.
Did you read those various google results for your error code, any clues there.

Also have you disabled Active Dirctory in Windows.

Your issue is more than likely a Windows configuration one as Windows comes set for defaults that wotk with Windows AD servers, that's what I mean about detuning Windows, you have to disabke that functionality.

Did you check Windiws registry (regedit) to see the reg patch was correctly applied.

Have you searched the Forums here on Windows 10 & read everything there is, surely a clue there, others are joining SME NT style DOMAINS OK.

Another long known trick is to change the DOMAIN name in Windows to a WORKGROUP name, something you do not want to use (8 characters no periods), then shut down Windows.
Then restart Windows, change WORKSTATION name to a DOMAIN name that you do want to use, then restart Wiindows.
Then after reboot try joining the DOMAIN again.

Check the reg patch is really there first.

[globalsi]

If you have a dot in your NT domain name, there's a trick: on win10, turn ipv6 off, switch to a fixed IP and don't set any DNS server. Now you can join the domain, and once it's done, switch back to DHCP (or fixed IP with a DNS)

Daniel, you're a god ! 
I do it for one machine because I needed to resolve quickly the problem.
For others, I'll follow janet's indications 

[janet]

globalsi

As Daniels suggestion works, go with that.

[globalsi]

Anyway, I really wanted to thank you all for the help you bring me through the forum.
THANK YOU