This sounds like a security issue. When you reboot the machine, the spooler
no longer has the security ID of the sender and schedules the job in system
context. The job will most likely print if you stop and start the spooler.
Now the real question is why the printer will not work for one user until a
spooler restart.
Does the user it works for have admin rights on the machine that shares the
printer?
--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
This posting is provided "AS IS" with no warranties, and confers no rights.
"RST" <> wrote in message
news: ps.com...
> On Sep 18, 10:56 am, fanofthemick
> <fanofthem...@discussions.microsoft.com> wrote:
>> I have a shared printer on a Vista system and 2 XP systems on the same
>> Workgroup. One of the XP systems can print to the shared Vista printer
>> with
>> no problem. The other sends the file to the queue but it doesn't print
>> until
>> I reboot the Vista system. I can't kill the print job and no other jobs
>> will
>> print until the problem one prints on re-boot. This happens regardless
>> of
>> what the content of what I am trying to print - emails, Word, Excel,
>> etc. -
>> it happens to any data sent to that printer form the other PC. Any
>> suggestions on the cause and solution? The printer is an HP 1020 Laser
>> connected via a USB port. It used to work until I plugged the printer
>> into a
>> different USB port on the Vista system and now the same thing happens
>> regardless of what USB port it is plugged into.
>
> Probably another Vista print spooler problem.
>