I’m trying to create a new forest. I just tried it on a virtualbox and I got the same issue. It gets to 16% and stalls. Again, I gave her a half hour…
The author is unknown.
 
hendersjAdministrator
10. Apr
I’ve been able to duplicate what I think is the error you’re seeing - but would need to confirm a few details:
1.	What is the value that you’re using for the root domain name in the YaST module?
2.	What is the FQDN of the host you’re installing on?
3.	What is the domain functional level (probably doesn’t matter - but just in case. I’m testing with the value of 2008R2)
You can obfuscate the domain name and FQDN as long as you use the same obfuscation for both.
I also found that when running it (I started YaST from a terminal window), there’s a prompt in the terminal window to set and confirm the administrator password for some reason - and that’s probably why it’s hanging up at 16%).
AD’s dependence on DNS is one of the things that can make the setup a bit more complicated. There are benefits to it, but it does make things a lot more involved if you’ve never set it up before. DNS zones and names in AD have to match (in my case, it’s hanging up because my test system has a name of localhost.localdomain - and what AD is looking for for the realm is “localdomain.something” (ie, a proper DNS zone). It complains if the DNS zone is too short (as it is here - if it were “localdomain.local” it’d probably work) because the short name (“localdomain”) can’t match the realm name, but the two have to be related.
After I input a password in the terminal window that I started from, I actually get error messages in YaST telling me this. I suspect you’d see the same thing.
 
Pauly-Walnuts
10. Apr
I forgot I had to install DNS. I retired some 15 years ago from the Windowz world. Getting old. And bored. Last version I touched, was 2008 R2 and only briefly. I was an MCSE on (If I recall) 2003?
Right now, I’m trying to configure DNS.
I did: sudo zypper in -t pattern dhcp_dns_server
Then I ran: sudo yast dns-server, and I’m told there is no such client module dns-server.
I really don’t want to do that manually.
If I’m understanding your 1st question correctly, it’s PaulyWalnuts.
The FQDN is PaulyWalnuts.rocks
Are you a fan of the Sopranos? 
This is not intended to be available anywhere other than my home.
Yes, 2008r2.
When I run yast from the command prompt, I’m told that the network is currently handled by NetworkManager, or is completely disabled.
You know, like Whisky Tango Foxtrot, right?
 
hendersjAdministrator
10. Apr
Then I ran: sudo yast dns-server, and I’m told there is no such client module dns-server.
You’ll need to probably also install the YaST package for managing DNS - yast2-dns-manager.  
Root domain in AD is the DNS zone name (essentially). So if you have hostname Pauly.Walnuts.rocks, the root domain would be Walnuts.rocks, and then the NETBIOS domain name would be WALNUTS (going from memory at the moment).
Are you a fan of the Sopranos? 
Indeed I am.  And Pauly always made me laugh.
When I run yast from the command prompt, I’m told that the network is currently handled by NetworkManager, or is completely disabled.
Can you show the output (and command) that gives this? Please place it in preformatted tags (</> in the formatting toolbar in the forum editor - that’ll make it easier to read.
 
Pauly-Walnuts
11. Apr
pauly@localhost:~> sudo yast dns-server
[sudo] password for root:
No such client module dns-server
pauly@localhost:~>
 
Pauly-Walnuts
11. Apr
The module dns-server is missing as well.
I installed DNS using yast2 software manager, selecting patterns and scrolled down to DHCP and DNS Server.
 
Pauly-Walnuts
11. Apr
Looks like those modules are no longer included in the newer releases of SUSE.
 
Pauly-Walnuts
11. Apr
^@pauly@localhost:/etc> yast2-dns-manager
yast2-dns-manager: command not found
 
Pauly-Walnuts
11. Apr
Can you send me a link to that in the repo? I’m not seeing it.
Unless I’m looking in the wrong area.
Are we having fun, yet?
Sure do appreciate your patients.
 
 
hendersjAdministrator
11. Apr
I just installed it from the repo:
$ zypper in yast2-dns-manager
Then launch yast2 with:
$ gnomesu -c '/sbin/yast2 dns-manager'
(or kdesu if you’re using KDE - or just launch YaST as root and you should see it in the list).
Glad to help out  
 
Pauly-Walnuts
11. Apr
Oh, hell, I’ve had that all along. Problem is:
 
21366×768 105 KB

 
Pauly-Walnuts
11. Apr
Clicking ok, does noting. If I enter the FQDN, I get the same result.
 
hendersjAdministrator
12. Apr
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.
 
Pauly-Walnuts
12. Apr
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”?
 
hendersjAdministrator
12. Apr
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.
 
Pauly-Walnuts
13. Apr
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?
 
hendersjAdministrator
13. Apr
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

 
Pauly-Walnuts
23h
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.
 
hendersjAdministrator
22h
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.
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.  
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.
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 1 - same login as you used for the forums.
 
Pauly-Walnuts
22h
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.