Local Printing - Still having problems ....

[Guest John F Kappler]

This is using Terminal Services on a Windows Server 2003 system with

latest updates installed (but no specific ones for this problem - if

there are any)

 

The problem manifests itself when the user connects to terminal

services and their printers do not become visible (get installed) on

the list of available printers.

 

I've checked that terminal services Client Settings allows Windows

Printer Mappings.

 

I've also checked that the printers are connected via COM, LPT or USB

ports and hey are.

 

I thought we might have the driver name problem, but there are no

(emphasise no - zero)) error 1111,1105 or 1106 messages in the system

event log on the server.

 

I've tried to check individual printer drivers support for terminal

services but this has proved extermely difficult (the link often given

here to the relevant page on the HP website doesn't work for me!).

 

At present we have 5 remote users, all with different printers, none

of whom can see their printer in the session.

 

Any ideas what do I do next?

 

TIA,

 

JohnK

[Guest Vera Noest [MVP]]

Re: Local Printing - Still having problems ....

 

If there are no printer events in the EventLog AND you have enabled

informational messages to be recorded in the EventLog on the server

(under Printers and Faxes - File menu - Server settings -

Advanced), then it means that redirection of local printers isn't

even attempted.

 

If redirection is attempted but fails because of a driver name

mismatch, it will generate an error in the EventLog, and those are

nearly always enabled (but check that as well).

 

Which version of the rdp client are you using? I'd recommend using

the version that comes with your 2003 server, you can install it on

the clients from C:\WINDOWS\system32\clients\tsclient\win32

\msrdpcli.msi

 

The link to the HP website works correctly, but it will wrap around

in this post, so you'll have to do some cutting and pasting in IE.

 

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

objectID=c00213455

 

or try this (direct download link):

 

http://h71028.www7.hp.com/ERC/downloads/4AA0-8465ENW.pdf

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

John F Kappler <john@pceffect.co.uk> wrote on 06 nov 2007 in

microsoft.public.windows.terminal_services:

> This is using Terminal Services on a Windows Server 2003 system

> with latest updates installed (but no specific ones for this

> problem - if there are any)

>

> The problem manifests itself when the user connects to terminal

> services and their printers do not become visible (get

> installed) on the list of available printers.

>

> I've checked that terminal services Client Settings allows

> Windows Printer Mappings.

>

> I've also checked that the printers are connected via COM, LPT

> or USB ports and hey are.

>

> I thought we might have the driver name problem, but there are

> no (emphasise no - zero)) error 1111,1105 or 1106 messages in

> the system event log on the server.

>

> I've tried to check individual printer drivers support for

> terminal services but this has proved extermely difficult (the

> link often given here to the relevant page on the HP website

> doesn't work for me!).

>

> At present we have 5 remote users, all with different printers,

> none of whom can see their printer in the session.

>

> Any ideas what do I do next?

>

> TIA,

>

> JohnK

[Guest John F Kappler]

Re: Local Printing - Still having problems ....

 

I'l lcheck the RDP drivers on the individual workstations as soon as I

can, but this has made me wonder about the method of connection...

 

The Terminal Server is on a domain which is controlled by an SBServer.

 

Remote users connect in using RWW and then electing to connect ot the

Terminal Server. At that point a window opens which looks to me like a

normal RDP window but am I wrong in thinking this?

 

BTW, the event logging is turned on.

 

JohnK

 

On Tue, 06 Nov 2007 12:50:06 -0800, "Vera Noest [MVP]"

<vera.noest@remove-this.hem.utfors.se> wrote:

>If there are no printer events in the EventLog AND you have enabled

>informational messages to be recorded in the EventLog on the server

>(under Printers and Faxes - File menu - Server settings -

>Advanced), then it means that redirection of local printers isn't

>even attempted.

>

>If redirection is attempted but fails because of a driver name

>mismatch, it will generate an error in the EventLog, and those are

>nearly always enabled (but check that as well).

>

>Which version of the rdp client are you using? I'd recommend using

>the version that comes with your 2003 server, you can install it on

>the clients from C:\WINDOWS\system32\clients\tsclient\win32

>\msrdpcli.msi

>

>The link to the HP website works correctly, but it will wrap around

>in this post, so you'll have to do some cutting and pasting in IE.

>

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

>objectID=c00213455

>

>or try this (direct download link):

>

>http://h71028.www7.hp.com/ERC/downloads/4AA0-8465ENW.pdf

>_________________________________________________________

>Vera Noest

>MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>

>John F Kappler <john@pceffect.co.uk> wrote on 06 nov 2007 in

>microsoft.public.windows.terminal_services:

>

>> This is using Terminal Services on a Windows Server 2003 system

>> with latest updates installed (but no specific ones for this

>> problem - if there are any)

>>

>> The problem manifests itself when the user connects to terminal

>> services and their printers do not become visible (get

>> installed) on the list of available printers.

>>

>> I've checked that terminal services Client Settings allows

>> Windows Printer Mappings.

>>

>> I've also checked that the printers are connected via COM, LPT

>> or USB ports and hey are.

>>

>> I thought we might have the driver name problem, but there are

>> no (emphasise no - zero)) error 1111,1105 or 1106 messages in

