Some HP Deskjet not compatible on Metaframe

[Pinkman]

I have a user that has an HP Deskjet 810C. She has a NT machine that runs the Citix client. Whenever she goes to print it takes F-O-R-E-V-E-R. This is true not only through Citrix, but also on her NT desktop. It spools and sits idle for a while, then when THE PC is ready it prints. <br>
<br>
I have tried multiple things all resulting in nothing. I went to the Citrix knowledgebase and found that there are certain models of HP Deskjets that are not 100% NT or Citrix compliant - even though they come with these drivers.<br>
<br>
My main question is if anyone is experiencing this problem and if so - did you get it fixed, purhaps by using another driver. <br>
<br>
I appreciate any responses,<br>
<br>
Pinkman

 

[oneworld]

Hey Pinkman....<br>
<br>
I ran into a similar problem and I beleive that I was forced to use the 640 drivers instead of the 810 ones. That was almost a year ago at a site that I was at so I am doing my best to try and remember. But what I do remember was that I was forced to use a driver from a lesser model printer. If I remember more I will be sure to post it here for you but give the 600 series a shot.<br>
<br>
<p> <br><a href=mailto: oneworld@goes.com> oneworld@goes.com</a><br><a href= > </a><br>

 

[Pinkman]

Oneworld,<br>
<br>
Thanks for the tip. I wish HP would have been as kind and told me to do the same!!!!!!!<br>
<br>
I am going to try the 640 drivers today and I will post my results a little later today.<br>
<br>
Thanks,<br>
Pinkman

 

[LetGeorgeDoIT]

I had a similar problem with one of the newer HP printer/fax/scanner combinations (model unrecalled - but within last year). Had to use a lower level 500c driver if I recall correctly. HP would not even allow it to be shared on a peer network until I used the older driver in same model range. good Luck!

 

[Pinkman]

Oneworld,<br>
<br>
No luck with the 640 drivers. But I think you and George are on the right track. I will try a few drivers and see if I get lucky.<br>
<br>
I will be sure to post my results - even if I set fire to the HP deskjet printers.<br>
<br>
Thanks again guys for the tips,<br>
pinkman

 

[stucker]

I have found that when printer drivers don't work to just pick one that is "built in" to Terminal Server. At the console I go to settings/printer and start the process to add a printer locally. At the manufacturer/model selection I look for the model that the user is trying to get to work. If it is not on the list I just pick one that is close. There also is usually a generic selection like "Deskjet" with no actual model number. Once I find a printer model that is close I have the user select that same model on thier local workstation. This seems to work for any printers where the mfg provided device drivers don't work. So far I would say that about 50% don't.<br>
Hope this helps. Sandy Tucker

 

[netanalyst]

In regards to a DJ 810c printer, hopefully you already have the answer, but if you don't, there are two ways of fixing this problem. 1- edit the WTSUPRN.inf file and reference the 810 printer to the 850 driver which comes default to NT TSE or 2-Install TSE-SP5 and install the actual 810 driver in ALL USER mode.&nbsp;&nbsp;Both will work.