Printing locally via Remote Desktop

Hello.  I am running Windows 8.1 locally and am connected via remote desktop to Windows Server 2012 r2.  I am trying to print locally on an HP Officejet Pro 8620 that is connected USB to the Windows 8.1 machine.  I have the same driver installed on both machines.  I have tried printing with Easy Print turned off and on.  I have also tried creating a printer profile on each machine using port LPT1.    And of course I have the selection checked on the local machine to use local resources.  None of the above have produced printer output locally.
Does anyone have any input?  I have searched only a little here and will search more as well as read available articles.  Thank you in advcance.
klittle11Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Chris HInfrastructure ManagerCommented:
try:

On the client launch Regedit.

Navigate to HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\AddIns\RDPDR

Add a key of type DWORD named FilterQueueType with value ffffffff

- See more at: http://techiezone.rottigni.net/2012/12/terminal-client-printer-redirection-magic/#sthash.egHKgCN0.dpuf


Also, do you know if you have printer redirection disabled on the RDS connector on the server or not selected on the RDP client?
0
klittle11Author Commented:
Hello, I added the key and no change.  I made sure printer redirection was turned off.  Disconnect RDS, reconnected and local default printer still lists as (redirected 2) in available printer list.  Still no print output on local pc side.
0
Chris HInfrastructure ManagerCommented:
Log out of user.  Log in as admin.  Set recursive "full access" rights on the c:\users\%username% per the user.

