Printer Issues

[Guest Freaky]

Hey there,

 

I've got a weird problem with a customer. This customer always had some

printers mapped through terminal services, these always worked fine.

 

A while ago they got a new printer, a HP LaserJet 2840. The strange

thing is the old printers are still there (they're still installed on

the computer and the terminal server still maps them thus), however on

the new printer there is nothing. No log entries, no printer, nothing.

The PCL6 driver (same version as client) is installed on the terminal.

Normally I would suspect a message that it can not map the printer due

to a missing driver, but there is no such message.

 

To troubleshoot I threw away all printers on the clients computer,

except the 2840. Now when I connect the client has no printers, still no

messages in the log about missing printer drivers.

 

Any ideas on how to troubleshoot this?

 

Kind regards

[Guest Freaky]

Re: Printer Issues

 

It's a network printer (TCP/IP network port thus, this isn't a problem

with the other printers).

 

Doubt the generic driver will do much as it doesn't appear the client

even alert the server of the printer (atleast so it appears as there are

no log entries about the printer whatsoever). Also last time we used the

generic driver it requested a lot of info for every print (like IP

address, printer model, etc, this is not acceptable unfortunately).

 

Thanks for the Re'

 

moncho wrote:

> Freaky wrote:

>> Hey there,

>>

>> I've got a weird problem with a customer. This customer always had some

>> printers mapped through terminal services, these always worked fine.

>>

>> A while ago they got a new printer, a HP LaserJet 2840. The strange

>> thing is the old printers are still there (they're still installed on

>> the computer and the terminal server still maps them thus), however on

>> the new printer there is nothing. No log entries, no printer, nothing.

>> The PCL6 driver (same version as client) is installed on the terminal.

>> Normally I would suspect a message that it can not map the printer due

>> to a missing driver, but there is no such message.

>>

>> To troubleshoot I threw away all printers on the clients computer,

>> except the 2840. Now when I connect the client has no printers, still no

>> messages in the log about missing printer drivers.

>>

>> Any ideas on how to troubleshoot this?

>

> How is this printer connected? TCP/USB/Parallel?

>

> Are you using the newest version of RDP?

>

> If yes, then try using a generic HP LaserJet PCL driver and see if that

> changes anything.

>

> moncho

[Guest moncho]

Re: Printer Issues

 

Freaky wrote:

> Hey there,

>

> I've got a weird problem with a customer. This customer always had some

> printers mapped through terminal services, these always worked fine.

>

> A while ago they got a new printer, a HP LaserJet 2840. The strange

> thing is the old printers are still there (they're still installed on

> the computer and the terminal server still maps them thus), however on

> the new printer there is nothing. No log entries, no printer, nothing.

> The PCL6 driver (same version as client) is installed on the terminal.

> Normally I would suspect a message that it can not map the printer due

> to a missing driver, but there is no such message.

>

> To troubleshoot I threw away all printers on the clients computer,

> except the 2840. Now when I connect the client has no printers, still no

> messages in the log about missing printer drivers.

>

> Any ideas on how to troubleshoot this?

 

How is this printer connected? TCP/USB/Parallel?

 

Are you using the newest version of RDP?

 

If yes, then try using a generic HP LaserJet PCL driver and see if that

changes anything.

 

moncho

[Guest Jim]

Re: Printer Issues

 

USB or HP port? This worked here:

http://support.microsoft.com/kb/302361

 

Freaky wrote:

> Hey there,

>

> I've got a weird problem with a customer. This customer always had some

> printers mapped through terminal services, these always worked fine.

>

> A while ago they got a new printer, a HP LaserJet 2840. The strange

> thing is the old printers are still there (they're still installed on

> the computer and the terminal server still maps them thus), however on

> the new printer there is nothing. No log entries, no printer, nothing.

> The PCL6 driver (same version as client) is installed on the terminal.

> Normally I would suspect a message that it can not map the printer due

> to a missing driver, but there is no such message.

>

> To troubleshoot I threw away all printers on the clients computer,

> except the 2840. Now when I connect the client has no printers, still no

> messages in the log about missing printer drivers.

>

> Any ideas on how to troubleshoot this?

