B
Brad Pears
Guest
I recently installed a driver for our HP OfficeJet 7310 all-in-one printer
on our Windows 2003 SP2 terminal server. The printer installed fine and I
(being the administrator) am able to print to this printer with no problems
from my session. The printer is configured with a static IP address as we
are using the ethernet interface.
However, when another terminal server users attempts to print to this
printer, the job immediately fails and the print job has to be cancelled
(even a test page) from the queue . I tried setting the "everyone" group to
full access (normally the everyone group has "print" only access) and this
did not solve the problem.
I am unsure as to why no other terminal server user can print to this
printer. It shows up fine in their printer list and shows as "ready".
I also tried logging on as another administrator and was able to print with
no probs - so it appears to be some sort of a permissions issue for sure...
Could there be a registry entry(s) that does not have the correct
permissions perhaps?? There certainly does not appears to be an issue with
teh permission on the print drivers 'Permissions' tab...
I am not sure where to look next!
Thanks, Brad
on our Windows 2003 SP2 terminal server. The printer installed fine and I
(being the administrator) am able to print to this printer with no problems
from my session. The printer is configured with a static IP address as we
are using the ethernet interface.
However, when another terminal server users attempts to print to this
printer, the job immediately fails and the print job has to be cancelled
(even a test page) from the queue . I tried setting the "everyone" group to
full access (normally the everyone group has "print" only access) and this
did not solve the problem.
I am unsure as to why no other terminal server user can print to this
printer. It shows up fine in their printer list and shows as "ready".
I also tried logging on as another administrator and was able to print with
no probs - so it appears to be some sort of a permissions issue for sure...
Could there be a registry entry(s) that does not have the correct
permissions perhaps?? There certainly does not appears to be an issue with
teh permission on the print drivers 'Permissions' tab...
I am not sure where to look next!
Thanks, Brad