Windows NT Clients Local Printer Not Printing

  • Thread starter Thread starter Golforfood
  • Start date Start date
G

Golforfood

I have a Windows 2003 Server R2 running and I have a client who uses Remote
Desktop to login. The client can't print to their local printer. I am using
Terminal Services. The just purchases a new printer which is an HP Laserjet
3055 All in One. I read a knowledgebase article on Microsoft's web site
(Article ID 302361) that says Printers that use ports that do not begin with
Com, Lpt, or USB are not redirected in a Remote Desktop or Terminal Services
Session. I have made the registry changes on the clients computer and also
changed the port from DOT$ to LPT. I still can't print. Is there anything
else I can do? I have spent a week on this and the client is trying to run a
business. Any help would be greatly appriciated.
 
Did you install the driver on the terminal server? I would test this
driver first to make sure it's terminal services compatible, otherwise,
your in for a lot of pain.

Jeff Pitsch
Microsoft MVP - Terminal Server
Citrix Technology Professional
Provision Networks VIP

Forums not enough?
Get support from the experts at your business
http://jeffpitschconsulting.com

Golforfood wrote:
> I have a Windows 2003 Server R2 running and I have a client who uses Remote
> Desktop to login. The client can't print to their local printer. I am using
> Terminal Services. The just purchases a new printer which is an HP Laserjet
> 3055 All in One. I read a knowledgebase article on Microsoft's web site
> (Article ID 302361) that says Printers that use ports that do not begin with
> Com, Lpt, or USB are not redirected in a Remote Desktop or Terminal Services
> Session. I have made the registry changes on the clients computer and also
> changed the port from DOT$ to LPT. I still can't print. Is there anything
> else I can do? I have spent a week on this and the client is trying to run a
> business. Any help would be greatly appriciated.
 
Golforfood wrote:
> I have a Windows 2003 Server R2 running and I have a client who uses Remote
> Desktop to login. The client can't print to their local printer. I am using
> Terminal Services. The just purchases a new printer which is an HP Laserjet
> 3055 All in One. I read a knowledgebase article on Microsoft's web site
> (Article ID 302361) that says Printers that use ports that do not begin with
> Com, Lpt, or USB are not redirected in a Remote Desktop or Terminal Services
> Session. I have made the registry changes on the clients computer and also
> changed the port from DOT$ to LPT. I still can't print. Is there anything
> else I can do? I have spent a week on this and the client is trying to run a
> business. Any help would be greatly appriciated.

Do you need all of the multi-function functions?

Do you have the latest RDP client installed?

How is the printer connected to the PC? USB? TCP/IP?

You can map the printer to a generic HP LaserJet Driver to do basic
printing because the printer has PCL. It should at least print.

moncho
 
Jeff:

I have installed the correct driver on the server, and yes I am in a lot of
pain. I have checked the hp website and have the correct driver for windows
2003. Is there a generic driver that I could load on the server? The one
that hp shows is laserjet 3055 PCL version 60.051.564.021.

"Jeff Pitsch" wrote:

> Did you install the driver on the terminal server? I would test this
> driver first to make sure it's terminal services compatible, otherwise,
> your in for a lot of pain.
>
> Jeff Pitsch
> Microsoft MVP - Terminal Server
> Citrix Technology Professional
> Provision Networks VIP
>
> Forums not enough?
> Get support from the experts at your business
> http://jeffpitschconsulting.com
>
> Golforfood wrote:
> > I have a Windows 2003 Server R2 running and I have a client who uses Remote
> > Desktop to login. The client can't print to their local printer. I am using
> > Terminal Services. The just purchases a new printer which is an HP Laserjet
> > 3055 All in One. I read a knowledgebase article on Microsoft's web site
> > (Article ID 302361) that says Printers that use ports that do not begin with
> > Com, Lpt, or USB are not redirected in a Remote Desktop or Terminal Services
> > Session. I have made the registry changes on the clients computer and also
> > changed the port from DOT$ to LPT. I still can't print. Is there anything
> > else I can do? I have spent a week on this and the client is trying to run a
> > business. Any help would be greatly appriciated.
>
 
"moncho" wrote:

> Golforfood wrote:
> > I have a Windows 2003 Server R2 running and I have a client who uses Remote
> > Desktop to login. The client can't print to their local printer. I am using
> > Terminal Services. The just purchases a new printer which is an HP Laserjet
> > 3055 All in One. I read a knowledgebase article on Microsoft's web site
> > (Article ID 302361) that says Printers that use ports that do not begin with
> > Com, Lpt, or USB are not redirected in a Remote Desktop or Terminal Services
> > Session. I have made the registry changes on the clients computer and also
> > changed the port from DOT$ to LPT. I still can't print. Is there anything
> > else I can do? I have spent a week on this and the client is trying to run a
> > business. Any help would be greatly appriciated.
>
> Do you need all of the multi-function functions? No, I don't, I just want to be able to print
>
> Do you have the latest RDP client installed? I believe so, but how do I check?
>
> How is the printer connected to the PC? USB? TCP/IP? It was connected through USB but then I read Article ID 302361 and it said to connect it to LPT and make a registry change per article on client computer as per instructions
>
> You can map the printer to a generic HP LaserJet Driver to do basic
> printing because the printer has PCL. It should at least print. How would I do this?
>
> moncho
>
>
 
Golforfood wrote:
>
> "moncho" wrote:
>
>> Golforfood wrote:
>>> I have a Windows 2003 Server R2 running and I have a client who uses Remote
>>> Desktop to login. The client can't print to their local printer. I am using
>>> Terminal Services. The just purchases a new printer which is an HP Laserjet
>>> 3055 All in One. I read a knowledgebase article on Microsoft's web site
>>> (Article ID 302361) that says Printers that use ports that do not begin with
>>> Com, Lpt, or USB are not redirected in a Remote Desktop or Terminal Services
>>> Session. I have made the registry changes on the clients computer and also
>>> changed the port from DOT$ to LPT. I still can't print. Is there anything
>>> else I can do? I have spent a week on this and the client is trying to run a
>>> business. Any help would be greatly appriciated.
>> Do you need all of the multi-function functions? No, I don't, I just want to be able to print
Excellent. Makes things easier.

>>
>> Do you have the latest RDP client installed? I believe so, but how do I check?
Windows Update has the newest RDP 6.0 client for download.

>>
>> How is the printer connected to the PC? USB? TCP/IP? It was connected through USB but then I read Article ID 302361 and it said to connect it to LPT and make a registry change per article on client computer as per instructions
>>
>> You can map the printer to a generic HP LaserJet Driver to do basic
>> printing because the printer has PCL. It should at least print. How would I do this?
The easiest way is to download the Terminal Server Printer Driver
Redirection Wizard at http://support.microsoft.com/kb/239088/en-us.

Then set it to a generic HP LaserJet PCL Printer Driver.

moncho
 
Back
Top