HP Support Forums
Join in the conversation.
12-27-2011 07:55 AM
I have a hp laserjet 1020 that I am vpn and remote desktop to a computer at work. I am suupose to be able to print from remote desktop to my local printer (the hp laserjet 1020) using the microsoft terminal Easy Print. The printer is showing up in the printer list, but when I try to print I get an error of Printer not ready. The printer is working fine on the local machine, just not through the remote desktop. I have install the printer drivers on the machine that I am remoting into , just to make sure. Is there anything else I can try. I am not finding any firewalls on either end blocking it?
12-29-2011 02:02 PM
Thanks for the post. I'm not sure of your full configuration, but I did find this great older article from MS support that I've pasted below. Hopefully, this will help with your VPN/Printer issue.......Good Luck!
Thanks MS support!
*Say thanks by clicking the *Kudos!* which is on the left*
*Make it easier for other people to find solutions, by marking my answer with (Accept as Solution) if it solves your issue.*
03-19-2012 07:59 PM
After many months of frustration and 7 1/2 hours with Microsoft advanced prof support I've finally pinned down this printer and a slew of others. This problem as far as I have come across deals exclusively with HP printers. In simple terms: the drivers are flawed. This 1022 is a prime example. It prints locally and via TCP/IP just fine. I have about 7 other printers and dummy printers in my printer folder. Enter a remote desktop session and ALL of them populate except the 1022. This shows that the hooks and RDT finders are locating your printers and installing them properly as remote printers. All except the 1022.
Log out of your RDT session: goto the local 1022 setup and change the printer driver to a PCL driver. I used a 1200 PCL driver. Now log back into your RDT server and hockus pocus! there is your printer. Totally un-usable because the driver will not run this printer. Caveat: each time I did this XP crashed (I couldn't get to the properties TAB anymore -- I had to un-install the 1022 and then re-install it with at least 1 reboot in the process)
Moving on we go to the HP OfficeJet/LajerJet2840. Same thing. It won't pass through as remote printer in RDT. Go local. Set the printer driver to AppleLaserWriter8500 and boom. (same logout, change, back in steps) and your LJ2840 shows up and works.
While I will have to wait until tomorrow I am betting that this will fix the exact same problem with the HP Officejet 8500A all in one with the exact same problem.
Hey HP? Whats with the drivers??
Another work around if you have a static enough environment is to install your local printer that will not show up under RDT on the server, and then point the port to your fixed IP on your router, and passthru port 9100 to your locally installed printer that is failing. You can now be on RDT and chooses the network printer that is printing to the TCP address of your home (or office) router.
03-25-2012 10:11 AM
We have run in to this issue when setting up our new terminalservices environment. It seems that any printer that is a host-based printer seems to have trouble printing with the Microsoft Easy Print driver. The issues we were seeing however, were that we couldn't print from DOS based applications remotely.
Our work around / fix was to replace any host based printers with non host based printers.
Hope this sheds a little light on your issue!
04-16-2012 08:13 AM
We have this issue when we install from network downloaded drivers. We found a PC that was working and found that it was installed from the CD that came with the 1020 printer. The Test Page has IMFNT5.DLL as it's main driver listed and is version 5.06.
If you install off the CD that has that version it should work fine!
04-16-2012 11:10 AM
found a Laserjet 1020 OEM cd and installed onto a fresh XP SP2 computer...printer worked fine (obviously not in RDP though)
installed SP3 and all updates, restart, prints fine locally...won't even transfer to the TS session despite RDP menu being checked for printers.
04-16-2012 11:45 AM
Tried the MS fixes.
Have also run the Mr. fix it.
This problem is not with a specific printer but with a series of HP printers.
Specifically, the LJ 1020n and HP Color Laserjet 2840.
For the LJ 2480 I set the driver to Applewriter 8500 and it worked. I spent all grades of time on this with Microsoft and they say it is a drier problem, and changing the driver and it magically works is proof. I set the 1020 to a PCl driver and it did show up on RDT but the print drier will not run with it -- it is not a host based driver.
I havea troublr ticket still open with MS and if HP feels it is not an HP issue we can set up a call with Microsoft and remedy the situation.
04-16-2012 11:49 AM
what i don't understand is how have we been able to print via RDP/TS for a good time now, but suddenly, there are problems with this?
Has there been an update to the Easy Print driver that came down? It can't be the HP LaserJet 1020 driver as I used an OEM cd from years ago and it still doesnt work. It also cant be our local computers are we still have dozens of other users printing fine.
04-16-2012 08:29 PM
it sounds like you are suggesting that under SP2 you were able to mark Share Printers in RDT and get them to show when you connected to a server but they didn't work.
And, After updating to SP3 they don't show up at all.
If so, the bottom line is that they do not work under either version. My understanding is that host procesing means there are no languages in the printer: Do ability to understand PCL, Postscript, or even the ascii character set ( hence they don't work in real DOS environments). Their output is some form of raster graphics direct to the printers engine. It understand makes dots here and there,
It can not understnad print 41H which wuould be a capital A in almost all other printers ever made.
HP (and others??) saved a few bucks in the CPU print engine's power.
It could be this would be intollerably slow to send back over a conenction to the RDT client so they disabled it. Thats would sound like MS did it and they claim no responsibility in it not working.
I have tried other suggested workarounds to try and trick Windows Server to see the printer and none of them work.
04-17-2012 05:21 AM
We managed to get a install CD and ran a test install, instead of the box showing the printer but generating an error in the RDP it now no longer shows up at all in the terminal server.
Yet we have another PC running the same version that works perfectly. We are thinking about cloning the box. But I have to wonder if maybe it is an issue with a hotfix/update on the terminal server itself and the users profile happened to already exist before the update.