Printer Issues



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
.



Relevant Pages

  • Linking To FoxPro via ODBC problem
    ... my XP machine had a Visual FoxPro driver version 1.00.02.00 ... I downloaded FoxPro ODBC driver version 6.01.8269.01 from MSDN. ... Both my client and I now have the same version. ... I have a customer table with 167 records. ...
    (microsoft.public.data.odbc)
  • Re: Printer Issues
    ... I've got a weird problem with a customer. ... The PCL6 driver (same version as client) is installed on the terminal. ... To troubleshoot I threw away all printers on the clients computer, ...
    (microsoft.public.windows.terminal_services)
  • Re: Printer Issues
    ... This had me quite surprised tho' as we have a whole bunch of customers ... I've got a weird problem with a customer. ... The PCL6 driver (same version as client) is installed on the terminal. ...
    (microsoft.public.windows.terminal_services)
  • Re: Printer Issues
    ... I've got a weird problem with a customer. ... The PCL6 driver (same version as client) is installed on the terminal. ... To troubleshoot I threw away all printers on the clients computer, ...
    (microsoft.public.windows.terminal_services)
  • Re: 2008 SBS no longer boots
    ... Windows *does* write to a log, however, during a safe-mode boot what driver it is attempting to load. ... Any thermal issues and a lot of other hardware problems should show up ... other customer, even a 2 week old one, the problem immediately returned. ... There was a time when a server (even one that had been "burned ...
    (microsoft.public.windows.server.sbs)