Jump to content

Printer on PC not available from TS


Recommended Posts

Guest David Brown
Posted

We are using Terminal Services on Windows Server 2003. I have a user with

and HP 3015 AIO printer on their laptop. When connected to the terminal

server she can not user the printer from terminal service because it is not

available. Other users have access to their local printer from Terminal

Services. This user needs to print to their local printer. Any help would

be appreciated.

Thanks,

-David

  • Replies 3
  • Created
  • Last Reply
Guest Callileah
Posted

RE: Printer on PC not available from TS

 

June 18, 2008

 

Dear David,

 

If the User is accessing the TS Server with Windows Remote Desktop

Application, then they need to "Edit" the Remote Desktop configuration to

allow access to the local (their laptop) printer. Your User's probelm is not

TS related, it's the Remote Desktop app config that is the issue.

 

How: I'll assume the User has a Remote Desktop icon on their laptop's desktop.

1. Right click the RD icon, and select "Edit".

2. Click on the "local resources" tab.

3. Put a checkmark in the check box for "Printers"

4. Go to the "General" tab and click the "Save As" button. Follow

instructions...

 

If the User doesn't have a pre-configured icon already, create a new one and

apply the steps above when doing so.

 

This should solve your problem.

--

Thanks,

Cal

Help Desk Admin

NY-NJ Trail Conference

"Connecting People with Nature since 1920"

 

 

"David Brown" wrote:

> We are using Terminal Services on Windows Server 2003. I have a user with

> and HP 3015 AIO printer on their laptop. When connected to the terminal

> server she can not user the printer from terminal service because it is not

> available. Other users have access to their local printer from Terminal

> Services. This user needs to print to their local printer. Any help would

> be appreciated.

> Thanks,

> -David

>

>

>

Guest Vera Noest [MVP]
Posted

RE: Printer on PC not available from TS

 

I doubt that enabling printer redirection will solve the problem,

since the OP obviously knows about printer redirection (it's

working for other users)

 

David, by all means check the printer redirection setting, but the

most likely reason is that the server doesn't have a driver for

this printer model. You can verify this by checking the EventLog on

the server at the time that the user connects to the TS. You should

see Events 1111, 1105, and 1106.

 

Now please don't rush and download and install the printer driver

on the Terminal Server! You have a bigger problem than just a

missing driver. All-In-One printers are generally *not* TS-

compatible, and their drivers are known to crash the printer

spooler or the whole server.

HP publishes detailed information about which printer drivers are

TS compatible and which not. Unfortunately, you don't give the full

model of the printer, so I'm not able to verify it's compatibility

state, but chances are that it isn't compatible.

You can check for yourself here:

 

HP Printers Supported in Citrix MetaFrame Presentation and Terminal

Server Environments

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?

objectID=c00213455

 

What you can do is map the printer to a native driver, by following

the instructions in this article:

 

239088 - Windows 2000 or Windows Server 2003 Terminal Services

server logs events 1111, 1105, and 1106

http://support.microsoft.com/?kbid=239088

 

or define a fallback printer on the server.

 

But be aware that the most you can get out of this printer is plain

text, if it will work at all. AIO printers are just no good in a TS

environment.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

=?Utf-8?B?Q2FsbGlsZWFo?= <Callileah@discussions.microsoft.com>

wrote on 18 jun 2008 in

microsoft.public.windows.terminal_services:

> June 18, 2008

>

> Dear David,

>

> If the User is accessing the TS Server with Windows Remote

> Desktop

> Application, then they need to "Edit" the Remote Desktop

> configuration to allow access to the local (their laptop)

> printer. Your User's probelm is not TS related, it's the Remote

> Desktop app config that is the issue.

>

> How: I'll assume the User has a Remote Desktop icon on their

> laptop's desktop. 1. Right click the RD icon, and select "Edit".

> 2. Click on the "local resources" tab.

> 3. Put a checkmark in the check box for "Printers"

> 4. Go to the "General" tab and click the "Save As" button.

> Follow instructions...

>

> If the User doesn't have a pre-configured icon already, create a

> new one and apply the steps above when doing so.

>

> This should solve your problem.

Guest David Brown
Posted

Re: Printer on PC not available from TS

 

Great information. Thanks. I did load the non AIO driver for the HP

Laserjet 3015 but as you have said it did not fix the problem. Thanks again

for the great information everyone.

-David

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message

news:Xns9AC1AF8326C25veranoesthemutforsse@207.46.248.16...

>I doubt that enabling printer redirection will solve the problem,

> since the OP obviously knows about printer redirection (it's

> working for other users)

>

> David, by all means check the printer redirection setting, but the

> most likely reason is that the server doesn't have a driver for

> this printer model. You can verify this by checking the EventLog on

> the server at the time that the user connects to the TS. You should

> see Events 1111, 1105, and 1106.

>

> Now please don't rush and download and install the printer driver

> on the Terminal Server! You have a bigger problem than just a

> missing driver. All-In-One printers are generally *not* TS-

> compatible, and their drivers are known to crash the printer

> spooler or the whole server.

> HP publishes detailed information about which printer drivers are

> TS compatible and which not. Unfortunately, you don't give the full

> model of the printer, so I'm not able to verify it's compatibility

> state, but chances are that it isn't compatible.

> You can check for yourself here:

>

> HP Printers Supported in Citrix MetaFrame Presentation and Terminal

> Server Environments

> http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?

> objectID=c00213455

>

> What you can do is map the printer to a native driver, by following

> the instructions in this article:

>

> 239088 - Windows 2000 or Windows Server 2003 Terminal Services

> server logs events 1111, 1105, and 1106

> http://support.microsoft.com/?kbid=239088

>

> or define a fallback printer on the server.

>

> But be aware that the most you can get out of this printer is plain

> text, if it will work at all. AIO printers are just no good in a TS

> environment.

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> =?Utf-8?B?Q2FsbGlsZWFo?= <Callileah@discussions.microsoft.com>

> wrote on 18 jun 2008 in

> microsoft.public.windows.terminal_services:

>

>> June 18, 2008

>>

>> Dear David,

>>

>> If the User is accessing the TS Server with Windows Remote

>> Desktop

>> Application, then they need to "Edit" the Remote Desktop

>> configuration to allow access to the local (their laptop)

>> printer. Your User's probelm is not TS related, it's the Remote

>> Desktop app config that is the issue.

>>

>> How: I'll assume the User has a Remote Desktop icon on their

>> laptop's desktop. 1. Right click the RD icon, and select "Edit".

>> 2. Click on the "local resources" tab.

>> 3. Put a checkmark in the check box for "Printers"

>> 4. Go to the "General" tab and click the "Save As" button.

>> Follow instructions...

>>

>> If the User doesn't have a pre-configured icon already, create a

>> new one and apply the steps above when doing so.

>>

>> This should solve your problem.


×
×
  • Create New...