Vbox v3.0.4, bridged network
host: openSuse v11.1
guest1: win xp sp3
guest2: os/2 v4.52
printer server: os/2 server v4.52
Neither guest has succeeded in actually printing anything. They both see and access the server's shares to create printer objects. But when a test page is printed, it sits forever in the printer queue.
The linux host can also see and access the remote printers. And print a test page both to a smb share and directly to an LPR port on one of the smb-shared printers. And it prints.
The blockage, then, is somewhere between the guest's printer output and the linux host.
Any suggestions where to look for the broken connection?
[Solved] Guest VMs not printing
Re: Guest VMs not printing
Try using lpr on the Guest(s).
[This space is intentionally left blank]
If you can read this, you can read the VirtualBox Manual, the Forum FAQ, and the QuickClick FAQ
-=[ Search this forum with Keywords, VirtualBox solutions at you're fingertips]=-
If you can read this, you can read the VirtualBox Manual, the Forum FAQ, and the QuickClick FAQ
-=[ Search this forum with Keywords, VirtualBox solutions at you're fingertips]=-
-
jimoe
- Posts: 126
- Joined: 20. Jul 2009, 05:59
- Primary OS: openSUSE
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: os/2, win-xp, win-10
Re: Guest VMs not printing
Okay, that worked. Thanks!
The reason the SMB connection failed after the initial success was that Windows decided that the connection was broken and placed the printer driver offline. Selecting "Use printer online" always failed. This is obviously not the case for a native installation. Is this a limitation of the "bridged adapter" network setup?
After setting up the LPR ports, the "Use printer online" option worked and continues to do so between Windows invocations.
The reason the SMB connection failed after the initial success was that Windows decided that the connection was broken and placed the printer driver offline. Selecting "Use printer online" always failed. This is obviously not the case for a native installation. Is this a limitation of the "bridged adapter" network setup?
After setting up the LPR ports, the "Use printer online" option worked and continues to do so between Windows invocations.