Good idea, it wasn’t set.
I set it to “Allow all”, but it is the same.
I can’t access the domain.
Doesn’t block nethserver incoming connections when they are not on the same subnet or the hub count is higher?
It must be something in that direction.
No, I have Nethserver native on the machine. There Virtualbox is installed and the Windows runs in that VM.
It gets the IP from DHCP from the Nethserver. Physical Clients work, they have the same DHCP Server.
I can’t find any difference between the VM and the Hardware machines.
They all should run on the green network
I was able to join my win10 vm to my home domain using a bridged connection and the propper configuration settings for promisques mode. As an inquiring sidenote: if your dhcp is set to allow connections for registered devices only (those with a reserved ip), did you add the vm in the reservations list?
My case might not entirely be the same since the vm is running elsewhere…
OK, I removed Virtualbox and installed the nethserver version. I did a “/sbin/vboxconfig”.
The rest of the documation is confusing.
Problem persists…
I think it is a firewall, routing, something problem
I have absolutly NO knowledge of firewall…
I could reproduce the issue. A virtualbox guest can’t reach the samba container by default.
After changing the virtualbox network adapter bridging from ens33 (my local network interface) to br0 I was able to ping the container but no port was reachable.
Fun, does it is specific to nethserver, I use myself virtualbox on a fedora, I do not remember if a windows guest can even ping the samba container. I need to try.
I am migrating from a Ubuntu installation and had no problem with the Windows guest to access the domain…
Markus: how did you even find that solution? I am in awe…
The academical question would be why this effect is happening.
The pragmatic question is: how to make it persistent? Should I create a bash script and run it with crontab?
Thomas
Probably a stupid question, but might adding an interface neth side and then appointing that interface through the vm solve things? Or, would the virtual netadapter show up somewhere to be able to assign it a role or something?
I ask this because I had to appoint an ip address through dhcp each time I created a vmware vm on my main system before it could reach the network. I eventually might try to get a vm going on the server, hardware should be fine, but there are a few uncertainties I’d need to clear out before I try.
I always bridge, but have dhcp set to only allow connections from reserved ip’s, some times leading to disconnections if for some reason, the mac address of the vnet adapter changed.
What I’m also wondering is, if the virtual box, somehow would expose an interface to nethgui or so. If yes, wouldn’t be enough to just bridge the interface from vbox to green? I’m just trying to understand / learn some does and don’ts …