Clicking ok, does noting. If I enter the FQDN, I get the same result.
Did a bit of digging this afternoon, and it looks like maybe there’s a library missing.
I tried this:
adtest:~ # yast2 samba-provision
/usr/lib64/ruby/gems/3.3.0/gems/ruby-augeas-0.5.0/lib/augeas.rb:48: warning: undefining the allocator of T_DATA class Augeas
Realm [TESTDOMAIN.TEST]:
Domain [TESTDOMAIN]:
Server Role (dc, member, standalone) [dc]:
DNS backend (SAMBA_INTERNAL, BIND9_FLATFILE, BIND9_DLZ, NONE) [SAMBA_INTERNAL]:
DNS forwarder IP address (write 'none' to disable forwarding) [127.0.0.1]: <x.x.x.x>
Administrator password:
Retype password:
Unable to determine the DomainSID, can not enforce uniqueness constraint on local domainSIDs
Repacking database from v1 to v2 format (first record CN=Repl-Topology-Stay-Of-Execution,CN=Schema,CN=Configuration,DC=testdomain,DC=test)
Repack: re-packed 10000 records so far
Repacking database from v1 to v2 format (first record CN=IntellimirrorSCP-Display,CN=406,CN=DisplaySpecifiers,CN=Configuration,DC=testdomain,DC=test)
Repacking database from v1 to v2 format (first record CN=71482d49-8870-4cb3-a438-b6fc9ec35d70,CN=Operations,CN=DomainUpdates,CN=System,DC=testdomain,DC=test)
error probing vfs module '/[Default VFS]/': NT_STATUS_INVALID_PARAMETER
Error loading module '/usr/lib64/samba/vfs/dfs_samba4.so': /usr/lib64/samba/vfs/dfs_samba4.so: cannot open shared object file: No such file or directory
error probing vfs module 'dfs_samba4': NT_STATUS_UNSUCCESSFUL
smbd_vfs_init: vfs_init_custom failed for dfs_samba4
create_conn_struct: smbd_vfs_init failed.
(For the DNS forwarder IP address, I put in a local DNS server on my home network)
I can’t seem to find anything that explains how to resolve the vfs module issue here or the missing library.
Can you confirm you see the same thing in your setup if you run the yast2 samba-provision command as root and go through the wizard (it’s kinda weird because doing it this way, it prompts for each thing you put in the wizard in the terminal window after you’ve entered and verified the administrator password)?
Something that I did find suggested is that you not use a TLD of “.local” (which IIRC is not uncommon in AD configurations) because the Avahi daemon uses that for something.
Friday night. The Admiral requests, and requires my attention:) I’ll dig into this tomorrow. In the meantime, will you clarify what you mean by a “top level domain” of “Local”?
No worries 
By TLD of local, I mean don’t use something like testdomain.local for the realm. I recalled that with an AD setup on Windows, it wasn’t unusual to do something like that if you didn’t want it discoverable from outside the network (ie, keeping the DNS clearly off the Internet - even though other mechanisms would prevent external access to resources), but with the setup on Linux, you shouldn’t do that because the Avahi daemon uses “.local” to identify local services (so I understand), and that can create confusion.
So for the realm, use something like testdomain.test rather than ending with .local.
I probably won’t have a ton of time this weekend to dig further into the missing library, but if I do, I’ll see what I can find out.
The contents of my Hosts file:
127.0.0.1 Localhost Localhost.localdomain
#IPV6 is commented out
192.168.68.54 Walnuts Pauly.Walnuts.rocks
Should be fine?
Hmmmm…
That might confuse things, because you’ve identified the hostname as “Walnuts” but the NETBIOS domain would also be WALNUTS with a hostname of PAULY.
What you probably want is:
127.0.0.1 Localhost Localhost.localdomain
#IPV6 is commented out
192.168.68.54 Pauly Pauly.Walnuts.rocks
Brian Adams reacted via Gmail
Been busy, busy, busy! Dunno how to upload a picture here. Just finished a wooden model of the USS Constitution. Only took a little over 3 years.
When I run yast2 I get a GUI that asks me to enter the root domain. I enter walnuts.com. I select next, and it then asks me to enter the (2008R2) forest and domain functional level, but as soon as I select that, it greys out on me.
Nice! You can add pictures using the picture icon in the editor toolbar - but you might want to save that for the Open Chat section. 
This is starting to feel more and more like a bug - I think it would make sense for you to report it in bugzilla.opensuse.org - same login as you used for the forums.
What is, and were is the open chat session? And why would I not want to upload it here?
I’ll report is as a bug.
Incidentally, when I run yast2 dns-manager, it loads the app, I get the options of file and options. The only option file gives me is exit, whereas, action asks where the DNS server is running. This computer, or the following computer. I select this computer, then ok, and nothing happens.
For giggles and grins, I enter the ip of the router, and again, nothing happens.
Seriously bumbed out, man… I can’t get any other distributions to run on this machine. Plus, I like Suse.
It’s a section of these forums that’s just for general chit-chat. I find the model interesting, but it’s off-topic for a technical discussion - we like to keep things organized to make the value of the discussion high for those following along.
To get there, you can click the link in my previous reply.
Sounds good - it does seem like something’s not happening in the software correctly, or that there’s something missing from the documentation. Been a long time since I set up a real AD domain controller for anything other than a test, and never really looked at the SAMBA one before, but the fact that I’m having to enter stuff in the terminal window I launch YaST from in order to make any headway tells me there’s probably something in the module that’s not working the way it’s supposed to.
dns-manager is, as I undersatnd it, intended specifically for the AD DNS server components, so it may be trying to create records (AD uses Service Resource Records very heavily, so it needs to be able to create and manage DNS records on the DNS server). My guess is that the reason it’s not doing anything is because it’s trying to perform administrative functions and isn’t able to.
I’ll be perfectly happy to let you report a bug:)
When posting a topic in open chat, how do I get is to notify you of the post?
Type @hendersj in your post for that Open Chat topic. 
1 Like
As I don’t have a need for the SAMBA AD controller, it’d be better if you opened it - that way, if the developer has questions, they’ll be able to ask you directly, rather than me having to be the ‘middleman’ or having to guess.
Oh, okay…
Gonna be doing a bit of copy and paste here:)
1 Like
Bug reported.
Talk to you soon.
Thanks for your valiant effort:)
1 Like
From the bug guys.
If you want to run an ADDC on TW, you should be using the Heimdal builds from
The samba packages in TW use MIT KRB5, which is known to have issues. I’m not
aware of any specific issues like described here, but perhaps try the Heimdal
build first and report the result here.
Interesting, thanks for reporting back.
1 Like
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.