• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 512
  • Last Modified:

RDP printer not showing up Microsoft issue event 1111

hello everyone,

I'm at my witt's end.  I'm somewhat familiar with RDP and printing.  Host and Remote devices must have same drivers.  I've done this very successfully in past now I'm struggling with a x86 machine connecting to a x64 Win 7 OS.  I've loaded the exact same x86 print driver on the new x64 Win7 OS but every time a x86 device with the x86 print driver hits the new x64 Win 7 (WITH the same x86 printer driver) I get a MS Event 1111- "printer driver HP 4100 PCL (just and example) is unknown".  I know the RDP local resource for printers is working because I get the unwanted XPS added to the RDP session from the remote pc but not the printers I need.  I'm using RDP from PC to PC there is no term server in the mix if that help you understand my environment a little better.   Please any guidance out there?
0
jo80ge121
Asked:
jo80ge121
  • 6
  • 3
2 Solutions
 
NetfloCommented:
Have you tried using the HP Universal Print driver as an alternative on both machines and does this help?
0
 
jo80ge121Author Commented:
I will try that now.  Should I load both x86 and x64 on the host pc Win7 x64? the remote pc is only x86
0
 
jo80ge121Author Commented:
changing both ends to HP universal worked however we support a remote connection to an outside office that is dedicated to use a specific HP 4100 PCL5 driver x86.  When I test it with this I always get the Event 1111 error "printer unknown" .   I found this below what do you think?  the section where is says to add the registry keys.  

http://technet.microsoft.com/en-us/library/ee891383(v=ws.10).aspx
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
jo80ge121Author Commented:
How come the 32bit drivers I load in the 64bit print server properties do no show up in the Advance tab of the a printer property window?
0
 
NetfloCommented:
Go to the Sharing Tab followed by clicking on Additional Drivers at the bottom. Does it say installed for x86 (32bit)? If not, looks like you have inconsistencies on the driver version which needs to be the same for this dialogue box to say yes.

Try taking a look at Control Panel -> Administrative Tools -> Print Management
Drill down to Print Servers -> PCNAME (Local) -> Drivers

Do you have the same driver and version number for x64 and x86 environments?
0
 
jo80ge121Author Commented:
No I do not have the same driver for the x64 and x86 enviroment.  I've been all over the web for a HP LaserJet 4100 PCL 5e x64 bit but couldn't find it.  

My question is that I can load a x86 on my x64 but why doesn't the x64 show me that other than in the server properties window?  In a Printer properties window on the host RDP I do not even see the x86 driver I loaded in the drop down list under the Advance tab BUT when I go to the server properties window I can see them in the driver list?
0
 
NetfloCommented:
Okay I had a look as well and it looks like HP don't have a 64 bit driver at all, other than the universal print driver.

In reply to your question, you're able to load a 32 bit driver as its valid and the issue is here you're dealing with different architecture of machines.

You essentially want the 32 bit driver to be presented to your client when RDC into your x64 host. But as there is no valid 64 bit equivalent driver present, the printer doesn't render.

Looks like you've hit a snag and I can only think to use the HP universal print driver (which works) or replace the printer with a modern equivalent which will have proper 32bit and 64bit drivers written for it.
0
 
jo80ge121Author Commented:
I agree Neflo.   Either change the printer or update the driver of the printer to a UPD.
0
 
jo80ge121Author Commented:
Netflo - in a pinch the link below in my previous post does work.   I was able to redirect the 4100 pcl 5e 32bit client side to a HP universal 64bit on the server side.  But there is no doubt from an IT support position the true fix is what you helped me conclude- replace the printer if you cannot use a 32bit & 64bit driver written for it.  


http://technet.microsoft.com/en-us/library/ee891383(v=ws.10).aspx 
(tip - don't just restart spooler, reboot the server side after applying the registry edit).
0

Featured Post

Upgrade your Question Security!

Add Premium security features to your question to ensure its privacy or anonymity. Learn more about your ability to control Question Security today.

  • 6
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now