kserritt
asked on
Terminal Services not redirecting to local printer
I am trying to configure terminal services to redirect printing to the local printer. According to the staff it was working correctly at one time but I didn't configure it then. The terminal server is on a remote network that is connected through VPN it is running Windows Server 2003. The client machines are all running Windows XP. The printer is a local network printer connected through TCP/IP to the client machines. They can print to the printer locally but are not given the printer as a option when connected via Terminal Services. I have only done this once before and it was years ago on a 2000 server so I very well could be missing something simple.
In Terminal Services Configuration I have set the RDP-Tcp to "Connect client printers at logon". I have checked to make sure that "Windows printer mapping" is not disabled.
In AD under the connection tab for the user I have it set to "Connect client printers at logon" and "Default to main client printer".
I have checked the GPO under Computer Configuration\Administrati
I am not sure what else at this point to check. Thanks in advance for any help you can give me.
Kansas
In Terminal Services Configuration I have set the RDP-Tcp to "Connect client printers at logon". I have checked to make sure that "Windows printer mapping" is not disabled.
In AD under the connection tab for the user I have it set to "Connect client printers at logon" and "Default to main client printer".
I have checked the GPO under Computer Configuration\Administrati
I am not sure what else at this point to check. Thanks in advance for any help you can give me.
Kansas
ASKER
It appears that now the locally attached printers are redirecting but the tcp/ip printer is not redirecting. The tcp/ip printer is the one they have always used.
I do not see any errors in the event logs. I see where it is connecting the local printer and then deleting it after the session ends but I don't see any error logs for the TCP/IP printer.
I do not see any errors in the event logs. I see where it is connecting the local printer and then deleting it after the session ends but I don't see any error logs for the TCP/IP printer.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Ok I have updated the RDP client to 6.0 and that still is not working. How do I need to go about installing the print driver on the server so I can double check that.
Install that printer locally on the term server to get the driver on it. What kind of printer is it?. Since you updated the rdc client, do you see errors now in the event log related to that printer not redirecting?
ASKER
Ok I upgraded the RDP client on one of the computers and it didn't solve the problem but that computer was using an older version of the print driver that was not on the server. When I upgraded the client that is using the same version driver as the server it worked. Wow I have racked my brain all day on this and never thought about upgrading the RDP client that was just working correctly 4 weeks ago. I guess someone has updated the server that I wasn't aware of.
Thank you so much for your help.
Thank you so much for your help.
we have had a number of issues with this here in our office and a number of our remote offices, it seems to affect HOST based printers which rely on the pc for processing power, the only way round we have found is to purchase a seperate utility called thinprint RDP engine, from www.thinprint.com we now have no issues what so ever
According to Microsoft KB Article KB302361:
http://support.microsoft.c
When you use Remote Desktop Connection or the Terminal Services Client version 4.0, 5.0 or 6.0 to connect to another Windows-based computer from a computer, your local printers are not redirected. As a result, your local printers are not available in the remote desktop or terminal services session.
To fix this problem on a computer that is not running Windows Server 2003 as a Terminal Server, force all ports (including DOT4) on the client computer to be filtered for redirection. To do this, add a DWORD value named FilterQueueType to HKEY_CURRENT_USER\Software
Follow these steps:
1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following key in the registry:
HKEY_CURRENT_USER\Software
3. On the Edit menu, point to New, and then click DWORD Value.
4. Type FilterQueueType, and then press ENTER.
5. On the Edit menu, click Modify.
6. Type FFFFFFFF, and then click OK.
7. Close the Registry Editor.
8. Restart your computer.
This enables all ports on the client to be redirected.
http://support.microsoft.c
When you use Remote Desktop Connection or the Terminal Services Client version 4.0, 5.0 or 6.0 to connect to another Windows-based computer from a computer, your local printers are not redirected. As a result, your local printers are not available in the remote desktop or terminal services session.
To fix this problem on a computer that is not running Windows Server 2003 as a Terminal Server, force all ports (including DOT4) on the client computer to be filtered for redirection. To do this, add a DWORD value named FilterQueueType to HKEY_CURRENT_USER\Software
Follow these steps:
1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following key in the registry:
HKEY_CURRENT_USER\Software
3. On the Edit menu, point to New, and then click DWORD Value.
4. Type FilterQueueType, and then press ENTER.
5. On the Edit menu, click Modify.
6. Type FFFFFFFF, and then click OK.
7. Close the Registry Editor.
8. Restart your computer.
This enables all ports on the client to be redirected.
Have you updated those servers recently? We had similar problems, ended up having to upgrade the RDC client to the latest version to get printer redirection working again.
If you do have the latest version, check event logs for the time when logging on, see if there are errors related to printer redirection. If there are erros, such as it couldn't connect printer whatever, then you probably have a driver mismatch. Is it all printers (locally attached and that tcp/ip printer you installed as local), or just some that aren't redirecting?
T