Can't print to client printer from W2003 R2 x64 TS

[Guest Mark L Cooper]

We just moved our main application from a W2000 server to a new W2003 R2 Std

x64 server.

 

We can run our main application on the new TS as usual from both XP and

Vista clients.

 

We've tested an XP client with an HP LaserJet 6P attached and a Vista

Business client with an HP LaserJet 6P.

 

We've tested with both normal 'user' accounts and administrator accounts.

 

The client printer does show up as the default printer in the Windows

Printer Select dialog box running on the TS.

 

Testing with Notepad and a 1 word document on the TS and trying to print to

the client printer gives the error "The handle is invalid." Printing to the

client printer from the main application gives no error....nothing happens.

 

All the above testing was done from both the XP and Vista client. The TS has

all updates available through Microsoft Update installed. The Vista and XP

clients have all updates available through Microsoft Update installed

including Remote Desktop 6.

 

Everything worked as expected when accessing the W2000 server from both XP

and Vista.

 

Any suggestions?

 

Thanks in advance,

Mark L Cooper

Information Technology

Perry County Ohio Bd of MR/DD

New Lexington, Ohio

[Guest Mark L Cooper]

Re: Can't print to client printer from W2003 R2 x64 TS

 

A little more info.

 

The TS is not a domain controller. It is set up as file server, a print

server with no printers attached, and a TS Licensing server. It is running

Sybase SQL Anywhere (ASA9).

 

All servers and workstations on the network are running Symantec Anti Virus

10.2.

 

 

The XP and Vista workstations are located in a different facitly than the

TS, connected over the Internet via a Gateway to Gateway VPN.

 

The topology of the network has not changed. We are in the process of moving

from the old W2000 Server to the new W2003 R2 x64 server....both located at

the same location.

 

Thanks,

Mark

 

"Mark L Cooper" <mlcooper54_no_spam@aol.com> wrote in message

news:EC1C9F5C-AD74-455D-8BED-BEAF0535972A@microsoft.com...

> We just moved our main application from a W2000 server to a new W2003 R2

> Std x64 server.

>

> We can run our main application on the new TS as usual from both XP and

> Vista clients.

>

> We've tested an XP client with an HP LaserJet 6P attached and a Vista

> Business client with an HP LaserJet 6P.

>

> We've tested with both normal 'user' accounts and administrator accounts.

>

> The client printer does show up as the default printer in the Windows

> Printer Select dialog box running on the TS.

>

> Testing with Notepad and a 1 word document on the TS and trying to print

> to the client printer gives the error "The handle is invalid." Printing to

> the client printer from the main application gives no error....nothing

> happens.

>

> All the above testing was done from both the XP and Vista client. The TS

> has all updates available through Microsoft Update installed. The Vista

> and XP clients have all updates available through Microsoft Update

> installed including Remote Desktop 6.

>

> Everything worked as expected when accessing the W2000 server from both XP

> and Vista.

>

> Any suggestions?

>

> Thanks in advance,

> Mark L Cooper

> Information Technology

> Perry County Ohio Bd of MR/DD

> New Lexington, Ohio

[Guest Vera Noest [MVP]]

Re: Can't print to client printer from W2003 R2 x64 TS

 

An x64 server can only use 64-bit printer drivers.

Where did the HP LaserJet driver come from? Are you using the

driver which came with the OS (from the installation CD), or did

you install a 3rd party printer driver?

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

"Mark L Cooper" <mlcooper54_no_spam@aol.com> wrote on 31 dec 2007

in microsoft.public.windows.terminal_services:

> A little more info.

>

> The TS is not a domain controller. It is set up as file server,

> a print server with no printers attached, and a TS Licensing

> server. It is running Sybase SQL Anywhere (ASA9).

>

> All servers and workstations on the network are running Symantec

> Anti Virus 10.2.

>

>

> The XP and Vista workstations are located in a different facitly

> than the TS, connected over the Internet via a Gateway to

> Gateway VPN.

>

> The topology of the network has not changed. We are in the

> process of moving from the old W2000 Server to the new W2003 R2