>> the system event log on the server.

>>

>> I've tried to check individual printer drivers support for

>> terminal services but this has proved extermely difficult (the

>> link often given here to the relevant page on the HP website

>> doesn't work for me!).

>>

>> At present we have 5 remote users, all with different printers,

>> none of whom can see their printer in the session.

>>

>> Any ideas what do I do next?

>>

>> TIA,

>>

>> JohnK

[Guest Vera Noest [MVP]]

Re: Local Printing - Still having problems ....

 

I've no idea how exactly RWW works. Maybe you'd better post to the

SBS newsgroup:

microsoft.public.windows.server.sbs

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

John F Kappler <john@pceffect.co.uk> wrote on 07 nov 2007 in

microsoft.public.windows.terminal_services:

> I'l lcheck the RDP drivers on the individual workstations as

> soon as I can, but this has made me wonder about the method of

> connection...

>

> The Terminal Server is on a domain which is controlled by an

> SBServer.

>

> Remote users connect in using RWW and then electing to connect

> ot the Terminal Server. At that point a window opens which looks

> to me like a normal RDP window but am I wrong in thinking this?

>

> BTW, the event logging is turned on.

>

> JohnK

>

> On Tue, 06 Nov 2007 12:50:06 -0800, "Vera Noest [MVP]"

> <vera.noest@remove-this.hem.utfors.se> wrote:

>

>>If there are no printer events in the EventLog AND you have

>>enabled informational messages to be recorded in the EventLog on

>>the server (under Printers and Faxes - File menu - Server

>>settings - Advanced), then it means that redirection of local

>>printers isn't even attempted.

>>

>>If redirection is attempted but fails because of a driver name

>>mismatch, it will generate an error in the EventLog, and those

>>are nearly always enabled (but check that as well).

>>

>>Which version of the rdp client are you using? I'd recommend

>>using the version that comes with your 2003 server, you can

>>install it on the clients from

>>C:\WINDOWS\system32\clients\tsclient\win32 \msrdpcli.msi

>>

>>The link to the HP website works correctly, but it will wrap

>>around in this post, so you'll have to do some cutting and

>>pasting in IE.

>>

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

>>objectID=c00213455

>>

>>or try this (direct download link):

>>

>>http://h71028.www7.hp.com/ERC/downloads/4AA0-8465ENW.pdf

>>_________________________________________________________

>>Vera Noest

>>MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>>

>>John F Kappler <john@pceffect.co.uk> wrote on 06 nov 2007 in

>>microsoft.public.windows.terminal_services:

>>

>>> This is using Terminal Services on a Windows Server 2003

>>> system with latest updates installed (but no specific ones for

>>> this problem - if there are any)

>>>

>>> The problem manifests itself when the user connects to

>>> terminal services and their printers do not become visible

>>> (get installed) on the list of available printers.

>>>

>>> I've checked that terminal services Client Settings allows

>>> Windows Printer Mappings.

>>>

>>> I've also checked that the printers are connected via COM, LPT

>>> or USB ports and hey are.

>>>

>>> I thought we might have the driver name problem, but there are

>>> no (emphasise no - zero)) error 1111,1105 or 1106 messages in

>>> the system event log on the server.

>>>

>>> I've tried to check individual printer drivers support for