Then, import that users ntuser.dat in regedit (as admin) and set recursive "full access" on the whole registry key.  (Don't forget to close the registry key!)

Let me know if you need me to elaborate on those steps.
0
Cloud Class® Course: Certified Penetration Testing

This CPTE Certified Penetration Testing Engineer course covers everything you need to know about becoming a Certified Penetration Testing Engineer. Career Path: Professional roles include Ethical Hackers, Security Consultants, System Administrators, and Chief Security Officers.

☠ MASQ ☠Commented:
The printer you're using isn't supported for use in a remote desktop environment, it falls into the category of HOST-bast printing where the processing function of the printer is handled locally by the operating system on the client rather than being managed by the printer itself.  Because of this the usual RDC functions for printing won't work as the local management can't be transferred over from the server for the local client to manage.

HP maintain a list of printers that are able to connect in this way which can be found here
http://h20195.www2.hp.com/V2/getpdf.aspx/4AA0-8465ENW.pdf

Any printer on this list will work as you describe (provided you use the recommended driver packages on server and client)
0
Tony JLead Technical ArchitectCommented:
Lets go back to basics. Have you enabled local printer mapping in the RDP client?

1.Open the remote desktop connection program (MSTSC.EXE)
2.Click Show Options in the Remote Desktop Connection dialog box.
3.Click the Local Resources tab.
4.Check Printers in the Local Devices box

It is also worth checking the ports, but I don't recall this being necessary.

5. From the same page as step 4 - Click More
6. Check Ports and Other Supported Plug and Play (PnP) Devices

Use the basic printer driver from here:

http://support.hp.com/us-en/drivers/selfservice/HP-Officejet-Pro-8610/8620/8630-e-All-in-One-Printer-series/5367611/model/5367613

(Direct download link) http://ftp.hp.com/pub/softlib/software12/COL51217/bi-124140-4/OJ8620_198.exe

Put this driver on both the server and client and see how you get on.
0
klittle11Author Commented:
Hello,

For Tony1044 comments -  I had done all mentioned.

For CHoward16980 - I had also done all mentioned.

For MASQ - I am scheduled to install an approved printer from the article you sited.  I will post the results.
0
Chris HInfrastructure ManagerCommented:
Can you try setting the print to a different printer driver on the client side, something unsupported or a laserjet and see if you at least get windings?  

If not, you're probably facing a firewall issue on client or some printer subsystem issue on your server.  

Client:
-is av off?  Uninstall it for test.  Uninstall any security software just to test.  Disable Windows firewall
-Does printer only show up once in devices and can you queue a test page?
-uninstall all printer drivers pertaining to this model printer and make sure to choose DELETE
(Do for both x86 and x64 bit versions)


Server:
-stop print spooler and delete c:\windows\system32\spool\printers
-start print spooler
-uninstall all printer drivers pertaining to this model printer and make sure to choose DELETE
(Do for both x86 and x64 bit versions)
-disable easy print


Install  the appropriate driver (CHOOSE ONE) on both server and client.

8620 basic driver 32-bit
http://ftp.hp.com/pub/softlib/software12/COL51220/bi-124146-4/OJ8620_Basicx86_198.exe

8620 basic driver 64-bit
http://ftp.hp.com/pub/softlib/software12/COL51393/bi-124466-4/OJ8620_Basicx64_198.exe


If it auto installs on the client because the printer gets plugged in, right click the printer in device manager, update driver, pick the above driver package directory where it extracted to.
0
klittle11Author Commented:
Got wingdings to print on client side using HP Universal Driver PCL5.  So local printer is getting commands now.  

Any suggestions on printing garbage with the above driver?
0
Chris HInfrastructure ManagerCommented:
At least we know they're talking.  STep 2, remove all remnants the 8600 series on both client and server.

http://wirthconsulting.org/2012/03/20/how-to-%E2%80%98really%E2%80%99-remove-unused-print-drivers-from-your-pc/#Windows-8
0
Chris HInfrastructure ManagerCommented:
Also is your server x64 and is your client x64?  What are the architectures.
0
Chris HInfrastructure ManagerCommented:
0
klittle11Author Commented:
Installed a new HP LaserJet Pro 400 M401.

Installed most current driver for unit on both ends, local client and server.  No Print.  Not even wingdings.

Installed Universal PCL6 version 6.3.9600.17415 on both ends and during remote desktop session we get a general error that printer could not print.

Anyone have suggestions on what is next?
0
☠ MASQ ☠Commented:
Do you mean RDC Version 6.3.9600.17415 and PCL6 UPD Driver Version 6.0.0.18849?

Assume the M401 is printing locally OK via USB
On the same network as the 2008R2 server (not using VPN etc)?

The hardware should (in theory) all work with the setup you're describing(!) so we may be back to a networking settings/permissions or even corrupt client OS.  Worth going back through choward16980's troubleshooting list above from the top.

Do you have another client you could plug the printer into to see if you get the same issue?
0
Chris HInfrastructure ManagerCommented:
1 RESET THE WINDOWS FIREWALL on the 2012R2 server.   Don't do anything until you do this....

2 RESET THE WINDOWS FIREWALL on the client.

3 Share the printer on the client computer via SMB  (you're usually asked at the end of the install to share)

4 Connect to the shared printer on the SERVER session via UNC path   (ie \\mycomputer then, right click the shared object printer and click CONNECT)    Also, make sure you're logged in as an ADMIN  on the 2012 R2 server.

5 Print to the shared connection

-----

^ this will indicate if you're printer subsystem is working, the firewall isn't jacked up and you're able to at least communicate with the client computer.  If this doesn't work or you still don't print output, it IS a problem with the printer subsystem as you've already communicated with the printer if you were able to connect.

Please perform the above to get a printed output on the new laserjet 400
0
klittle11Author Commented:
Ok, I finally got it.  This was a group effort for sure.

Got it to print, but only wing dings after CHOWARDS16980's troubleshooting list.  That was progress for sure.

Then decided to Install the HP LaserJet Pro 400 M401 after MASQ's post and reading the article link.

Then I was back to no printing with the Universal Print Driver (which I have had issues with in so many networking situations regardless of the printer make and model).

Installed the basic driver on client and server side and YEA!  it worked finally!!

Thank you all for your input, as you can tell I am rusty on the server side of things and it really helped straighten out my troubleshooting to be having a conversation, Thank You!
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
klittle11Author Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for klittle11's comment #a40935508
Assisted answer: 250 points for ☠ MASQ ☠'s comment #a40916963
Assisted answer: 250 points for choward16980's comment #a40925176

for the following reason:

Ok, I finally got it.  This was a group effort for sure.

 Got it to print, but only wing dings after CHOWARDS16980's troubleshooting list.  That was progress for sure.

 Then decided to Install the HP LaserJet Pro 400 M401 after MASQ's post and reading the article link.

 Then I was back to no printing with the Universal Print Driver (which I have had issues with in so many networking situations regardless of the printer make and model).

 Installed the basic driver on client and server side and YEA!  it worked finally!!

 Thank you all for your input, as you can tell I am rusty on the server side of things and it really helped straighten out my troubleshooting to be having a conversation, Thank You!
0
Tony JLead Technical ArchitectCommented:
I said to use the basic print driver very early on in this discussion and yet I get no credit?
0
Chris HInfrastructure ManagerCommented:
Not to bust chops, but I believe your direct link above:

(Direct download link)  http://ftp.hp.com/pub/softlib/software12/COL51217/bi-124140-4/OJ8620_198.exe

actually links to the full package and probably complicated the problem.
0
Tony JLead Technical ArchitectCommented:
Hmm. It definitely didn't at the time I posted it. But nevertheless I very specifically said to put the basic driver on both the server and client and this turned out to be the solution.  

To quote myself:

"Use the basic printer driver from here: 

<links from above removed>

Put this driver on both the server and client and see how you get on."

However you want to argue a changed link the OP closed with the statement that my proposed solution was the correct one.
0
Tony JLead Technical ArchitectCommented:
Actually, being pedantic, I didn't just contribute but I identified the actual solution. No only did I do this early on in the discussion but I was the first person to do so...
0
Chris HInfrastructure ManagerCommented:
Even with the full driver set, or with easy print, and also mentioning he did just what you said, the printer would not produce an output. I believe the server-side printer was goofed and shuffling things around remedied it.  

I think the full solution was to delete printer and printer port, delete driver on server and client, re-install basic driver on both, and  matching the cpu architecture (which was never provided) and driver version appropriately.
0
Tony JLead Technical ArchitectCommented:
I disagree. Sorry. 20 years of experience with Thin Client technologies tells me that using the correct driver combination was the solution.

I've seen similar issues time after time after time and full function and/or mismatched drivers - particularly non corporate printers from HP (and doubly so for USB connected devices) - are almost always the cause.

I would hazard that the steps weren't done properly in the early stages. Particularly, as you pointed out, that the link to the direct download was erroneous.

Taking the comments from the closing statement as they were actually written, using the basic drivers on both server and client fixed the issue. Using the basic drivers on both the server and client was my suggestion. The two match.

I could say I should have all the points since it's pretty much cut and dry and frankly the rest of the chatter just confused things but I am only asking for some credit where it's due.
0
Tony JLead Technical ArchitectCommented:
Thanks. So after everything I still get no acknowledgement that I gave the solution and the asker even admitted this?!
0
klittle11Author Commented:
Hello All,

I posted a comment to the above from my phone, but I guess it did not take.

Tony, installing the basic driver for the original printer did NOT work.  The original printer has the "basic driver" that you recommended and it did not remedy the situation.  

Read ALL the posts and you will see that I installed a second printer, purchased specifically due to the article that MASQ posted.

By "basic" printer driver I did not mean one from the lists that you posted for the original printer, so I am sorry for that poor use of language.  What I meant by basic driver was not the full printer driver available to the average consumer.
0
Tony JLead Technical ArchitectCommented:
I won't carry on protesting, but yet again you are referring to the basic driver. The driver that removes all of the bells and whistles such as the printer ink levels. AKA the corporate or non-consumer driver. Otherwise known as the very driver I said to install on both the server and client. You will, in all likelihood, find it's the same driver across all the models as HP moved to a unified model some years ago.

But the question is closed and however unfairly I feel that it was done, then so be it. The important thing is that you found a solution.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Remote Access

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.