SCALE Joins Active Directory with wrong computer name TrueNAS-SCALE-22.02.4

[inman.turbo]

For some reason after changing the hostname of scale ( In my case to "tnscale") Then joining AD Domain truenas still reports the computer name as TRUENAS. The same is so for mDNS ans WS-Discovery. Windows computers on the network see the nas always as TRUENAS, no matter what the hostname is set to. This could become very problematic when having more than one nas on the network. Is this a bug or am I missing something?

 

[anodos]

The AD form has netbiosname. This is what is used for creating computer object in AD.

 

[inman.turbo]

Ahh ... it's hidden under advanced settings. Leaving the domain then rejoining with correct netbios name solves this. Thank you!

 

[inman.turbo]

Alternatively, editing the netbios name under services>smb also fixes this. I was expecting the hostname to update netbios name, and wasn't aware it could be configured independently. In the past I've only used NFS on freenas/truenas (for VM backing)

 

[Marc Lachapelle]

My domain name is longer than 15 characters (18) and ends by .lan , is there an option for me?

 

[anodos]

My domain name is longer than 15 characters (18) and ends by .lan , is there an option for me?

Your domain name shouldn't affect things. Internally winbindd uses the short-form of the AD domain name (which was automatically generated when you created your AD domain). This is different and relates to the hostname (which is not same as netbios workgroup).

 

[Marc Lachapelle]

First thanks for your quick response. This post will give you more details about the steps I tried https://www.truenas.com/community/t...s-joining-active-directory.96422/#post-724339 I just tried minutes ago and got "Failed to discover Active Directory Domain ..." . The details are on post 724339 . Is there a place where I can find the steps to properly give you all the data?