I did’nt change (tweak/hack) nothing, yet,
simply install services and configured them
Nethserver 7.7 with AD and one NIC card which is configured as bridge under GREEN zone.
nethserver is 192.168.100.254
the AD as been deployed on 192.168.100.254
it’s probably of the bridge, but I expect this working since I create it through cockpit
When I try to create a user it fail
the old interface tell me
ads_connect: No logon servers are currently available to service the logon request.
Didn't find the ldap server!
kinit: Cannot contact any KDC for realm 'AD.DOMAIN.TLD' while getting initial credentials
But then when I scan from my laptop the port are open
Discovered open port 135/tcp on 192.168.100.253
Discovered open port 53/tcp on 192.168.100.253
Discovered open port 445/tcp on 192.168.100.253
Discovered open port 139/tcp on 192.168.100.253
Discovered open port 88/tcp on 192.168.100.253
Discovered open port 49154/tcp on 192.168.100.253
Discovered open port 389/tcp on 192.168.100.253
Discovered open port 636/tcp on 192.168.100.253
Discovered open port 3268/tcp on 192.168.100.253
Discovered open port 49153/tcp on 192.168.100.253
Discovered open port 49152/tcp on 192.168.100.253
Discovered open port 3269/tcp on 192.168.100.253
Discovered open port 464/tcp on 192.168.100.253
NethServer and AD do not use the same IP, but the same Interface. The Interface is bridged for the Linux Container running in NethServer which provides the AD capability. (Sounds complicated, but usually just works…).
Personally, I have the NethServer of my clients on IP .20, and the AD on .11.
I also specify the AD as WINS, and make the Entry in DHCP, so that is propagated to clients…
This may be a bug in the new interface.
-> Needed entries for Shorewall are not being made.
Try deleting your AD, and re-creating it from the old Interface ( Port :980 ).
Report if that helps, so the bug can be weeded out…
As I understand, this is a new server, so there are probably few or no entries in that AD.
It isn’t even working properly. What can you lose?
No reinstalls needed, no CLI needed, all via Web…
Just for your Info:
Use the old Interface and make a Config-Save (See Backup in the old Interface) BEFORE deleting your AD.
Delete the AD (also old Interface)
Reboot, and restore that saved config (You can specify which backup you want to restore).
NethServer will rebuild exactly that AD, but set the correct settings so everything works, including Shorewall. NethServer generally restores WITH all modules, they’re downloaded if needed.
I’ve had to do this before, a samba update a while back screwed my AD. I repaired by using the above procedure. It also worked on a few client installation inflicted by the update…
NethServer is very resilent, I assume you may have found a bug in the new Interface, but the old one works as far as the mentionned issues are concerned… (Shorewall et Al.)
via CLI: I remove nethserver-samba, reboot than reinstall nethserver-samba without success
via OldInterface: I remove file-server, reboot than reinstall file-server without success
but as good habit transcend distribution I did snapshot
after the restoration now I understand what you means by uninstall the AD, the button wasn’t there before
Did you manually reinstall nethserver-samba / file-server or did you - as suggested - Restore your settings?
Most likely you found a bug in the new Interface - please report that to the Bugtracker. I’m just not sure personally, what the right link is, but someone on the Dev-Team should be able to give you the right pointers…
If it works, by all means take the easiest route.
If it doesn’t, do step by step, if running in a virtual environment, make snapshots.
It’s like insurance. Better to never to have to claim insurance for whatever.
If you DO need it, it’s always better knowing, it been dealt with, and paid for…
the diff of the old machine which didn’t work and the new one
I used the old interface to configure almost everything except the backup part because I backup to Backblaze, but I’m not ready to blame cockpit or the nethserver dev to team for this.
Another different was /tmp was on a different partition of 1GB but the default permission
packages/software/modules I didn’t reinstall
3.1 mattermost
3.2 squid (proxy and filter)
3.3 report (network-dante)
3.4 freepbx
3.5 snmp
3.6 ipsec
If you’re in Thailand, you’ve got beautiful nature down there. True, B’kok is a sprawling metrapolis, but nature isn’t far. I am swiss, but was living in Malaysia the first ten years of my life and been a few times since then to visit.
I’m now in central Switzerland (Just outside of Zug), here’s my view: