?
Solved

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

Posted on 2011-02-17
6
Medium Priority
?
1,357 Views
Last Modified: 2013-11-21
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 ?
0
Comment
Question by:hounschell
  • 3
  • 2
6 Comments
 
LVL 124
ID: 34922606
are they network printing to the printer or client mapped printing?
0
 

Author Comment

by:hounschell
ID: 34922636
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)
0
 
LVL 124
ID: 34922674
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.
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 11

Expert Comment

by:yelbaglf
ID: 34922675
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.
0
 
LVL 124

Accepted Solution

by:
Andrew Hancock (VMware vExpert / EE MVE^2) earned 2000 total points
ID: 34922676
0
 

Author Closing Comment

by:hounschell
ID: 34922821
Worked perfectly ... thank you
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Some time ago I faced the need to use a uniform folder structure that spanned across numerous sites of an enterprise to be used as a common repository for the Software packages of the Configuration Manager 2007 infrastructure. Because the procedu…
Know what services you can and cannot, should and should not combine on your server.
This video Micro Tutorial explains how to clone a hard drive using a commercial software product for Windows systems called Casper from Future Systems Solutions (FSS). Cloning makes an exact, complete copy of one hard disk drive (HDD) onto another d…
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…
Suggested Courses

809 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question