> x64 server....both located at the same location.

>

> Thanks,

> Mark

>

> "Mark L Cooper" <mlcooper54_no_spam@aol.com> wrote in message

> news:EC1C9F5C-AD74-455D-8BED-BEAF0535972A@microsoft.com...

>> We just moved our main application from a W2000 server to a new

>> W2003 R2 Std x64 server.

>>

>> We can run our main application on the new TS as usual from

>> both XP and Vista clients.

>>

>> We've tested an XP client with an HP LaserJet 6P attached and a

>> Vista Business client with an HP LaserJet 6P.

>>

>> We've tested with both normal 'user' accounts and administrator

>> accounts.

>>

>> The client printer does show up as the default printer in the

>> Windows Printer Select dialog box running on the TS.

>>

>> Testing with Notepad and a 1 word document on the TS and trying

>> to print to the client printer gives the error "The handle is

>> invalid." Printing to the client printer from the main

>> application gives no error....nothing happens.

>>

>> All the above testing was done from both the XP and Vista

>> client. The TS has all updates available through Microsoft

>> Update installed. The Vista and XP clients have all updates

>> available through Microsoft Update installed including Remote

>> Desktop 6.

>>

>> Everything worked as expected when accessing the W2000 server

>> from both XP and Vista.

>>

>> Any suggestions?

>>

>> Thanks in advance,

>> Mark L Cooper

>> Information Technology

>> Perry County Ohio Bd of MR/DD

>> New Lexington, Ohio

[Guest Mark L Cooper]

Re: Can't print to client printer from W2003 R2 x64 TS

 

Thanks for the response

 

All drivers came with each OS. No 3rd party. No updates from HP web site.

 

Server x64 driver that came with W2003 R2 x64

Client Vista driver that came with Vista Business (32 bit)

Client XP driver that came with XP (32 bit)

 

Thanks,

Mark

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message

news:Xns9A17DCCA7CA95veranoesthemutforsse@207.46.248.16...

> An x64 server can only use 64-bit printer drivers.

> Where did the HP LaserJet driver come from? Are you using the

> driver which came with the OS (from the installation CD), or did

> you install a 3rd party printer driver?

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>

> "Mark L Cooper" <mlcooper54_no_spam@aol.com> wrote on 31 dec 2007

> in microsoft.public.windows.terminal_services:

>

>> A little more info.

>>

>> The TS is not a domain controller. It is set up as file server,

>> a print server with no printers attached, and a TS Licensing

>> server. It is running Sybase SQL Anywhere (ASA9).

>>

>> All servers and workstations on the network are running Symantec

>> Anti Virus 10.2.

>>

>>

>> The XP and Vista workstations are located in a different facitly

>> than the TS, connected over the Internet via a Gateway to

>> Gateway VPN.

>>

>> The topology of the network has not changed. We are in the

>> process of moving from the old W2000 Server to the new W2003 R2

>> x64 server....both located at the same location.

>>

>> Thanks,

>> Mark

>>

>> "Mark L Cooper" <mlcooper54_no_spam@aol.com> wrote in message

>> news:EC1C9F5C-AD74-455D-8BED-BEAF0535972A@microsoft.com...

>>> We just moved our main application from a W2000 server to a new

>>> W2003 R2 Std x64 server.

>>>

>>> We can run our main application on the new TS as usual from

>>> both XP and Vista clients.

>>>

>>> We've tested an XP client with an HP LaserJet 6P attached and a

>>> Vista Business client with an HP LaserJet 6P.

>>>

>>> We've tested with both normal 'user' accounts and administrator

>>> accounts.

>>>

>>> The client printer does show up as the default printer in the

>>> Windows Printer Select dialog box running on the TS.

>>>

>>> Testing with Notepad and a 1 word document on the TS and trying

>>> to print to the client printer gives the error "The handle is

>>> invalid." Printing to the client printer from the main

>>> application gives no error....nothing happens.

>>>

>>> All the above testing was done from both the XP and Vista

>>> client. The TS has all updates available through Microsoft

>>> Update installed. The Vista and XP clients have all updates

