MYTAIR
asked on
Print fails when RDP from Win 7 to Win2008R1 to Win2003R2
If i connect to my 2008R1 32bit server my printers are redirected and print works just fine, the print driver for all the printers are "Easy Print"
But i have one application that runs on a Win2003R2 32 bit box, and if I connect to this server from the rdp session i have on the win2008R1 the printer is redirected, but the print driver on the 2003 server is HP deskjet 500, and if i try to print the print job is send from the 2003 server to the 2008 server, but it stops there it never gets to my computer and the print is lost.
I have upgraded the RDP client on the 2008R2 server to 6.1(protocol 7.0), and i have installed XPS essentials and the 2003 server but stile i have the same problem.
If i connect direct from my computer to the 2003 server, print works fine but all my users can't do that do to network restrictions.
But i have one application that runs on a Win2003R2 32 bit box, and if I connect to this server from the rdp session i have on the win2008R1 the printer is redirected, but the print driver on the 2003 server is HP deskjet 500, and if i try to print the print job is send from the 2003 server to the 2008 server, but it stops there it never gets to my computer and the print is lost.
I have upgraded the RDP client on the 2008R2 server to 6.1(protocol 7.0), and i have installed XPS essentials and the 2003 server but stile i have the same problem.
If i connect direct from my computer to the 2003 server, print works fine but all my users can't do that do to network restrictions.
Doing a "double hop" RDP connection will almost always cause issues with the redirected printers that are installed on the client PC.
Two suggestions:
1. install printers on the 2008 Terminal Server using drivers installed on the 2003 server (so printers will redirect from the 2008 server to the 2003 server)
2. if that doesn't work, have users connect to the 2003 R2 server directly from their client PCs (.
but, there are a couple of things to look for in the event logs of the 2003 server to see if the printers are being seen at all.
when the option to redirect printers is selected in the RDP connection, the remote server will try to load that printer for the user, but it won't be able to if the driver isn't installed. If the driver isn't present on the remote server, you will see an Event ID 1111 error in the System Event log. That will give you the name of the driver that the server fails to recognize when the user logs on. this confirms that the driver is the reason why the printer isn't being redirected.
I hope this helps.
Alicia
Two suggestions:
1. install printers on the 2008 Terminal Server using drivers installed on the 2003 server (so printers will redirect from the 2008 server to the 2003 server)
2. if that doesn't work, have users connect to the 2003 R2 server directly from their client PCs (.
but, there are a couple of things to look for in the event logs of the 2003 server to see if the printers are being seen at all.
when the option to redirect printers is selected in the RDP connection, the remote server will try to load that printer for the user, but it won't be able to if the driver isn't installed. If the driver isn't present on the remote server, you will see an Event ID 1111 error in the System Event log. That will give you the name of the driver that the server fails to recognize when the user logs on. this confirms that the driver is the reason why the printer isn't being redirected.
I hope this helps.
Alicia
ASKER
Hi
I was out of office Friday, but i will try your suggestions today and give feedback.
I was out of office Friday, but i will try your suggestions today and give feedback.
ASKER
I have tried to install the same printer driver on the 2003R2 box as is installed on my local PC and on the 2008R1 box but print still dossent work.
When i log on to the 2008R1 box the print driver isn’t used, the server uses "Terminal Services Easy Print" so i think that when I log on to the 2003R2 box the 2003 can't recognize a driver called "Terminal Services Easy Print" and it falls back to "HP deskjet 500".
I have add screenshots of the print propperties for the servers
Unfortunately it is not an option for the users to connect to the 2003 server directly :(
print-on-2003.jpg
print-on-2008.jpg
When i log on to the 2008R1 box the print driver isn’t used, the server uses "Terminal Services Easy Print" so i think that when I log on to the 2003R2 box the 2003 can't recognize a driver called "Terminal Services Easy Print" and it falls back to "HP deskjet 500".
I have add screenshots of the print propperties for the servers
Unfortunately it is not an option for the users to connect to the 2003 server directly :(
print-on-2003.jpg
print-on-2008.jpg
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
?
Also, check the event logs when the user logs in. Are there any Terminal Server events stating problems mapping the printer?