I’m going no where fast.
. I can access the internet and define/manage/use printers defined in cups with no problems but there seems to be a problem with adapter / protocol / and ip to virtual guests
tried loopback ip 127.0.0.2 as reported in ifconfig as access point to http://localhost:631/printers/<printername>.in virtualbox guest.
tried wlp2s0 ip 192.168.0.39 in ifconfig as access point
tried virtualbox define for wlp2s0 at 10.0.2.15 as access point
tried all the various incarnations of the adapters in virtual guests : NAT, NAT-network, Bridged etc. … and nothing works to define network printer or access internet.
tried samba but it says config can’t be done by a root user ??? I can understand not letting a user make changes but not the root
any ideas would be appreciative
I had everything working in 11.2 with older virtualbox (single core/32bit ) and things were easy but can’t understand why 13.2 with virtualbox 4.3.30 is so vague (4 core/64bit)
You’re looking at virtualized networks all wrong…
If you pass a device to the Guest, the Guest would monopolize use of the device.
So, for instance if you’re on a laptop with a wireless connection,
If you passed the actual physical wireless adapter to the Guest, then the Host would lose network connectivity.
That’s <not> what most people want although in rare cases it’s useful to understand that configuration.
<Normal> setups implement a “Linux Bridge Device” (on Linux. If on another OS, would be called something different).
I’ve posted full descriptions before in the Virtualization forum if you search using “linux bridge device” as key words.
The main idea is that a Linux Bridge Device is created and multiple Guests and the Host can then share its use. Depending on what created the LBD, it might be called br0, vmnet0, something else.
This is all generally set up automatically by whatever virtualization technology you install.
You always configure a wired connection <inside the Guest>(never changes) and in the Guest Settings you select what virtual network you wish to connect to, the choices are typically bridged, NAT and Host Only.
Once your Guests is configured as a working node on your network, <only then> do you configure access to services… You can’t put the cart before the horse by trying to configure access to printers and network shares before you verify you’ve set up networking properly first.
OK so had thought that the wireless network wlp2so was one network and the cups server being another separate network resident to the host and virtualized independently at the guests which would allow for either of them to be configured independent. Host systems are running perfectly as far networking goes. The virtual server of virtualbox needs to have server to host device and guest to server defines and drivers for things to work. Selecting Guest and choosing settings is complicated but liveable for the guest to server side. I had assumed that since some setting changes here show the true interface wlp2s0 (wireless) and ethu3x7 (Lan) the host to server was being addressed but such is not the case.
Under file → preferences is another set of network settings with two types of network definable. These being NAT and Host-Only… Nothing was defined under these. Using a little trial and error I found Host-Only will try and connect to the wifi as soon as a guest starts creating a fight between the host and the virtualbox for control. The NAT setting seems to have solved internet access problems for at least two virtual guests. When I set a NAT device here, Windows 2000 using NAT on 1st listed device and cable connected gives internet access. Windows 7 requires Bridged on the Intel Pro/1000 MT Desktop device and allow all with cable connected. No settings so far allow Windows XP Pro sp1 to work.
So now I have:
. Host to Virtual server as:
. NAT device enabled
. Virtual server to Win 2000 guest
. NAT device type PCnet - PCI II, cable connected and MAC address set identical to the wpl2s0 wireless device … working good
. Virtual server to Win 7 guest
. Bridge device name wpl2s0, device type Intel Pro/1000 MT Desktop, cable connected, and MAC set identical to the wpl2s0 device… working good
. Virtual server to XP guest
. No settings work at all.
. Defining printers in guests does not work even though CUPS has a working printer that is marked shared, enable internet printing all everyone.
. Under Linux host the printer shows as available even if it not on and jobs sent to the printer just que until the printer is turned on but maybe
. I have to actually turn on the printer to define it???