They are using the driver supplied with the printer (HP LaserJet P1006).
On the terminal server, are the users using the HP LaserJet 4 driver on the server? If not, then you've specified the driver wrong in the file or you never loaded the driver on the server.
I have the dummy INF file pointed to the LaserJet 4 driver. I loaded the LaserJet 4 driver through Print Management on the TS.
How can I tell if the users are using the LJ4 driver? Whenever a user logs in, a printer is created for the session. Does that change from login to login? For instance, user A is always logged into session 3, or user A is the 1st to login today, so he gets session 1. Make sense?
If you configure your 'view' (from the menu) to details you'll be able to see what driver is being used.
There is one person connected currently. She is using the driver for the printer attached to her local machine (HP LaserJet P1006). If I right click on her printer session, Properties, Advanced, I can change the driver to the HP LaserJet 4 there, then save. Is this how I change the driver? Do I need to restart the spooler or have her disconnect/reconnect from the VPN?
Thanks a lot.
I changed the driver to HP LaserJet 4, restarted the spooler and tried printing with no luck. I changed the driver back to HP LaserJet P1006, restarted the spooler and was able to print something.
This would be fine if the settings saved after the user logs off, but that is not the case.
I don't think this printer is going to work for me. I've tried the PCL drivers from the install CD to no avail.
I am upgrading to Windows Server 2008 Wednesday morning, which includes EasyPrint. Hopefully this fixes the problems.
I am having the same #$@% problems with a HP LaserJet P1006 printer - I am about to throw this thing out the window.
Thanks for the help here though!
As Jeff said, this is a classic bad printer driver issue. HP states, regarding the P1006:
Also you said that the remap of the driver using the INF file did not work.
So next steps:
- fix the mapping issue (edit the INF)
or
- Replace the local client driver for a HP4 (a printer for use in TS)
Also Server 2008 is much better with these issues but it will not fix the bad driver.
--Emil
OH and I want photos of the printer being thrown out the window
I've tried the INF route with no luck. When a user was connected, I changed their driver to the HP4, no luck.
My upgrade to Server 2008 is almost done. I will report my findings.
I'm an SVP with Suddenlink. I'm not sure who the participant in this forum is using our company name, but I would respectfully ask that you NOT use our company name in your posts in this forum since you are not authorized to speak on behalf of Suddenlink. Please contact me at pete-DOT-abel-AT-suddenlink-DOT-com with any questions. Thank you.
Hi,Given by friends from the links you may have seen your work. To help, but I wanted to give an alternative link.HP Laserjet P1006 Driver
Good Luck
We had similar issues on 2003 r2 and the only way we were able to resolve it 100% was by using the HP universal driver for TS.
We haven't had any problems thus far in any of our 2008 r2 environments. Hope this helps.