>>> available through Microsoft Update installed including Remote

>>> Desktop 6.

>>>

>>> Everything worked as expected when accessing the W2000 server

>>> from both XP and Vista.

>>>

>>> Any suggestions?

>>>

>>> Thanks in advance,

>>> Mark L Cooper

>>> Information Technology

>>> Perry County Ohio Bd of MR/DD

>>> New Lexington, Ohio

[Guest Mark L Cooper]

Re: Can't print to client printer from W2003 R2 x64 TS

 

A little more info after perusing some earlier posts:

 

There is no physical parallel port on the TS

There is a physical parralel port on both the XP and Vista clients. The HP

6P's on both clients are set to port LPT1.

 

Thanks,

Mark

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message

news:Xns9A17DCCA7CA95veranoesthemutforsse@207.46.248.16...

> An x64 server can only use 64-bit printer drivers.

> Where did the HP LaserJet driver come from? Are you using the

> driver which came with the OS (from the installation CD), or did

> you install a 3rd party printer driver?

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>

> "Mark L Cooper" <mlcooper54_no_spam@aol.com> wrote on 31 dec 2007

> in microsoft.public.windows.terminal_services:

>

>> A little more info.

>>

>> The TS is not a domain controller. It is set up as file server,

>> a print server with no printers attached, and a TS Licensing

>> server. It is running Sybase SQL Anywhere (ASA9).

>>

>> All servers and workstations on the network are running Symantec

>> Anti Virus 10.2.

>>

>>

>> The XP and Vista workstations are located in a different facitly

>> than the TS, connected over the Internet via a Gateway to

>> Gateway VPN.

>>

>> The topology of the network has not changed. We are in the

>> process of moving from the old W2000 Server to the new W2003 R2

>> x64 server....both located at the same location.

>>

>> Thanks,

>> Mark

>>

>> "Mark L Cooper" <mlcooper54_no_spam@aol.com> wrote in message

>> news:EC1C9F5C-AD74-455D-8BED-BEAF0535972A@microsoft.com...

>>> We just moved our main application from a W2000 server to a new

>>> W2003 R2 Std x64 server.

>>>

>>> We can run our main application on the new TS as usual from

>>> both XP and Vista clients.

>>>

>>> We've tested an XP client with an HP LaserJet 6P attached and a

>>> Vista Business client with an HP LaserJet 6P.

>>>

>>> We've tested with both normal 'user' accounts and administrator

>>> accounts.

>>>

>>> The client printer does show up as the default printer in the

>>> Windows Printer Select dialog box running on the TS.

>>>

>>> Testing with Notepad and a 1 word document on the TS and trying

>>> to print to the client printer gives the error "The handle is

>>> invalid." Printing to the client printer from the main

>>> application gives no error....nothing happens.

>>>

>>> All the above testing was done from both the XP and Vista

>>> client. The TS has all updates available through Microsoft

>>> Update installed. The Vista and XP clients have all updates

>>> available through Microsoft Update installed including Remote

>>> Desktop 6.

>>>

>>> Everything worked as expected when accessing the W2000 server

>>> from both XP and Vista.

>>>

>>> Any suggestions?

>>>

>>> Thanks in advance,

>>> Mark L Cooper

>>> Information Technology

>>> Perry County Ohio Bd of MR/DD

>>> New Lexington, Ohio

[Guest Vera Noest [MVP]]

Re: Can't print to client printer from W2003 R2 x64 TS

 

I'm sorry, but then I have no idea what causes this.

 

Googling for "handle is invalid" gives quite some hits, maybe

there's something there that helps. HP also has a document about

this error:

 

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

objectID=bpj06941

 

but the bottomline seems to be: call Microsoft Support. And that's

probably what I would do, too.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

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

___ please respond in newsgroup, NOT by private email ___

 

"Mark L Cooper" <mlcooper54_no_spam@aol.com> wrote on 01 jan 2008

in microsoft.public.windows.terminal_services:

> Thanks for the response

>

> All drivers came with each OS. No 3rd party. No updates from HP

> web site.

>

> Server x64 driver that came with W2003 R2 x64