>>> terminal services but this has proved extermely difficult (the

>>> link often given here to the relevant page on the HP website

>>> doesn't work for me!).

>>>

>>> At present we have 5 remote users, all with different

>>> printers, none of whom can see their printer in the session.

>>>

>>> Any ideas what do I do next?

>>>

>>> TIA,

>>>

>>> JohnK

[Guest John F Kappler]

Re: Local Printing - Still having problems ....

 

Thinking about this, as all the clients are XP Pro (with auto-updates

turned on) and the SBS is 2003 R2, then an out of date version of RDP

shouldn't be the problem... (I wait to be corrected!).

 

Meanwhile, where else might the problem be?

 

TIA,

 

JohnK

 

 

On Wed, 07 Nov 2007 02:35:51 -0800, "Vera Noest [MVP]"

<vera.noest@remove-this.hem.utfors.se> wrote:

>I've no idea how exactly RWW works. Maybe you'd better post to the

>SBS newsgroup:

>microsoft.public.windows.server.sbs

>_________________________________________________________

>Vera Noest

>MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>

>John F Kappler <john@pceffect.co.uk> wrote on 07 nov 2007 in

>microsoft.public.windows.terminal_services:

>

>> I'l lcheck the RDP drivers on the individual workstations as

>> soon as I can, but this has made me wonder about the method of

>> connection...

>>

>> The Terminal Server is on a domain which is controlled by an

>> SBServer.

>>

>> Remote users connect in using RWW and then electing to connect

>> ot the Terminal Server. At that point a window opens which looks

>> to me like a normal RDP window but am I wrong in thinking this?

>>

>> BTW, the event logging is turned on.

>>

>> JohnK

>>

>> On Tue, 06 Nov 2007 12:50:06 -0800, "Vera Noest [MVP]"

>> <vera.noest@remove-this.hem.utfors.se> wrote:

>>

>>>If there are no printer events in the EventLog AND you have

>>>enabled informational messages to be recorded in the EventLog on

>>>the server (under Printers and Faxes - File menu - Server

>>>settings - Advanced), then it means that redirection of local

>>>printers isn't even attempted.

>>>

>>>If redirection is attempted but fails because of a driver name

>>>mismatch, it will generate an error in the EventLog, and those

>>>are nearly always enabled (but check that as well).

>>>

>>>Which version of the rdp client are you using? I'd recommend

>>>using the version that comes with your 2003 server, you can

>>>install it on the clients from

>>>C:\WINDOWS\system32\clients\tsclient\win32 \msrdpcli.msi

>>>

>>>The link to the HP website works correctly, but it will wrap

>>>around in this post, so you'll have to do some cutting and

>>>pasting in IE.

>>>

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

>>>objectID=c00213455

>>>

>>>or try this (direct download link):

>>>

>>>http://h71028.www7.hp.com/ERC/downloads/4AA0-8465ENW.pdf

>>>_________________________________________________________

>>>Vera Noest

>>>MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>>>

>>>John F Kappler <john@pceffect.co.uk> wrote on 06 nov 2007 in

>>>microsoft.public.windows.terminal_services:

>>>

>>>> This is using Terminal Services on a Windows Server 2003

>>>> system with latest updates installed (but no specific ones for

>>>> this problem - if there are any)

>>>>

>>>> The problem manifests itself when the user connects to

>>>> terminal services and their printers do not become visible

>>>> (get installed) on the list of available printers.

>>>>

>>>> I've checked that terminal services Client Settings allows

>>>> Windows Printer Mappings.

>>>>

>>>> I've also checked that the printers are connected via COM, LPT

>>>> or USB ports and hey are.

>>>>

>>>> I thought we might have the driver name problem, but there are

>>>> no (emphasise no - zero)) error 1111,1105 or 1106 messages in

>>>> the system event log on the server.

>>>>

>>>> I've tried to check individual printer drivers support for

>>>> terminal services but this has proved extermely difficult (the

>>>> link often given here to the relevant page on the HP website

>>>> doesn't work for me!).

>>>>

>>>> At present we have 5 remote users, all with different

>>>> printers, none of whom can see their printer in the session.

>>>>

>>>> Any ideas what do I do next?

>>>>

>>>> TIA,

>>>>

>>>> JohnK

[Guest TP]

Re: Local Printing - Still having problems ....

 

Hi John,

 

Please check the basics:

 

In Terminal Services Configuration on your TS, RDP-Tcp

Properties, Client Settings tab

- Make sure "Use connection settings from user settings" is checked

- Make sure "Windows printer mapping" is *unchecked*

 

On your TS, make sure that the Print Spooler service is running.

 

In Remote Web Workplace, when connecting make sure that

"Enable documents on the remote compuer to be printed on a

local printer" is checked under Optional Settings.

 

In Active Directory User and Computers, Properties of each

user account, Environment tab, make sure that "Connect client

printers at logon" is checked.

 

In the applicable Group Policy Object, make sure that "Do not

allow client printer redirection" is set to Not Configured under:

 

Computer\Admin Templates\Windows Components\Terminal Services\Client/Server data redirection

 

Thanks.

 

-TP

 

John F Kappler wrote:

> Thinking about this, as all the clients are XP Pro (with auto-updates

> turned on) and the SBS is 2003 R2, then an out of date version of RDP

> shouldn't be the problem... (I wait to be corrected!).

>

> Meanwhile, where else might the problem be?

>

> TIA,

>

> JohnK