Terminal services printing problem

[krose]

I thought I'd ask this in networking but if it should be in peripherals please move it.

My wife's business has a server running Win2K terminal services. A branch office needs to print documents from the server to a local printer via remote desktop. This desktop computer runs Win2K. RD is configured to connect to the local printer. This all worked fine with a Brother 1440 laser printer which was connected to the desktop via parallel port. The printer died so I need a replacement. Of course most are USB now, so I tried to get a USB printer to work with RD.

I logged in to the server from home, and using the add printer wizard, added my Canon ip5200 as a local printer to the terminal services port assigned to my session. Printed a test page and a couple of test documents to the Canon and all was well. When I log on the server from home the Canon is the default printer for my session, as it should be. Great, it works! But not so fast...

I checked the local ads and decided to pick up an HP P1006 laser since it was on sale. The branch office doesn't print all that much so this should do fine. Yesterday I went to the office and installed the printer, tested it and it worked fine. I logged onto the server and repeated the procedure I used at home for the Canon to add the HP. Printed a test page and a couple documents so I though at was well. But no, today I get a call that it doesn't work. From remote desktop I opened the printer to see the print queue. Print jobs would spool and print, but nothing comes out of the printer. I had the user open the printer on the local desktop which shows the first job as printing and the rest just sitting there queued. Delete the jobs and try again, same result. Tried it at home and the Canon still works fine. Anybody have any ideas as to what's wrong? Is it just that the HP won't work this way? Should I return it and get a parallel printer if I can find one? Thanks in advance.

 

[kstornado]

See if the following applies to your situation.

http://support.microsoft.com/kb/302361

 

[krose]

Thanks. I saw that article before but figured it should work because the local port is named USBxxx and should be redirected. I just tried the registry fix but no luck. It tries to print but nothing happens. Then I see it trying to delete the print job in the printer window but nothing happens either. So it just sits there so you have to reboot the server to fix that. Looks like the HP driver doesn't support terminal services printing. Unless I can find a printer driver that does, looks like I need to go shopping again.

 

[RebateMonger]

There are also "universal printer drivers" that can be installed on the server and client. The ones I've tested work very well. But they don't give them away. They are either licensed per Server (unlimited users) or per User. There are usually free trial periods.

 

[krose]

I found universal drivers on the HP website but it doesn't support this model. I am just going to return this and for $20 more get a Brother HL-5240, it has a universal driver designed to work with terminal services. I learned a lesson about doing better research before shopping.

 

[RebateMonger]

Originally posted by: krose
I found universal drivers on the HP website but it doesn't support this model.

Different principle. I meant something like this:

Uniprint Terminal Server Edition

 

[krose]

Thanks for the information. I got the Brother and it is working fine over remote desktop. I used a "universal driver" on their website that is specifically for terminal services. The install was painless. Thanks again.