Terminal Server...fighting with this particular printer

YeOldeStonecat

Well-Known Member
Reaction score
6,691
Location
Englewood Florida
I usually have a pretty good method for getting a terminal server to support printing to an end users remote printer. Find the latest corporate/.inf drivers..manually add drivers to the driver tab under print server properties, then update the remote workers computer with the latest drivers...and the RDP session usually "populates" it just fine. For stubborn ones that don't auto populate, I'll manually add printer through the remote workers RDP session..fake the install to LTP1 or something..and then once installed..flip it to the TS001 port..and it's all set.

Have a stubborn one here though.
Server 2008 Terminal Server
XP Pro remote client
She has an Officejet 6300...worked for years. It died..she picked up its replacement, an Officejet 6500 A Plus...710n. I go to HPs site...only has drivers for Win7/Vista 32 or 64..and XP. So I download the Win7/Vista ones..sometimes they'll work fine on server. But it's a setup only fine...no unzipping of .inf files. Double click it to launch..and it stops with a "This operating system is not supported"..and closes.

I found "Corporate Drivers" for a similar model..a 709n...figured cool..close enough. Got it working...but when she logs out, logs in again the next day..the prior TS port goes "inactive"..she has to right click..run as admin..go to change the port to the next available TS port. And even that doesn't always work.
 
I don't know for sure in this case. but in similar circumstances I have downloaded a HP driver installation package - extracted the exe file using 7zip, allowing me to access the necessary individual files, and then manually installed in a manner similar to what you described earlier. I did download the driver you mentioned above (e710n) and it does extract using 7zip.
 
There's a Microsoft White Paper on Terminal Server and Printer since Terminal Server was released with Windows NT. It was a separate package then. I have deployed TS using Windows NT, 2000 and 2003 servers and always have printing issue with local printer. I haven't tried Windows 2008 if the issue is still the same. However, one thing for sure RDP is keeping up with ICA.

On a terminal server environment, do not connect the printer to the server or workstation. Set it up as a network printer. It performs better than a local printer. If the printer doesn't have the capability, then you can connect an external Print Server. Stay away from Wireless Print Server

Of course if you have a local apps and not connected to a Terminal Server, then local printer is still better.
 
I don't know for sure in this case. but in similar circumstances I have downloaded a HP driver installation package - extracted the exe file using 7zip, allowing me to access the necessary individual files, and then manually installed in a manner similar to what you described earlier. I did download the driver you mentioned above (e710n) and it does extract using 7zip.

I'm wary of that...have done that once with a prior OfficeJet...and it crashed the whole print spool service of the terminal server. Had to manually clean out all the drivers in the spooler and load it up again. Fully engrained in me to use proper drivers certified and supported for use in a server OS.
 
Have you tried looking for the HP Universal Print Driver? There are 32-bit & 64-bit versions available and I believe it works with pretty much any HP printer - might be worth a shot.
 
Have you tried looking for the HP Universal Print Driver? There are 32-bit & 64-bit versions available and I believe it works with pretty much any HP printer - might be worth a shot.

I haven't tried that on an officejet/deskjet printer....have used it on laserjet many times. Perhaps I'll give it a shot. I'd probably have to install a local printer object on her XP workstation at her house...using that driver...and then match on the server end.
 
Did you ever find a fix to this? I have a client going through the same thing, ink jet Canon all in one printer constantly having to change the port in order to get it to print.
 
Back
Top