*New 12.1 series Release:
2020-09-13: XigmaNAS - released

*New 11.4 series Release:
2020-09-12: XigmaNAS - released!

We really need "Your" help on XigmaNAS https://translations.launchpad.net/xigmanas translations. Please help today!

Producing and hosting XigmaNAS costs money. Please consider donating for our project so that we can continue to offer you the best.
We need your support! eg: PAYPAL

Problem Connecting N4F to Samba Active Directory

Authenticating XigmaNAS users using Active Directory or NT PDC
Forum rules
Set-Up GuideFAQsForum Rules
Post Reply
Posts: 11
Joined: 25 Jul 2017 21:51
Status: Offline

Problem Connecting N4F to Samba Active Directory


Post by Jdo300 »


I recently setup a samba active directory domain controller on an Ubuntu test VM (which, by itself seems to be working great). I can login to the domain I created from other computers on my LAN and set user permissions, etc. Now, I would like to connect my N4F test VM to my Active Directory VM.

My Domain Controller Info:
NetBIOS Hostname: AD
Domain Name: local.rgusa.com
IP Address:

On the Access -> Active Directory page of the N4F VM, I have the following settings:

Domain Controller Name: AD
Domain Name (DNS/Realm-Name): local.rgusa.com
Domain Name (NetBIOS-Name): LOCAL
Administrator Name: administrator
Administration Password: [Active Directory Controller admin password]

Then, under Services -> CIFS/SMB, I used these settings:

Authentication: Active Directory
Server Max Protocol: Default
Server Min Protocol: Default
Client Max Protocol: Default
Client Min Protocol: Default
NetBIOS Name: nas4free
Workgroup: LOCAL
Interface Selection: All Interfaces
Description: NAS4Free Server
Dos Charset: CP437 (Latin US)
Unix Charset: UTF-8
Log Level: Disabled
Local Master Browser: No
Time Server: No
Password Server:
WINS Server:
Trusted Domains: [Unchecked]

All Advanced settings left on their defaults.

So, if I reboot the server and then goto Diagnostics -> Information and then click on the "MS Domain" Heading, I see the following in the log:

MS Active Directory Information & Status:

Code: Select all

Results for net rpc testjoin:

Environment LOGNAME is not defined. Trying anonymous access.
Join to domain 'LOCAL' is not valid: NT_STATUS_CANT_ACCESS_DOMAIN_INFO

Ping winbindd to see if it is alive:
could not ping winbindd!
Ping to winbindd failed

Check shared secret:
could not obtain winbind interface details: WBC_ERR_WINBIND_NOT_AVAILABLE
could not obtain winbind domain name!
failed to call wbcCheckTrustCredentials: WBC_ERR_WINBIND_NOT_AVAILABLE
Could not check secret
checking the trust secret for domain (null) via RPC calls failed
List Important Users

Code: Select all

Connection to AD failed (Error NT_STATUS_UNSUCCESSFUL)
I'm not quite sure where to start to troubleshoot this. Any ideas?

Jason O

Posts: 11
Joined: 25 Jul 2017 21:51
Status: Offline

Re: Problem Connecting N4F to Samba Active Directory


Post by Jdo300 »

Hello All,

For anyone who comes across this post wondering what happened. The issue ended up being the spelling for the hostname of the AD test server. Once I corrected that, everything connected correctly.

- Jason O

Post Reply

Return to “Active Directory”