What does xadcntrl status say? Are all services up?

Did you manage to reconfigure LUM? Is at least ndsd up and running?

If you are unable to connect to the master DC, you could try to connect to another Edir server for getting LUM configured. You can later, if the master DC  gets available, change that setting back to the master DC.

You need to get ndsd and LUM running, then you can dig further. Without LUM a connection as Edir user to the samba share of sysvol will fail.

First question I would ask is what does xadcntrl status tell you? Is everything running? I had issues as well with dsfw upgrades from 18.3 to 24.1. I had the same ldap issue. Took days to figure it out. 

I believe I finally resolved by running /opt/novell/xad/sbin/upgrade_dsfw.pl

No still trying to get LUM running on the master DC... since hours....

Unable to connect to LDAP server

xxx.xxx.xxx or the specified user 

cn=admin,o=system does not have enough privileges to

configure Linux User Management. Error returned is 

140:UNKNOWN_ERROR. Please correct the problem and re-run

namconfig after the install. Other products dependent on LUM

will also need to be reconfigured.

xadcntrl tells all services active

Thanks for input, running the upgrade script, unfort changes nothing

Have you tried to change the ldap server? Have you tried a namconfig -k?

I think I had to reboot it after running the upgrade script before everything worked out. Were there any errors from the script?

AUT_Tom said:

Got some weired problems after upgrading my servers from OES 2018 SP3 to OES 24.1.

I've got many weird problems on DSfW (OES 18.3). I've opened a dozen cases over the past year. Most of my issues have never been resolved.

AUT_Tom said:

Most important problem is that the GPO's not working because the SYSVOL is not accessable from the clients and my DC master server is not visible in MMC console under Windows.

My Windows Event Viewer (still) reports many such events.

Last year I had several support sessions with OT support and the developers. A number of defects were identified: Sysvol could not be accessed via the short domain name nor IP address. It could be accessed using the FQDN but, that's not how Windows does it. A defect was created but, before work began, the defect was changed to an enhancement request and I never heard anything further.

AUT_Tom said:

If i try to connect to SYSVOL of the DC master over windows client with the network path a prompt appears to enter my login credentials but end up with wrong user and password.

Yup! Been there; Done that.

You can probably authenticate if you use "<FQDN>\<username>" as your username.

AUT_Tom said:

Log file only sayed that install cannot connect to LDAP server.

My 18.3 log files are full of them. I currently have a case open to resolve a list of issues similar to yours.

Clearly DSfW has issues. I'm sorry you are experiencing them but it is comforting to know that I am not the only one!

yes i changed to the ldap of the other DC, same error message.
namconfig -k i do, no error and no changes

reboot done, no changes, no errors at script

Have you tried to change the LDAP server to another eDir server?

As far as I remember using the local edir server gave problems.

But maybe you do not need to reconfigure LUM, if namcd is already running.

Do you have another volume on this server except the sysvol? If so can you access that?

And what permissions does the sysvol have? They should be RW for the administrator and the Domain Admins and readable by all.