Terminal Server 2003 32 bit, Windows 7 64 bit printing issues

My 64 bit Windows 7 users cant print to their local hp 4100 printer while connected to a Terminal Server 2003 32 bit Machine. I'm assuming the reason is 64 bit drivers aren't compatible with the 32 bit native drivers. I've tried to change the 32 bit drivers to 64 bit with no success. the driver update fails.

Does anyone know how to get this to work ?
Who is Participating?
Andrew Hancock (VMware vExpert / EE MVE^2)Connect With a Mentor VMware and Virtualization ConsultantCommented:
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
are they network printing to the printer or client mapped printing?
hounschellAuthor Commented:
The printers on the Windows 7 64 bit computers are local printers some are usb connections and some are local using at tcpip port (on the local home network)
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
Okay so, this is local printing only.

There is no need to install a 64 bit printer driver on the Windows 2003 Teminal Server.

When a client logs on, Windows Server 2003-based server checks the name of the printer driver on the client and looks for the same printer driver name in the Ntprint.inf file. If the name of the driver is not found, the error messages are logged and the printer is not redirected.

Check the eventlog on the server, and I suspect that no printer appears mapped in their printers?

Install the 32bit driver on the server

follow this article to create a new custom print.inf file.

you need to match the driver name on the client, with the 32 bit driver on the server.

When they log in, and it will auto map their printer. The workstation 64 bit driver does the actually printing, but the spooler on the server, spools the job using the 32 bit driver on the server.

It's quite normal, that not all drivers are included.
I assume you're using in session printers.  

The 64-bit driver that is being used on the client-side will need it's 32-bit version installed on the Terminal Servers.  We have a couple of these, and we actually just use the HP UPD drivers.
hounschellAuthor Commented:
Worked perfectly ... thank you
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.