Topic: Windows 10 domain join?

[Marco Hess]

I just update a workstation from Win 7 Pro to Win 10 with a clean install but have trouble to get it to join the domain on my current main SME8 server.

The same PC was on the domain under Windows 7.

I applied the registry changes from server-resources for Win10.

When I follow the Setting > Accounts > Work access > Join or leave domain I go to the 'Join a domain', fill in the domain name and admin & password and after a while I get an error like: 'That domain couldn't be found. Check the domain name and try again.'

In the event viewer on the work station it says:

The machine DESKTOP attempted to join the domain XXXXXX but failed. The error code was 1355.

When I look at the netsetup.log on the workstation, there is a message there about unable to find a DC in the specified domain:

01/07/2016 18:47:58:463 NetpValidateName: checking to see if 'XXXXXX' is valid as type 3 name
01/07/2016 18:47:58:526 NetpCheckDomainNameIsValid [ Exists ] for 'XXXXXX' returned 0x0
01/07/2016 18:47:58:526 NetpValidateName: name 'XXXXXX' is valid for type 3
01/07/2016 18:47:58:526 NetpDsGetDcName: trying to find DC in domain 'XXXXXX', flags: 0x1020
01/07/2016 18:48:28:526 NetpDsGetDcName: failed to find a DC in the specified domain: 0x54b, last error is 0x0
01/07/2016 18:48:28:526 NetpJoinDomainOnDs: NetpDsGetDcName returned: 0x54b
01/07/2016 18:48:28:526 NetpJoinDomainOnDs: Function exits with status of: 0x54b
01/07/2016 18:48:28:526 NetpJoinDomainOnDs: NetpResetIDNEncoding on '(null)': 0x0
01/07/2016 18:48:28:526 NetpDoDomainJoin: status: 0x54b

Googling indicates that 0x54b/1355 is some sort of DNS problem.

Further searches in the event log for DNS shows:

Network query initiated for the name _ldap._tcp.dc._msdcs.XXXXXX (is parallel query 1) on network index 0 with interface count 1 with first interface name Ethernet, local addresses 10.1.0.100; and Dns Servers 10.1.0.21;

Another message:

A name not found error was returned for the name _ldap._tcp.dc._msdcs.XXXXXX.xxxxxx.com. Check to ensure that the name is correct. The response was sent by the server at 10.1.0.21:53.

This goes a bit beyond my understanding of DNS queries. Does SME8 supposed to know about a query like  _ldap._tcp.dc._msdcs.XXXXXX ??? or is that a Samba thing?

Regards,

Marco

[Stefano]

hi Marco, any news about it?

W10 domain joining is supported in SME8, please be sure your server is up to date (actually SME 8.2 is the last release), but be aware that SME 8 branch is in maintenance mode.. so start planning your migration to SME 9

[Marco Hess]

No, still no luck with getting the Win10 machine to join the domain.

I have migrated the domain services from my SME8-32 to my SME9-64 server.

Also does not make a difference.

WinXP and Win7 machines successfully join or rejoin the domain but not the Win10 machine.

[Marco Hess]

Turns out my problem was caused by my WiFi routers!

Hunting through the logs on my server I suddenly noticed something in the nmbd log:

"There is already a domain master browser at IP 10.1.0.AA for workgroup XXXXXX registered on subnet 10.1.0.BB."

Turns out that 10.1.0.AA ip address was one of my WiFi Access Points. Its a WiFi router loaded with ROOter software and this turns out to have a fully fledged samba server in there. It is capable of serving a plugged in USB disk to the network.

In my 'wisdom' when I set it up (a few years back now) I configured it with the same XXXXXX workgroup/domain name as the rest of the network (even though I did not use USB disks with it) and had not noticed that in its smbd.conf configuration template (in my defence it was hidden behind a TAB in its config web page) it has a setting:

domain master = yes

Which is pretty likely to cause some confusion on the network.

After I changed that workgroup/domain name on these access points to something completely different and rebooted them and all other machines on the network, the SME server Samba was now happy that it was the domain master.

And after that I was able to successfully join the Windows 10 machine to the domain. Yeah!

A bit of an obscure problem, with older versions of Windows having no problem with it but Windows 10 got confused about it.

[Stefano]

well, at the end you solved your issue and that's good

[guest22]

Nice catch Marco!