> Client Vista driver that came with Vista Business (32 bit)

> Client XP driver that came with XP (32 bit)

>

> Thanks,

> Mark

>

> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

> in message

> news:Xns9A17DCCA7CA95veranoesthemutforsse@207.46.248.16...

>> An x64 server can only use 64-bit printer drivers.

>> Where did the HP LaserJet driver come from? Are you using the

>> driver which came with the OS (from the installation CD), or

>> did you install a 3rd party printer driver?

>>

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>>

>> "Mark L Cooper" <mlcooper54_no_spam@aol.com> wrote on 31 dec

>> 2007 in microsoft.public.windows.terminal_services:

>>

>>> A little more info.

>>>

>>> The TS is not a domain controller. It is set up as file

>>> server, a print server with no printers attached, and a TS

>>> Licensing server. It is running Sybase SQL Anywhere (ASA9).

>>>

>>> All servers and workstations on the network are running

>>> Symantec Anti Virus 10.2.

>>>

>>>

>>> The XP and Vista workstations are located in a different

>>> facitly than the TS, connected over the Internet via a Gateway

>>> to Gateway VPN.

>>>

>>> The topology of the network has not changed. We are in the

>>> process of moving from the old W2000 Server to the new W2003

>>> R2 x64 server....both located at the same location.

>>>

>>> Thanks,

>>> Mark

>>>

>>> "Mark L Cooper" <mlcooper54_no_spam@aol.com> wrote in message

>>> news:EC1C9F5C-AD74-455D-8BED-BEAF0535972A@microsoft.com...

>>>> We just moved our main application from a W2000 server to a

>>>> new W2003 R2 Std x64 server.

>>>>

>>>> We can run our main application on the new TS as usual from

>>>> both XP and Vista clients.

>>>>

>>>> We've tested an XP client with an HP LaserJet 6P attached and

>>>> a Vista Business client with an HP LaserJet 6P.

>>>>

>>>> We've tested with both normal 'user' accounts and

>>>> administrator accounts.

>>>>

>>>> The client printer does show up as the default printer in the

>>>> Windows Printer Select dialog box running on the TS.

>>>>

>>>> Testing with Notepad and a 1 word document on the TS and

>>>> trying to print to the client printer gives the error "The

>>>> handle is invalid." Printing to the client printer from the

>>>> main application gives no error....nothing happens.

>>>>

>>>> All the above testing was done from both the XP and Vista

>>>> client. The TS has all updates available through Microsoft

>>>> Update installed. The Vista and XP clients have all updates

>>>> available through Microsoft Update installed including Remote

>>>> Desktop 6.

>>>>

>>>> Everything worked as expected when accessing the W2000 server

>>>> from both XP and Vista.

>>>>

>>>> Any suggestions?

>>>>

>>>> Thanks in advance,

>>>> Mark L Cooper

>>>> Information Technology

>>>> Perry County Ohio Bd of MR/DD

>>>> New Lexington, Ohio

[Guest Mark L Cooper]

Re: Can't print to client printer from W2003 R2 x64 TS

 

An update on the printer problem.

 

PrimoPDF = create a PDF printer driver

 

I installed PrimoPDF 32 bit driver on 2 Vista 32 Bit clients

I installed PrimoPDF 64 bit driver on W2003 R2 x64 server, then deleted the

PrimoPDF driver from the available printer list. Did not un-install

PrimoPDF.

 

Printing from TS resident main application to PrimoPDF (from workstation) in

session 1 brings up the PrimoPDF dialog box on the workstation (after

minimizing the TS session). I select any of my client printers and the

document prints fine. This works from Notepad running on the TS also.

 

The above suggests everything is set up properly on both the TS and the

client re: printer redirection. I'm beginning to suspect the HP LaseJet 6P

driver included with W2003 R2 x64 is the culprit.

 

Just to cover all bases, I turned off Windows firewall on the client

computers to make sure they weren't blocking any traffic meant for the

printer. Still no luck.

 

 

 

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message

news:Xns9A187544AFC83veranoesthemutforsse@207.46.248.16...