>

> Kind regards

[Guest TP]

Re: Printer Issues

 

Hi,

 

Please use the version of the Remote Desktop Client

that came with 2003 server. The install file for it is

located on the server's hard drive here:

 

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

 

This version will automatically attempt to map local

printers attached to standard tcp/ip ports, usb, etc.

 

Thanks.

 

-TP

 

Freaky wrote:

> Hey there,

>

> I've got a weird problem with a customer. This customer always had

> some printers mapped through terminal services, these always worked

> fine.

>

> A while ago they got a new printer, a HP LaserJet 2840. The strange

> thing is the old printers are still there (they're still installed on

> the computer and the terminal server still maps them thus), however on

> the new printer there is nothing. No log entries, no printer, nothing.

> The PCL6 driver (same version as client) is installed on the terminal.

> Normally I would suspect a message that it can not map the printer due

> to a missing driver, but there is no such message.

>

> To troubleshoot I threw away all printers on the clients computer,

> except the 2840. Now when I connect the client has no printers, still

> no messages in the log about missing printer drivers.

>

> Any ideas on how to troubleshoot this?

>

> Kind regards

[Guest Freaky]

Re: Printer Issues

 

Thanks a bunch Jim, it worked :)

 

This had me quite surprised tho' as we have a whole bunch of customers

with TCP/IP printer that work just fine. TP below here however mentions

the TSC client that came with 2003 server. Not sure if that's the 6.0

(IIRC, the one that's optional on windows update now), but that could be

it, they're using the one that came with WinXP.

 

Honestly I find the new version pretty annoying as it has an extra popup

asking for the password. It will also ask if it's OK to map drives n

such. Personally I'm a very simple guy, if I put the checkmark there,

then I want it, I do not want another dialog asking me if I'm sure.

Hence why we usually don't update it.

 

Anyways thanks a bunch again :D

 

Jim wrote:

> USB or HP port? This worked here:

> http://support.microsoft.com/kb/302361

>

> Freaky wrote:

>> Hey there,

>>

>> I've got a weird problem with a customer. This customer always had some

>> printers mapped through terminal services, these always worked fine.

>>

>> A while ago they got a new printer, a HP LaserJet 2840. The strange

>> thing is the old printers are still there (they're still installed on

>> the computer and the terminal server still maps them thus), however on

>> the new printer there is nothing. No log entries, no printer, nothing.

>> The PCL6 driver (same version as client) is installed on the terminal.

>> Normally I would suspect a message that it can not map the printer due

>> to a missing driver, but there is no such message.

>>

>> To troubleshoot I threw away all printers on the clients computer,

>> except the 2840. Now when I connect the client has no printers, still no

>> messages in the log about missing printer drivers.

>>

>> Any ideas on how to troubleshoot this?

>>

>> Kind regards

[Guest TP]

Re: Printer Issues

 

It is *not* version 6, that is why I recommend it.

 

The knowledgebase solution works fine, however, it must

be done for every user that will use the machine. For

example, someone else will use this machine in the future

and then the solution to this problem will need to be

remembered (or if not, researched again) and applied

again. Ditto if the current user's profile needs to be

recreated for some reason.

 

If you update the client to the version I mentioned you only

need to do it once and it will work for all user accounts

in the future. No manual registry edits needed and the

install can be pushed out via group policy if desired. The

install typically takes less than 15 seconds to complete on

modern hardware and less than a minute on older machines.

 

-TP

 

Freaky wrote:

> Thanks a bunch Jim, it worked :)

>

> This had me quite surprised tho' as we have a whole bunch of customers

> with TCP/IP printer that work just fine. TP below here however

> mentions the TSC client that came with 2003 server. Not sure if

> that's the 6.0 (IIRC, the one that's optional on windows update now),

> but that could be it, they're using the one that came with WinXP.

>

> Honestly I find the new version pretty annoying as it has an extra

> popup asking for the password. It will also ask if it's OK to map

> drives n such. Personally I'm a very simple guy, if I put the

> checkmark there, then I want it, I do not want another dialog asking

> me if I'm sure. Hence why we usually don't update it.

>

> Anyways thanks a bunch again :D