Terminal Server Local Printers not Coming over from Client

[brady12345]

Hello Everyone,

We have terminal server installed on windows 2003 server and all clients are windows xp system.

I am trying to connect my local and network printers while accessing terminal serve but I am not able to see any of my local printers on terminal server.

All setting with the RDP are to set to connect printers.

Thanks in advance,

Bracy

 

[PPettit]

This may help:

"Printers That Use Ports That Do Not Begin With COM, LPT, or USB Are Not Redirected in a Remote Desktop or Terminal Services Session"

Microsoft Knowledge Base article 302361

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

 

[Dublin73]

All setting with the RDP are to set to connect printers."

This is set in 2 places, in the user properties in Active Directory and at the Terminal Server itself, on the RDP connection.

I presume you have tested this by logging in with a domain admin account? The default behaviour is... when you log in with an account that has admin rights over the server, Windows will map your local printer, installing the driver for it if it isn't installed already

 

[brady12345]

I tried that Knowledge Base article but it didnt do the trick. As for the setting to connect remote printers, thats set. The thing is, I have tested it on different computers and seems that only certain printers dont copy. The HP 4300's, Micrsoft Image Writer are examples of ones that copy over but like an HP mfc-3050 or brother mfc-8220 do not copy over?
I even tried updating to RDP v. 6 and it doesnt bring these MFC printers over.

 

[brady12345]

Do you think it could be the TS needs a driver for these types of machines?

 

[PPettit]

Did you make the necessary registry changes on each workstation and then reboot them before logging into the server? The registry modification should have exposed pretty much anything that shows up in your "Printers and Faxes" folder.

Like brady12345 mentioned, you may need to install the specific driver for each device. I'm surprised that the HP doesn't work. I have almost no trouble with HP printers.

The Brother may be a problem if it's a "host-based" printer. Those generally don't work well with TS. Check out this link if you're unfamiliar with the term:

http://www.pcmag.com/encyclopedia_term/0,2542,t=host-based+printing&i=57256,00.asp

 

[kenred]

We had the samee problem here, the drivers do need to be installed on the Terminal Server. You can see all the failed printers in the Event Logs.

Microsoft have a tool that makes the installations a bit easier for you at

http://www.microsoft.com/downloads/...E9-40DB-484F-862E-38A094EEEAF7&displaylang=en

you just run the program, it comes up with all the problem printers and you install the drivers for them.

This worked for us, if I have missunderstood the question I apologise.

Ken

 

[brady12345]

You are right, thanks! Also, has anyone had any luck scaning from a local MFC machine, like a HP 3050 to a terminal server??

Thanks