T
Thomas M.
Windows XP SP2
I support an office that recently purchased a USB label printer. The manual
for the printer indicates that it can be networked if the separate USB print
server is purchased, which they did not do. Of course, now they want to put
the label printer on the network, but they have killed the idea of
purchasing the USB print server to make that happen. So we've attached the
label printer to a client PC that will act as the print server. Our network
is Novell, which uses UNIX to do network printing. I want to stress that
while we are on a Novell network, I believe that this is a *Windows* problem
(my reasons for believing this will become apparent in a moment).
Here's the current setup: The label printer is attached to Angie's PC via a
USB cable. It is installed as a local printer on Angie's machine and is
shared out as DOAAEDL. Another user named Janelle needs access to the label
printer. We've setup the label printer in Novell. When Janelle tries to
print to the label printer, Novell returns a message saying that the
document printed successfully, but nothing actually prints. Both the Novell
and Windows print queues are empty, and Windows does not return an error
message on Janelle's computer. So from Janelle's computer it's as if
everything worked fine, and since Novell does not return an error either,
it's clear that the network thinks everything worked fine as well.
However, if I look at the System log on Angie's computer, I see some 4008
and 4010 errors generated by NPDSVC. I looked up the 4010 error and found
article 318713 (http://support.microsoft.com/kb/318713). The problem is
that the article refers to Windows 2000, and I have the problem on a fully
patched Windows XP machine with the latest service pack installed.
It's clear to me that the print job is making it all the way through to
Angie's computer, and that it's getting killed there for some reason. I
just don't know why. Maybe her machine needs to be running a protocol or
service to handle the UNIX print job that it receives from the network?
At any rate, I'm stumped. Does anyone know how to fix these errors on a
Windows XP SP2 machine?
FYI: I already searched the Novell site, and they've got squat for these
errors.
--Tom
I support an office that recently purchased a USB label printer. The manual
for the printer indicates that it can be networked if the separate USB print
server is purchased, which they did not do. Of course, now they want to put
the label printer on the network, but they have killed the idea of
purchasing the USB print server to make that happen. So we've attached the
label printer to a client PC that will act as the print server. Our network
is Novell, which uses UNIX to do network printing. I want to stress that
while we are on a Novell network, I believe that this is a *Windows* problem
(my reasons for believing this will become apparent in a moment).
Here's the current setup: The label printer is attached to Angie's PC via a
USB cable. It is installed as a local printer on Angie's machine and is
shared out as DOAAEDL. Another user named Janelle needs access to the label
printer. We've setup the label printer in Novell. When Janelle tries to
print to the label printer, Novell returns a message saying that the
document printed successfully, but nothing actually prints. Both the Novell
and Windows print queues are empty, and Windows does not return an error
message on Janelle's computer. So from Janelle's computer it's as if
everything worked fine, and since Novell does not return an error either,
it's clear that the network thinks everything worked fine as well.
However, if I look at the System log on Angie's computer, I see some 4008
and 4010 errors generated by NPDSVC. I looked up the 4010 error and found
article 318713 (http://support.microsoft.com/kb/318713). The problem is
that the article refers to Windows 2000, and I have the problem on a fully
patched Windows XP machine with the latest service pack installed.
It's clear to me that the print job is making it all the way through to
Angie's computer, and that it's getting killed there for some reason. I
just don't know why. Maybe her machine needs to be running a protocol or
service to handle the UNIX print job that it receives from the network?
At any rate, I'm stumped. Does anyone know how to fix these errors on a
Windows XP SP2 machine?
FYI: I already searched the Novell site, and they've got squat for these
errors.
--Tom