Remote Client Printer not showing up when connected to TS

  • Thread starter Thread starter dean.carrefour
  • Start date Start date
D

dean.carrefour

Guest
We migrated to a new network and terminal server recently. I have one user
who worked fine before, but now when she connects, her local printer doesn't
show up. It says 'no printer detected, would you like to add one?' when she
tries to print. Of course it won't let her add one. The 'local' printer
option is grayed out. She is in a remote office. This is a brand new
Windows 2003 Server running nothing but Terminal Services. We have several
other users in other remote sites working just fine on this same server. I
can login as her from here, where the server is located, and print just fine
on my printer. I have also tried this from multiple machines here as well
as tried it connecting from another machine externally and remote desktoping
into the terminal server here, logging in as her. Printing on the local
printer worked fine. I have her printer driver installed on the terminal
server. I had her get on another machine in her office, remote desktop to
the terminal server, login as herself, same results.

This has really got me stumped. Any help will be greatly appreciated.


Dean
 
Re: Remote Client Printer not showing up when connected to TS

Have you checked the EventLog on the Terminal Server for any
printer-related warnings or errors at the time the user connects?

If there aren't any events, then the server doesn't even attempt to
redirect the local printer. If that is the case, check the
configuration of printer redirection in the RDP client and on the
Terminal Server, update the RDP client to at least the XP SP2
version or apply KB article 302361 to get support for redirection
of non-standard local port names, including tcp/ip ports.

If there is an event stating that redirection is attempted, but
fails, then it's probably a driver name mismatch. The event
description should give further details.

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"dean.carrefour" <dean.carrefour@newsgroup.nospam> wrote on 02 okt
2007 in microsoft.public.windows.terminal_services:

> We migrated to a new network and terminal server recently. I
> have one user who worked fine before, but now when she connects,
> her local printer doesn't show up. It says 'no printer
> detected, would you like to add one?' when she tries to print.
> Of course it won't let her add one. The 'local' printer option
> is grayed out. She is in a remote office. This is a brand new
> Windows 2003 Server running nothing but Terminal Services. We
> have several other users in other remote sites working just fine
> on this same server. I can login as her from here, where the
> server is located, and print just fine on my printer. I have
> also tried this from multiple machines here as well as tried it
> connecting from another machine externally and remote desktoping
> into the terminal server here, logging in as her. Printing on
> the local printer worked fine. I have her printer driver
> installed on the terminal server. I had her get on another
> machine in her office, remote desktop to the terminal server,
> login as herself, same results.
>
> This has really got me stumped. Any help will be greatly
> appreciated.
>
>
> Dean
 
Re: Remote Client Printer not showing up when connected to TS

There is an event in the event logs. It's an Event ID 1111 in the System
Log that states:

Event Type: Error
Event Source: TermServDevices
Event Category: None
Event ID: 1111
Date: 10/2/2007
Time: 1:47:49 PM
User: N/A
Computer: C4TS1
Description:
Driver hp LaserJet 1320 PCL 5e required for printer hp LaserJet 1320 PCL 5e
is unknown. Contact the administrator to install the driver before you log
in again.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 12 0d 00 00 ........

So is that a driver name mismatch? If so, how do I correct it? Thanks for
your help.

Dean



"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
news:Xns99BDE39883D1Fveranoesthemutforsse@207.46.248.16...
> Have you checked the EventLog on the Terminal Server for any
> printer-related warnings or errors at the time the user connects?
>
> If there aren't any events, then the server doesn't even attempt to
> redirect the local printer. If that is the case, check the
> configuration of printer redirection in the RDP client and on the
> Terminal Server, update the RDP client to at least the XP SP2
> version or apply KB article 302361 to get support for redirection
> of non-standard local port names, including tcp/ip ports.
>
> If there is an event stating that redirection is attempted, but
> fails, then it's probably a driver name mismatch. The event
> description should give further details.
>
> _________________________________________________________
> Vera Noest
 
Re: Remote Client Printer not showing up when connected to TS

Mmm, normally, Event 1111 shows an obvious name mismatch, like
"HP LaserJet 1320 Series" driver required for "HP LasetJet 1320",
which would not be the same name (it's case sensitive and must
match *exactly*). And then you would fix it by following this KB
article:
http://support.microsoft.com/?kbid=239088

But assuming that your text is copied and pasted from the EventLog,
I can't detect a name mismatch.
According to HP, the TS-compatible version of the driver for this
printer is version 60.41.41.00. Can you check if that's what you
installed on the server?

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"dean.carrefour" <dean.carrefour@newsgroup.nospam> wrote on 02 okt
2007 in microsoft.public.windows.terminal_services:

> There is an event in the event logs. It's an Event ID 1111 in
> the System Log that states:
>
> Event Type: Error
> Event Source: TermServDevices
> Event Category: None
> Event ID: 1111
> Date: 10/2/2007
> Time: 1:47:49 PM
> User: N/A
> Computer: C4TS1
> Description:
> Driver hp LaserJet 1320 PCL 5e required for printer hp LaserJet
> 1320 PCL 5e is unknown. Contact the administrator to install the
> driver before you log in again.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 00 00 00 00 12 0d 00 00 ........
>
> So is that a driver name mismatch? If so, how do I correct it?
> Thanks for your help.
>
> Dean
>
>
>
> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote
> in message
> news:Xns99BDE39883D1Fveranoesthemutforsse@207.46.248.16...
>> Have you checked the EventLog on the Terminal Server for any
>> printer-related warnings or errors at the time the user
>> connects?
>>
>> If there aren't any events, then the server doesn't even
>> attempt to redirect the local printer. If that is the case,
>> check the configuration of printer redirection in the RDP
>> client and on the Terminal Server, update the RDP client to at
>> least the XP SP2 version or apply KB article 302361 to get
>> support for redirection of non-standard local port names,
>> including tcp/ip ports.
>>
>> If there is an event stating that redirection is attempted, but
>> fails, then it's probably a driver name mismatch. The event
>> description should give further details.
 
Back
Top