I am running NethServer 7.7.1908 on a Intel NUC. This is a temporary situation. I am trying to migrate to a Hyper-V VM.
What I did is:
Install NethServer 7.7.1908
Install the updates
Create a config and data backup on the original NethServer
Changed the IP of the original serer (temporary)
Disable DHCP (on the original server)
Stop nsdc (NethServer Domain Controller container) (on the original server)
Stop dnsmasq (on the original server)
Restored config (new install)
Restored data (new install)
I am able to ping the new install on the correct IP address (192.168.0.200).
I am unable to ping the nsdc (192.168.0.201) from my network.
I am able to ping the nsdc (192.168.0.201) from the console of the new install of NethServer.
I did look into the network settings and the firewall settings.
The bridge (br0) was originally bound to en01 (Intel NUC) and is now bound to eth0 (Hyper-V VM).
I can’t find any differences between the original and the new install firewall rules.
The physical port of the server which I use for the Hyper-V switch is connected to a unmanaged switch. The unmanaged swich is connected to a managed swich. The switch port is set to VID 300. Untagged traffic will be on VLAN 300.
I am hoping someone can help with this.
In the meanwhile I did set another IP on the new install of NethServer (192.168.0.198) and I did stop DCHP and disabled nscd + dnsmasq on the new install. I did change the IP on the original install (NUC) back to 192.168.0.200 and enabled the required services. Everything works fine from te NUC. I will shutdown the Hyper-V VM for now.
I understand that nscd is in a container. I am not sure how to trouble shoot the connectivity with the container from my LAN; I am able to ping nscd from the Nethserver’s terminal / console. My guess it is a network issue but I am not sure how to continue.
I did notice that I can view the users via “System” > “Users and Groups”. The Account Provider is set to “Local Active Directory”.
AFAIK, in Hyper-V, as in VMWare, you need to enable the so called “promicious mode” on the NIC for AD to work correctly.
Proxmox doesn’t need any special treatment, works out of the box. I’d suggest looking at Proxmox - it comes with so many free features, like file backup for Windows and Linux, Clustering, fast Migration.
Best of all: you can even live migrate a Windows VM from an Intel CPU to an AMD, as long as Proxmox is installed on both, the VM migrates - and doesn’t even notice the different CPUs!