Another observation: When I initiate a print job, it appears in the Windows print queue as printing. After about 1 minute the error message pops up saying there was an error printing. Soon thereafter the job drops from the queue. I have no idea if this is illuminating information or just "ho-hum".
On Sun, Nov 5, 2017 at 6:17 PM, Denis Heidtmann <denis.heidtm...@gmail.com> wrote: > The saga continues--- > (The subject should be NOT printing from VB) > > It was suggested that in installing the printer from the Win2k guest I > should give the port name of 9100. Did not help. (Note that this is the > name, not the number. The number has on all recent attempts been 9100.) > > I have stumbled on a list of messages in a file accessed through control > panel/administrative tools/computer management/system tools/event > viewer/system Here is one that might mean something to those skilled in > the art. I was asked what the error message was. This is all the detail I > have been able to come up with. > > 11/3/2017 9:13:15 > Printer hp deskjet 990c series was created. > > 11/3/2017 10:28:43 > The document Test Page owned by Administrator failed to print. Win32 error > code returned by the print processor: 3003 (0xbbb). > > Whenever I attempt to print I see this identical error, whether a test > page or document. > > Note that I can ping the printer from the guest, so that hints to me that > the issue is the installation of the printer in windows, not in the > network. I have lost track of how many times I have deleted the printer > and reinstalled. Note that this driver works from the windows2000 guest on > my desktop. I also note that the printer worked before changing the desktop > and the router, although I have had issues in the distant past, details of > which my foggy head cannot recall. > > Is changing to NAT still a thing worth trying? > > -Denis > _______________________________________________ PLUG mailing list PLUG@lists.pdxlinux.org http://lists.pdxlinux.org/mailman/listinfo/plug