Win7 client connecting to Windows Server 2003 Terminal Server printer not mapping

Hi Experts,
I have a Win7 client (32-bit) connecting to my load-balanced Windows Server 2003 Terminal Servers (32-bit). I have about 100 users connecting to both of the Terminal Servers with about 100 print drivers without any issues. Now, I have a new Win7 client that has a HP M4345 MFP printer using the HP M4345 MFP PCL 6 driver. I installed the driver on the Terminal Servers without any issues but when the user connects, the printer doesn't map at all. I get a Event ID of "1111" which typically means that the print driver isn't on the server (which it is). I found KB article "KB302361", which is a registry change on the client computer. We did that, rebooted the client ans still no joy. I called HP support and they recommended using the Universal Print Driver, but I'd prefer to make this work using the specific driver for that printer. Any help would be much appreciated! Thank you!
ScorchToggsAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

dumpsterdivingdaveCommented:
I have found that there are a few printers (mainly older ones) where the drivers just don't work between Windows 7 and Server 2003.

First thing first...  How is this printer connected to the Windows 7 client?  Is this a network printer or connected via USB?

If it is a network printer, you can simply add the printer directly to the server and not have to worry about re-routing the print jobs through the Windows 7 client.  If it is a USB printer, you can try sharing the printer and then adding the shared printer as a network printer on the Server 2003.

Let me know if either of those work, or if you need me to elaborate.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ScorchToggsAuthor Commented:
Hi Dumpster:
Yes, I should have mentioned how the printer was connected! It's a brand new HP 4345 MFP that is connected to the network directly at the client site. The printer works fine locally (when NOT connected to TS), so we know it works. I have the exact driver on the server as the WIn7 client.
0
ScorchToggsAuthor Commented:
Dupmpster: I think you're referring to an IP Printer install when you say "add the printer directly to the server"? I'll try the IP setup in a few minutes to see if that helps. I'll follow up shortly. Any other ideas?
0
dumpsterdivingdaveCommented:
If it is a network capable printer, I would directly add it to the server as a local printer and skip the TS mapping.  This way, the print job can be directly sent from the server to the printer and not have to be sent from the server to the PC and then from the PC to the printer.  If you need to know how to do that, just let me know what the IP Address of the printer is.
0
ScorchToggsAuthor Commented:
IP printer install worked.  Thank you!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.