virtualbox.org

My system:
VitualBox: 6.1.14
Host: MX Linux 19.3
Desktop: Xfce
HP printer Envy 5544
Guest: Windows 7

My Hardware:
HP PC with Intel processor Generation 4 and 8 GB RAM

I was successful with making my HP printer available for VirtualBox and my VM.
I was successful to install the windows print driver in my V M. But now the problems start:


Issue 1:

Bug:
1. start Linux
2. start VirtualBox
3. start VM Windows 7
4. open MS Word
5. turn on the printer

Result:
A) The printer display shows the following message: "Error Code 0XB88670D0".
B) The VM no longer works. I cannot close MS Word and I can not shut down Windows 7. So I have to "switch off" VirtualBox





Issue 2: I can print, but there is an unexpected message from the windows print driver:

1. start Linux
2. turn on the printer
3. wait until the printer is ready
4. start VirtualBox
5. start VM Windows 7
6. open MS Word and print a document

Result:
After a few seconds a dialog box from the printer driver installed in Windows appears with the message: "Communication with printer not possible".
Two seconds later it prints normally. I can close the dialog box with the message. 7. if I then leave the Windows VM and MS Word open and turn off the printer, it takes more than 20 seconds for the printer to turn off. Normally (outside the VM) it takes less than 7 seconds.


Would appreciate some help. Thank you.

Putting physical hardware into a VM, even through USB, can have problems. You just have to find a method that works, then only use that method, and accept what happens, as long as the method works.

Use the method under Issue 2, and tolerate the popup box, because the printer still prints. Don't turn the printer off until the VM is turned off first, or do something else for the extra 13 seconds you have to wait.

A more practical setup is to connect the printer to the host OS only if possible, and share the printer to the VM over a Bridged or Host-Only network.

Thank you.

A more practical setup is to connect the printer to the host OS only if possible, and share the printer to the VM over a Bridged or Host-Only network.

Do I need SaMBa Server for MS Networking on the host for A) and B) ?
A) share the printer to the VM over a Bridged network
B) share the printer to the VM over a Host-Only network

Plagrö wrote:Do I need SaMBa Server for MS Networking

I am no Linux guru, but I have heard that Linux networking and shared folders that Windows can use is called Samba.

Bridged puts the VM on the same Ethernet network as the host PC. Host-Only makes a private Ethernet network between the host PC and the VM only. Either acts like an Ethernet network. Virtualbox Networks: In Pictures

Pretend you have a Linux PC and a Windows PC networked together, and you want the Windows PC to use the printer attached to the Linux PC. This would be a standard web-search problem, not a Virtualbox problem.

Plagrö wrote: Do I need SaMBa Server for MS Networking on the host for A) and B) ?

Yes.

SaMBa is Linux's implementation of the Windows SMB networking protocol, so if you want to talk to a Windows network like a Windows PC does then yes you need Samba. I don't keep up with Linux but I assume Samba will have kept up with SMB versions, i.e. SMB2 support will be needed if you want to talk to modern secure Windows networks.

I should mention that I've never had to install SAMBA. It's always been part of the default bundle of the desktop distros I install (typically Mint and Ubuntu desktop).

Thank you.

I should mention that I've never had to install SAMBA. It's always been part of the default bundle of the desktop distros I install (typically Mint and Ubuntu desktop).

When I was installing my Linux I have unchecked SAMBA during the installation process, because at that time I needed no network.