One good solution is to try a config restore on NethServer.
Make a full backup with Proxmox PBS (!)
Make a NethServer Backup with Config Backup (Just to be on the safe side!).
Remove the AD
Restore the config backup (AD should be reinstalled)
Reboot the server and test!
Note:
No Users, Groups or Data get removed, when you delete AD!
Are users/groups showing in server manager? Just to ensure NethServer AD is workingâŠ
Can you ping the domain name from a client?
ping ad.domain.tld
Does dig work?
dig ad.domain.tld
Your LDAP server URI is configured to an IP, I have the ad domain like ldaps://ad.domain.tld, maybe it doesnât matter.
Is your AD domain the same as your network domain? Itâs recommended to use a subdomain, see documentation.
This could be a possible cause for DNS issues.
If the problem was caused / started by an older Server (Same IP, Name, NetBIOS-Name, etc, then the problem is probably an AD internal issue. Check eg with PHPLDAPadmin, if the values for the AD server itself are correctâŠ
The AD Server is quite fussy if a conflict with AD/IP/Names turn up. Often, the AD database needs to be cleanedâŠ
The network connection change from domain to private.
Windows does this to me many times on other PCs in our network, and now it did it to this server.
This is so rare, it slipped out of my sight several times.
This is the first time this has happened with a server.
The solution is:
Remove the gateway from the network interface. (no need to reboot)
At this point it identifies the network âdomain networkâ
Write down the gateway again.
But, sometimes (rare) the problem is not solved (why?) then is another trick:
Disable the network interface and when reactivating it recognizes it as domain (but this has failed me a more than few times).
And I canât use this is Iâm trouble-soothing the server remotely.