Issues with LaserJet 5550 and Terminal Services

[Matt Emmott]

We are running a Windows 2003 Server as a Terminal Server, and are having issues with some printers, especially the LaserJet 5550, showing up when termed in. All users are on Windows XP Pro SP2.

Here's the scenario: I will install a LaserJet 5550 server on my local PC via a TCP/IP port to the print server. I will then tell my term services connection to connect my local printers on signon, and then log into the terminal server. My other printers will show up, but most of the time the LaserJet 5550 will not. Then, when I try to log out, the connection hangs at the logoff screen for upwards of five minutes. This seems to happen for all of our 5550s, not just one.

I have tried changing the drivers, and am currently using the "HP Universal Printing PCL 6" driver.

Is there something else I should be doing?

[WillNiccolls]

http://support.microsoft.com/kb/302361/en-us

that article explains that only certain types of printer ports are forwarded to the the RDP connection. Changing a registry key allows all printer ports (TCP/IP in your case) to be connected.

Hope this helps.

[Matt Emmott]

Thanks, but that doesn't help me - That fix is for users with locally attached all-in-one printers - All my users are connected to the 5550s via TCP across a Windows print server.