[PLUG] Printing from Virtual Box
Denis Heidtmann
denis.heidtmann at gmail.com
Mon Oct 16 03:13:40 UTC 2017
Status: I got started trying to set up the printer in bridging, using the
printer's name rather than the IP. I thought I would continue in that
direction until I was either successful or could figure out why not. I got
the name of the printer from the router--it said HP69E035. I shut off
wireless direct. Printing from the host still works. I set up a new port:
TCP/IP; gave it the same name as the printer. I went through the install
procedure. Says it was successful, but it will not print.
I can reach the printer's embedded web server from the host and the guest
(10.0.0.244). Right now I suspect the Windows Install may be the issue. I
will try again using the IP address rather than the name, but I am not
optimistic.
Fortunately I can easily get by for some time without printing from the
guest on the laptop. I want to hammer through this so that I learn. That
is why I have stuck to bridging mode and using the name rather than the
IP. But I understand there are advantages to NAT. I should be able to
change to NAT when I have exhausted my ability to learn from the bridging
exercise.
I would go to the Clinic were I not signed up for something else through
11/19. If I still have stamina to learn from this after the 19 I will try
to get to the Clinic.
Thanks for all the help. I welcome ideas on how to understand what may be
wrong.
-Denis
On Thu, Oct 12, 2017 at 8:22 AM, Tomas <tomas.kuchta.lists at gmail.com> wrote:
> I cannot see anything obviously wrong with the vBox config you are
> using. Unless, of course the problem is with your Windows setup messing
> things up or you need to poke at the vBox config file (sometimes even
> virtual computers wants to play!).
>
> I would think that there is no harm in trying to change the network
> setup to NAT, it could do two things for you:
> a) isolate the windows from interferring with your host network
> b) reset the vBox config, just in case there is something funny in
> there from your past setup.
>
> To change the setting (your VM must be powered down) you can just run
> this command:
> vboxmanage modifyvm f54caf05-a7ed-450e-be1a-94865fef7e5c --nic1 nat
> Alternatively, you could just select NAT in the GUI
>
> After you do the above, try this:
> 1. start your VM
> 2. ping your router from W2k: in Win start cmd.exe and run:
> ping 10.0.0.1
> 3. as per 2.:
> ping printerIP
>
> If it works, you should be able to setup the printer in windows by
> giving it the printer's IP.
>
> If you do not succeed, I would advice you to go to PLUG clinic for help
> this Sunday. I am sure that Wes/others will be able to help you with
> the networking from your vBox.
>
> Best luck, Tomas
>
> On Tue, 2017-10-10 at 19:00 -0700, Denis Heidtmann wrote:
> > I am impressed with you willingness to help from the other side of
> > the
> > world. Thank you so much for your help.
> >
> > Below is the output you asked for. I have only one VM at present. A
> > friend suggested dig -s 10.0.0.244 to find the name of the printer,
> > since I
> > wanted to avoid the complications of ip address not fixed. But it
> > seems
> > that 10.0.0.244 is the web address of the embedded web server. I do
> > not
> > know if that is what is accessed when printing. But the dig output
> > did not
> > produce a name that I could see. And I see that I can specify a
> > fixed IP
> > address in the printer, so that may not be a concern. And I agree
> > that I
> > need to turn off the "direct" access to the printer.
> >
> > I cannot think of why I would want to have access to the guest from
> > the
> > host. You can see that I use a shared folder to allow me to pass
> > data
> > between the two. If there are other reasons I would want to have
> > that
> > access I am open to suggestions.
> >
> > denis at denis-ThinkPad-L420:~$ for i in $(vboxmanage list vms | awk
> > '{print
> > $2}'); do echo "INFO:
> > >
> > > vboxmanage showvminfo $i"; vboxmanage showvminfo $i; done
> > INFO:
> > vboxmanage showvminfo {f54caf05-a7ed-450e-be1a-94865fef7e5c}
> > Name: Win2kSP2
> > Groups: /
> > Guest OS: Windows 2000
> > UUID: f54caf05-a7ed-450e-be1a-94865fef7e5c
> > Config file: /home/denis/VirtualBox VMs/Win2kSP2/Win2kSP2.vbox
> > Snapshot folder: /home/denis/VirtualBox VMs/Win2kSP2/Snapshots
> > Log folder: /home/denis/VirtualBox VMs/Win2kSP2/Logs
> > Hardware UUID: f54caf05-a7ed-450e-be1a-94865fef7e5c
> > Memory size: 500MB
> > Page Fusion: off
> > VRAM size: 16MB
> > CPU exec cap: 100%
> > HPET: off
> > Chipset: piix3
> > Firmware: BIOS
> > Number of CPUs: 1
> > PAE: off
> > Long Mode: off
> > CPUID Portability Level: 0
> > CPUID overrides: None
> > Boot menu mode: message and menu
> > Boot Device (1): Floppy
> > Boot Device (2): DVD
> > Boot Device (3): HardDisk
> > Boot Device (4): Not Assigned
> > ACPI: on
> > IOAPIC: off
> > Time offset: 0ms
> > RTC: local time
> > Hardw. virt.ext: on
> > Nested Paging: on
> > Large Pages: off
> > VT-x VPID: on
> > VT-x unr. exec.: on
> > Paravirt. Provider: Default
> > State: powered off (since 2017-10-10T00:59:08.000000000)
> > Monitor count: 1
> > 3D Acceleration: off
> > 2D Video Acceleration: off
> > Teleporter Enabled: off
> > Teleporter Port: 0
> > Teleporter Address:
> > Teleporter Password:
> > Tracing Enabled: off
> > Allow Tracing to Access VM: off
> > Tracing Configuration:
> > Autostart Enabled: off
> > Autostart Delay: 0
> > Default Frontend:
> > Storage Controller Name (0): IDE
> > Storage Controller Type (0): PIIX4
> > Storage Controller Instance Number (0): 0
> > Storage Controller Max Port Count (0): 2
> > Storage Controller Port Count (0): 2
> > Storage Controller Bootable (0): on
> > IDE (0, 0): /home/denis/VirtualBox VMs/Win2kSP2 Clone.vdi (UUID:
> > 617a86c4-a14a-4fbb-b4b7-f5e3fe0d6297)
> > IDE (1, 0):
> > /home/denis/.config/VirtualBox/VBoxGuestAdditions_5.0.18.iso
> > (UUID: 71defe8b-0622-4b63-98a0-880e5acb88f8)
> > NIC 1: MAC: 080027D66D3F, Attachment: Bridged Interface
> > 'wlp3s0',
> > Cable connected: on, Trace: off (file: none), Type: Am79C973,
> > Reported
> > speed: 0 Mbps, Boot priority: 0, Promisc Policy: deny, Bandwidth
> > group: none
> > NIC 2: disabled
> > NIC 3: disabled
> > NIC 4: disabled
> > NIC 5: disabled
> > NIC 6: disabled
> > NIC 7: disabled
> > NIC 8: disabled
> > Pointing Device: USB Tablet
> > Keyboard Device: PS/2 Keyboard
> > UART 1: disabled
> > UART 2: disabled
> > UART 3: disabled
> > UART 4: disabled
> > LPT 1: disabled
> > LPT 2: disabled
> > Audio: enabled (Driver: PulseAudio, Controller: AC97,
> > Codec:
> > STAC9700)
> > Clipboard Mode: disabled
> > Drag and drop Mode: disabled
> > VRDE: disabled
> > USB: enabled
> > EHCI: disabled
> > XHCI: disabled
> >
> > USB Device Filters:
> >
> > <none>
> >
> > Bandwidth groups: <none>
> >
> > Shared folders:
> >
> > Name: 'win2kfiles', Host path: '/home/denis/win2kfiles' (machine
> > mapping),
> > writable
> >
> > Video capturing: not active
> > Capture screens: 0
> > Capture file: /home/denis/VirtualBox VMs/Win2kSP2/Win2kSP2.webm
> > Capture dimensions: 1024x768
> > Capture rate: 512 kbps
> > Capture FPS: 25
> >
> > Guest:
> >
> > Configured memory balloon size: 0 MB
> >
> >
> > denis at denis-ThinkPad-L420:~$
> >
> >
> > On Tue, Oct 10, 2017 at 2:22 AM, Tomas <tomas.kuchta.lists at gmail.com>
> > wrote:
> >
> > >
> > > Here is command line which prints your full VirtualBox
> > > configuration:
> > > for i in $(vboxmanage list vms | awk '{print $2}'); do echo "INFO:
> > > vboxmanage showvminfo $i"; vboxmanage showvminfo $i; done
> > >
> > > Post the output here if you are still stuck with the printer
> > > Please check the test for sensitive info - if you have any in the
> > > notes/description, and include only the problematic Windows VM if
> > > you
> > > have more than one configured
> > >
> > > - Tomas
> > >
> > > On Mon, 2017-10-09 at 18:19 -0700, Tomas Kuchta wrote:
> > > >
> > > > Dennis,
> > > > I have another question:
> > > > >
> > > > > Do you need to connect to your windows VM from the host or
> > > > > another
> > > computer/phone on the network?
> > > >
> > > >
> > > > >
> > > > > >
> > > > > > I am thinking that it maybe easier to provide a guide how to
> > > configure you vBox network rather than to debug your issue - over
> > > this mailing list.
> > > >
> > > >
> > > > >
> > > > > >
> > > > > > If I would to provide guidance on fresh network configuration
> > > > > > for
> > > unsupported and unpatched windows - I would probably suggest simple
> > > NAT setup as it provides little more isolation for you windows.
> > > >
> > > >
> > > > >
> > > > > If you need to directly connect to your windows from the host
> > > > > or the
> > > network then bridging setup would be more appropriate.
> > > >
> > > >
> > > > >
> > > > > Depending on your answer, there are pretty good guides
> > > > > available.
> > > Please see if you could follow one of them.
> > > >
> > > >
> > > > The networking in vBox is pretty well described in:
> > > > http://virtualbox.org/manual/ch06.html
> > > >
> > > > >
> > > > > Depending on your need (NAT or Bridge) try to follow the
> > > > > appropriate
> > > section of this tutorial:
> > > >
> > > > https://www.dedoimedo.com/computers/virtualbox-network-sharing.ht
> > > > ml
> > > >
> > > > >
> > > > > >
> > > > > > Note: The tutorial uses host IP examples in 192.168.x.x You
> > > > > > on the
> > > other hand use 10.0.0.x - that is OK - keep your host network
> > > settings - do not get confused about it when following the
> > > tutorial.
> > > >
> > > >
> > > > >
> > > > > If you choose NAT then you host and windows guest IPs should be
> > > > > on
> > > different networks.
> > > >
> > > >
> > > > >
> > > > > If you choose Bridging, your internet router should assign IP
> > > > > to your
> > > windows guest in the same 10.0.0.x range.
> > > >
> > > >
> > > > >
> > > > > >
> > > > > > In both instances, you will be connecting to your 10.0.0.244
> > > > > > printer.
> > > Please note that the printer's IP might change occasionally by your
> > > router, unless configured as static.
> > > >
> > > >
> > > > >
> > > > > As already mentioned, I would disable all other networking
> > > > > stuff such
> > > as internet/HP/cloud printing on the printer.
> > > >
> > > >
> > > > >
> > > > > I hope it helps, for anything else go to PLUG clinic on the
> > > > > right
> > > Sunday.
> > > >
> > > >
> > > > Tomas
> > > >
> > > > >
> > > > > >
> > > > > > On Oct 10, 2017 7:19 AM, "King Beowulf" <kingbeowulf at gmail.co
> > > > > > m>
> > > wrote:
> > > >
> > > > On 10/09/2017 03:14 PM, Denis Heidtmann wrote:
> > > >
> > > > >
> > > > > >
> > > > > > Progress. I got the ip address of the printer from
> > > settings/network in the
> > > >
> > > >
> > > > >
> > > > > >
> > > > > > host, pinged it from the host, then pinged it from
> > > > > > win2k. Both
> > > were
> > > >
> > > >
> > > > >
> > > > > >
> > > > > > successful. But then I found out that the host could not
> > > > > > connect
> > > to the
> > > >
> > > >
> > > > >
> > > > > >
> > > > > > router/modem until I shut down win2k in VB! So it appears
> > > > > > that
> > > either the
> > > >
> > > >
> > > > >
> > > > > >
> > > > > > host is connected to the router/modem or it is connected to
> > > > > > the
> > > printer.
> > > >
> > > >
> > > > >
> > > > > >
> > > > > > This is not the usual way the host connects to the printer,
> > > > > > as I am
> > > able to
> > > >
> > > >
> > > > >
> > > > > print without losing my internet connection. The address was
> > > >
> > > > >
> > > > > >
> > > > > > 192.168.223.100. I need to get rid of this direct connection
> > > > > > to
> > > the
> > > >
> > > >
> > > > >
> > > > > >
> > > > > > printer. Then how do I get the (proper) ip address for the
> > > printer?
> > > >
> > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > --- snip---
> > > >
> > > >
> > > >
> > > > As
> > > >
> > > > >
> > > > > Tomas mentioned, this sounds like something screwy with the
> > > > > host-
> > > guest
> > > >
> > > >
> > > > bridging setup in that when VB+Win2K fires up, the guest has sole
> > > >
> > > > ownership of the NIC. Thus, the laptop host goes "dark".
> > > >
> > > >
> > > >
> > > > you said (?)the printer is on wifi and uses DHCP (not fixed IP).
> > > > The
> > > >
> > > > printer IP address is from the wifi router and has nothing to do
> > > > with
> > > >
> > > > either host or guest OS. You can get the Printer IP by using the
> > > >
> > > > printer front panel to print a Network status page, or log in to
> > > > the
> > > >
> > > > >
> > > > > router web GUI (http://10.0.0.1) to see what IP is assigned.
> > > >
> > > >
> > > >
> > > > >
> > > > > Some printers can advertise over wifi for direct
> > > > > connection. You
> > > will
> > > >
> > > >
> > > > >
> > > > > want to turn that off inside the printer configuration
> > > > > settings.
> > > Either
> > > >
> > > >
> > > > page through the printer front panel or use the printer web GUI
> > > >
> > > > >
> > > > > (http://10.0.0.244)
> > > >
> > > >
> > > >
> > > > -Ed
> > > >
> > > > _______________________________________________
> > > >
> > > > PLUG mailing list
> > > >
> > > > PLUG at lists.pdxlinux.org
> > > >
> > > > http://lists.pdxlinux.org/mailman/listinfo/plug
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > _______________________________________________
> > > PLUG mailing list
> > > PLUG at lists.pdxlinux.org
> > > http://lists.pdxlinux.org/mailman/listinfo/plug
> > >
> > _______________________________________________
> > PLUG mailing list
> > PLUG at lists.pdxlinux.org
> > http://lists.pdxlinux.org/mailman/listinfo/plug
> _______________________________________________
> PLUG mailing list
> PLUG at lists.pdxlinux.org
> http://lists.pdxlinux.org/mailman/listinfo/plug
>
More information about the PLUG
mailing list