virtualbox.org

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?

Try using lpr on the Guest(s).

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.