W
wim.wauters@unisoftdesign.co.uk
Guest
Hi all,
I have a remote site which has this very consistent problem:
they can print on their WASP lable printer fine (it runs off of one of
the PCs),
but when trying to print to their local printer (an HP 2600n, through
a TCP/IP port),
they keep getting an extra print jobs:
- which are empty
- first one can't be deleted
- first one stalls the PC's printer queue and the printer itself
Restarting the spooler clears the problematic first empty print job,
but my long suffering network users don't get access to windows
services...so they end up rebooting their PC instead.
The local printers can't be reached directly from the terminal server,
as this would require investing in a VPN endpoint. They are not
getting a windows 2008 server neither (to run a TS gateway).
Since the label printer works fine, I reckon the HP2600n should too.
HP support is coming up blank so far.
Anybody else out there came across this empty print job problem?
WFR,
Wim Wauters
UnisoftDesign.co.uk
IT sysadmin
I have a remote site which has this very consistent problem:
they can print on their WASP lable printer fine (it runs off of one of
the PCs),
but when trying to print to their local printer (an HP 2600n, through
a TCP/IP port),
they keep getting an extra print jobs:
- which are empty
- first one can't be deleted
- first one stalls the PC's printer queue and the printer itself
Restarting the spooler clears the problematic first empty print job,
but my long suffering network users don't get access to windows
services...so they end up rebooting their PC instead.
The local printers can't be reached directly from the terminal server,
as this would require investing in a VPN endpoint. They are not
getting a windows 2008 server neither (to run a TS gateway).
Since the label printer works fine, I reckon the HP2600n should too.
HP support is coming up blank so far.
Anybody else out there came across this empty print job problem?
WFR,
Wim Wauters
UnisoftDesign.co.uk
IT sysadmin