I think on the contrary it can be relevant, because if the VM has a bridged interface it cannot be reached by the host system (at on least my Linux/Fedora/KVM install). Could you ping it from another machine?
The ns7-vm has 192.168.0.235 and can be pinged from any machine in the network. The KDC is in a container i think. The 192.168.0.236 can be pinged from ns7-vm, but not from any other machine in network.
hi @alefattorini , unfortunately i have troubles with setting up a nethserver-dc instance. I created a ns7 instance with webvirtmanager and updated it. everything worked perfectly. The installation of nethserv-dc-package itself worked also. But when i try to start the DC, the process stucks at “57% adjust-services”. Tried it serveral times. But always the same.
sorry, but i give up!! Can’t figure out the problem. In the KVM-VM the DC-installation stucks at “57% adjusting services”. The KVM-VM is much slower than the Virtualboxmachine. I tried it three times and everytime the same. Also I had on both machines (kvm and vbox) the problem to create user. Only if I created the user without password and changed the password afterwards it worked. I think there is somewhere an issue with the authentication of users, because of the LDAP-server has the same ip as the KDC and both are not reachable from the Network, only from the CLI of the vm itself. It’s like the firewall drops traffic to nsdc, but that can’t be because of openfirewal settings and I disabled shorewall at all.
Thanks for listening to my problems and your try to help.
I did many test installations and the boot isn’t really necessary.
Surely it can solve some kind of situation, but the dc must work out-of-the-box after the installation, and all your tests are very valuable to us in finding all the bugs!
I found only one issue on the DC: on a VM with a bridged interface, I can’t access the DC from other machines in the network. The same issue doesn’t apply on physical machine, so I would blame something in the network setup of my VMs.