> I'm sorry, but then I have no idea what causes this.

>

> Googling for "handle is invalid" gives quite some hits, maybe

> there's something there that helps. HP also has a document about

> this error:

>

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

> objectID=bpj06941

 

The above document did not help any. Our Terminal Server doesn't have a

parallel port installed. If it did, I'd connect the HP 6P directly to the TS

to see if it would print.

 

 

 

Thanks,

Mark

 

 

>

> but the bottomline seems to be: call Microsoft Support. And that's

> probably what I would do, too.

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

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

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

>

> "Mark L Cooper" <mlcooper54_no_spam@aol.com> wrote on 01 jan 2008

> in microsoft.public.windows.terminal_services:

>

>> Thanks for the response

>>

>> All drivers came with each OS. No 3rd party. No updates from HP

>> web site.

>>

>> Server x64 driver that came with W2003 R2 x64

>> Client Vista driver that came with Vista Business (32 bit)

>> Client XP driver that came with XP (32 bit)

>>

>> Thanks,

>> Mark

>>

>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

>> in message

>> news:Xns9A17DCCA7CA95veranoesthemutforsse@207.46.248.16...

>>> An x64 server can only use 64-bit printer drivers.

>>> Where did the HP LaserJet driver come from? Are you using the

>>> driver which came with the OS (from the installation CD), or

>>> did you install a 3rd party printer driver?

>>>

>>> _________________________________________________________

>>> Vera Noest

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

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

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

>>>

>>> "Mark L Cooper" <mlcooper54_no_spam@aol.com> wrote on 31 dec

>>> 2007 in microsoft.public.windows.terminal_services:

>>>

>>>> A little more info.

>>>>

>>>> The TS is not a domain controller. It is set up as file

>>>> server, a print server with no printers attached, and a TS

>>>> Licensing server. It is running Sybase SQL Anywhere (ASA9).

>>>>

>>>> All servers and workstations on the network are running

>>>> Symantec Anti Virus 10.2.

>>>>

>>>>

>>>> The XP and Vista workstations are located in a different

>>>> facitly than the TS, connected over the Internet via a Gateway

>>>> to Gateway VPN.

>>>>

>>>> The topology of the network has not changed. We are in the

>>>> process of moving from the old W2000 Server to the new W2003

>>>> R2 x64 server....both located at the same location.

>>>>

>>>> Thanks,

>>>> Mark

>>>>

>>>> "Mark L Cooper" <mlcooper54_no_spam@aol.com> wrote in message

>>>> news:EC1C9F5C-AD74-455D-8BED-BEAF0535972A@microsoft.com...

>>>>> We just moved our main application from a W2000 server to a

>>>>> new W2003 R2 Std x64 server.

>>>>>

>>>>> We can run our main application on the new TS as usual from

>>>>> both XP and Vista clients.

>>>>>

>>>>> We've tested an XP client with an HP LaserJet 6P attached and

>>>>> a Vista Business client with an HP LaserJet 6P.

>>>>>

>>>>> We've tested with both normal 'user' accounts and

>>>>> administrator accounts.

>>>>>

>>>>> The client printer does show up as the default printer in the

>>>>> Windows Printer Select dialog box running on the TS.

>>>>>

>>>>> Testing with Notepad and a 1 word document on the TS and

>>>>> trying to print to the client printer gives the error "The

>>>>> handle is invalid." Printing to the client printer from the

>>>>> main application gives no error....nothing happens.

>>>>>

>>>>> All the above testing was done from both the XP and Vista

>>>>> client. The TS has all updates available through Microsoft

>>>>> Update installed. The Vista and XP clients have all updates

>>>>> available through Microsoft Update installed including Remote

>>>>> Desktop 6.

>>>>>

>>>>> Everything worked as expected when accessing the W2000 server

>>>>> from both XP and Vista.

>>>>>

>>>>> Any suggestions?

>>>>>

>>>>> Thanks in advance,

>>>>> Mark L Cooper

>>>>> Information Technology

>>>>> Perry County Ohio Bd of MR/DD

>>>>> New Lexington, Ohio