Hello , I did an upgrade from TN CORE 13 to SCALE 25.10.2.1 , this went not like a breeze but not too hard.
TNC13 was joined without problem to WS2016 AD server, now with Scale i Get this each try i do to create jointure.
I’m out of ideas what to check and my nerves are now at their maximum load 
Any guru with ideas?
I’m not an expert in WS2016 nor in scale but enough to follow steps you could help me with.
Thanks.
Are you using your AD servers as DNS? If not give that a try.
Another thing to try is delete the old object in AD reboot and try to rejoin.
thanks Johnny for your answer,
Yes already set AD as DNS (192.168.1.47) on TNS with no success, also already deleted all the previous registred machine in AD and cleared DNS entries too without luck.
rebooted many times AD and TNS —> KO
so now i’m out of ideas what to try
Just tried a new time an this time i got a weird thing, like DNS IP should be 192.168.1.47 but here it displays written in reverse order, why this mess can happen if this is really the DNS IP from Windows server which is displayed?
I have the same issue with 25.10.2.1. I’m trying to join it to a Samba 4 Active directory and I get errors that it can’t find my PDC. My DNS is setup correctly, I have all the required SRV records. I’m able to join a Windows 11 computer to this active directory without any issue and I can login to the Windows 11 computer with credentials from the AD but TrueNAS scale refuses to join.
Are you missing a reverse zone?
Hi,
what is a reverse zone?
Do i need that if AD server and Truenas are on same LAN?
on another location i’m in same scenario WS2016 AD server and TNS and it works nicely and i don’t have a reverse zone too.
So i’m not sure if this is mandatory?
```
Just tried a new time an this time i got a weird thing, like DNS IP should be 192.168.1.47 but here it displays written in reverse order, why this mess can happen if this is really the DNS IP from Windows server which is displayed?
```
That’s the reverse lookup for your DC. Minimally, DCs should have PTR entries in the AD DNS. It not being present indicates probably a manual change to your AD DNS that’s rather significantly broken.
thanks for that answer but as i’m french and don’t know what PTR entry means. i’m lost to check something.
If you could give me an example or detailled guidance on what to do could be awesome
I suggest doing internet search on the terms. Microsoft may have French documentation that assists on Domain Controlers, Active Directory and DNS Pointer Records.
https://www.cloudflare.com/learning/dns/dns-records/dns-ptr-record/
Thanks for cloudflare explainations, reading this for PTR use , in my case I don’t understand what it could help for.
On my LAN i have WSE2016 (acting as DNS) on static IP 192.168.1.47 and TNS server 25.10.2.1 having static IP 192.168.1.37 and set to use 192.168.1.47 as DNS resolver .
Name resolution is working fine in both ways, ping FQDN or Nslookup with IP or FQDN are resolving fine.
May be i’m wrong, but i’m not sure my problem is DNS related
I got another location with exactly same hardware install and there’s no Reverse Zone set on the WSE2016 DNS service and that location is working like a charm AD SYNC is OK.
For test and also to retablish external Bkuups for WSE16 server, tonight I added a Synology NAS to the WSE16 AD (it went like a breeze compare to Scale) worked at the first try.
Once jointure was done I created a new bkup task from software running on WSE16 side and started to bkup without any problem on synology NAS.
So almost that test proof AD is working fine and probably this is bugs on Scale side.
Out of interest have you tried joining from a clean install?
No , i didn’t, all the locations have been upgraded from TNC 13 to TNS 25.10.2.1
And for now I have no other TNS on same location to test with and it’s not where i’am almost 30km far from here.
Finally , i read the TN docs and tried to create a DNS PTR registration on WSE2016 Side and AD Sync worked at the first try after.
