PC Review


Reply
Thread Tools Rate Thread

Install local printer for XP client on W2000 TS

 
 
Matthew Harris [MVP]
Guest
Posts: n/a
 
      12th Feb 2004
What type of printer is this? Have you tied using an
alternate driver on the terminal server, like an HP
LaserJet 4 driver?

As a side note...installing drivers from third parties
onto your terminal server can cause things to get a little
dicey. If a driver crashes, it can cause your entire
server to become unstable and/or crash. Be very careful
when loading non-certified drivers onto your terminal
server. Test them thoroughly.

-M

>-----Original Message-----
>I recently upgraded a client computer from W2000 to

WinXP. Our Terminal Server is W2000 Server. I am unable
to print to the local printer connected to the client
computer when logon to Terminal Server. I have the
drivers installed on the TS and I can see the printer, but
I am unable to print. I send the print job, it shows up
in the print que, but is just hangs there. Eventually, I
receive a message saying "Unable to connect to the
printer". I did not have any problems printing to the
printer when the client computer operating system was
W2000. Any ideas?
>.
>

 
Reply With Quote
 
 
 
 
=?Utf-8?B?bmNoZWVr?=
Guest
Posts: n/a
 
      13th Feb 2004
The printer is an HP LaserJet 1200. When I logon through Terminal Server, I can see the printer. I cannot make the printer my default printer. I can send a document to the printer. It appears in the 'print que'. I then receive an error message "Cannot connect to printer. Cancel or Retry". If I retry, I get the same message. The driver installed on the Terminal Server is for W2000. Do we need to install the driver for Windows XP, since the client computer is running XP

Thank

----- Matthew Harris [MVP] wrote: ----

What type of printer is this? Have you tied using an
alternate driver on the terminal server, like an HP
LaserJet 4 driver

As a side note...installing drivers from third parties
onto your terminal server can cause things to get a little
dicey. If a driver crashes, it can cause your entire
server to become unstable and/or crash. Be very careful
when loading non-certified drivers onto your terminal
server. Test them thoroughly

-

>-----Original Message----
>I recently upgraded a client computer from W2000 to

WinXP. Our Terminal Server is W2000 Server. I am unable
to print to the local printer connected to the client
computer when logon to Terminal Server. I have the
drivers installed on the TS and I can see the printer, but
I am unable to print. I send the print job, it shows up
in the print que, but is just hangs there. Eventually, I
receive a message saying "Unable to connect to the
printer". I did not have any problems printing to the
printer when the client computer operating system was
W2000. Any ideas
>
>

 
Reply With Quote
 
Matthew Harris [MVP]
Guest
Posts: n/a
 
      13th Feb 2004
It sounds like the drive might be causing a problem. Have
you tried using a HP LaserJet 4 driver with it?

What happens if you try to make the printer your default
printer?

check out this article on how to make the system use a
different driver for your printer:

http://support.microsoft.com/default.aspx?scid=kb;en-
us;275495&Product=win2000

-M

>-----Original Message-----
>The printer is an HP LaserJet 1200. When I logon through

Terminal Server, I can see the printer. I cannot make the
printer my default printer. I can send a document to the
printer. It appears in the 'print que'. I then receive
an error message "Cannot connect to printer. Cancel or
Retry". If I retry, I get the same message. The driver
installed on the Terminal Server is for W2000. Do we need
to install the driver for Windows XP, since the client
computer is running XP?
>
>Thanks
>
> ----- Matthew Harris [MVP] wrote: -----
>
> What type of printer is this? Have you tied using

an
> alternate driver on the terminal server, like an HP
> LaserJet 4 driver?
>
> As a side note...installing drivers from third

parties
> onto your terminal server can cause things to get a

little
> dicey. If a driver crashes, it can cause your

entire
> server to become unstable and/or crash. Be very

careful
> when loading non-certified drivers onto your

terminal
> server. Test them thoroughly.
>
> -M
>
> >-----Original Message-----
> >I recently upgraded a client computer from W2000 to

> WinXP. Our Terminal Server is W2000 Server. I am

unable
> to print to the local printer connected to the

client
> computer when logon to Terminal Server. I have the
> drivers installed on the TS and I can see the

printer, but
> I am unable to print. I send the print job, it

shows up
> in the print que, but is just hangs there.

Eventually, I
> receive a message saying "Unable to connect to the
> printer". I did not have any problems printing to

the
> printer when the client computer operating system

was
> W2000. Any ideas?
> >.
> >

>.
>

 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
W2000 Pro - Will not install new Canon USB Printer Jim Microsoft Windows 2000 New Users 2 12th Jul 2006 04:30 AM
Local printer on XP Pro client vs 2K Client? Gordon Fecyk Windows XP Work Remotely 0 18th Dec 2004 05:34 AM
Local printer works in Win2K RDP client, not on XP Pro RDP client Gordon Fecyk Windows XP Work Remotely 0 17th Dec 2004 12:47 AM
Cannot install printer on W2000 after SP4 apply BR Microsoft Windows 2000 Printing 1 2nd Dec 2003 05:37 PM
ISA Firewall client not install on W2000 Pro lgario@new-age-data.com Microsoft Windows 2000 0 4th Nov 2003 03:47 PM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 02:23 PM.