up vote 0 down vote favorite
share [g+] share [fb]

I am having problems with users printing to a HP Color LaserJet 3600dn, with its queue shared from a Windows2003 R2 Standard Server VM on ESXi.

The server and printer are in the same subnet; sometimes clients (Windows XP) trying to print from other subnets get no error message but nothing is printed. Looking in the server event viewer, I find this error message:

The document my_document.doc owned by my_user failed to print on printer my_printer. Data type: NT EMF 1.008. Size of the spool file in bytes: 1441792. Number of bytes printed: 24. Total number of pages in the document: 1. Number of pages printed: 0. Client machine: \192.0.2.5. Win32 error code returned by the print processor: 259. No more data is available.

I do not know if I should be looking at the server or the firewall, for the following reasons:

  • This has been detected when printing from another subnet should point to firewall, but then I would expect it to always fail or always succeed. We do not manage the firewall, and given that everything else is working correctly I do not believe this to be an issue.
  • The problem occurs with this particular model, this points me to the server. But that does not explain why PCs in the same subnet show no trouble at all.
  • The printer hardware error has been ignored, it happens in two different printers.
  • Initially I thought it might be a communication error. I setup a new server on an old PC in the same CPD but with the subnet of the clients that were having trouble and since then there have been no more troubles.

Any idea of what could I check / what setups I could try in order to, at least reduce the scope of things that may be causing this?.

link|improve this question
100% accept rate
2  
You don't seem to have a good grasp of basic networking, network printing, or Windows server administration. You should call in someone who does, perhaps a boss, co-worker, or hired consultant. – Chris S♦ May 17 '11 at 14:01
feedback

1 Answer

up vote 0 down vote accepted

It looks like I was looking for the wrong code: looking for the event ID (6161) led me to http://social.technet.microsoft.com/wiki/contents/articles/windows-server-troubleshoot-event-id-6161-print-spooler-status.aspx

In the page, it listed several posible messages from the spooler and the one I was looking for was there. A senior SA has recommended increasing memory (actually it is 2GB), I'll try it in a few days.

EDIT 05/13/2011: The error has appeared again, last step will be using a different version of drivers (but these work well in another server!!)

link|improve this answer
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.