Hi Everyone,
My work has a main office in Victoria (Australia) and a regional office in Queensland. The two offices are separated by about 1700 kilometers, and they are connected by VPN. Often the Victorian office sends print jobs to the regional Queensland office.
In the Queensland office we have an XP computer connected to a Kyocera (FS-2000) printer, and lately we have been seeing some strange entries in the Windows Print Spooler:
.JPG)
Even though you may conclude that nothing will print with the spooler in this condition surprisingly print jobs still get through to the printer, it is as if they skips past the jobs that are "stuck"!
Even more confusing we are often seeing "N/A" for the number of pages on some spooled print jobs:
.JPG)
Once again you might assume that no print jobs will be able to get through with the spooler in this condition, however this is not always the case! However sometimes it is!!!
Usually rebooting the computer (in Queensland) helps, but sometimes we also have to reboot the Server in Victoria.
If anybody has any suggestions on how to resolve this, or what might be the cause of this it will be greatly appreciated.
Kind Regards,
Davo
P.S.: Here is a video showing the strange behaviour: http://www.youtube.com/watch?v=eJfXB...ature=youtu.be
My work has a main office in Victoria (Australia) and a regional office in Queensland. The two offices are separated by about 1700 kilometers, and they are connected by VPN. Often the Victorian office sends print jobs to the regional Queensland office.
In the Queensland office we have an XP computer connected to a Kyocera (FS-2000) printer, and lately we have been seeing some strange entries in the Windows Print Spooler:
Even though you may conclude that nothing will print with the spooler in this condition surprisingly print jobs still get through to the printer, it is as if they skips past the jobs that are "stuck"!
Even more confusing we are often seeing "N/A" for the number of pages on some spooled print jobs:
Once again you might assume that no print jobs will be able to get through with the spooler in this condition, however this is not always the case! However sometimes it is!!!
Usually rebooting the computer (in Queensland) helps, but sometimes we also have to reboot the Server in Victoria.
If anybody has any suggestions on how to resolve this, or what might be the cause of this it will be greatly appreciated.
Kind Regards,
Davo
P.S.: Here is a video showing the strange behaviour: http://www.youtube.com/watch?v=eJfXB...ature=youtu.be
Comment