Common Windows Issues: Mapped Printers Unreachable


 

Problem:  Client printers (printers either directly attached to your remote workstation, or network accessible printers) do not map when you establish a Remote Desktop Connection to a Cloud Server.  
 
Cause:  This can be caused by driver mismatches, client settings, server configuration settings, or user profile settings in Active Directory.
 
Resolution:  You will need to update printer drivers, check the Local Resources configuration for your Remote Desktop Services, and check Active Directory user permissions (if applicable). 
 
  1. Visit the printer manufacturer’s website and download/install the appropriate driver for the OS and processor architecture (x86 or x64) on both the workstation and the server – the drivers you download must be the EXACT same version in order for mapping to function (i.e. PCL6, PCL5, PS, etc). If the server is x64 and the client is x86, you will need to load both driver types on the server in order for the printers to be mapped. To do this:
  • Click Start -> Printers, highlight an existing printer, then hit the Print Server Properties button at the top of the screen.
  • Select the Drivers tab, and click the Add button.  In the screen where you’re prompted for the processor type, select both the x64 and x86 boxes, click Next, and locate the appropriate driver packages for installation.

  2.  Ensure that Remote Desktop has client printers set to map. To do this:

  • Open up the Remote Desktop client and click the Options button.
  • Click on the Local Resources tab, and check to see that there is a check in the box assigned to printers.

  3.  Ensure that the Terminal Services Configuration (2003 R2 and 2008) and the Remote Desktop Services Configuration (2008 R2) allows for client printer mapping.

  • For Windows 2008:  Click Start, Administrative Tools, Terminal Services, Terminal Services Configuration.  On the left pane, select RD Session Host Configuration and then right-click RDP-Tcp within the Connections section of the right-hand pane, then select Properties.  In the window that pops up, click the Client Settings tab and make sure that the box next to Windows Printer is UNCHECKED (read: a check in this box means printer mapping is DISABLED).
  • For Windows 2008 R2:  Click Start, Administrative Tools, Remote Desktop Services, Remote Desktop Host Configuration. On the left pane, select RD Session Host Configuration and then right-click RDP-Tcp within the Connections section of the right-hand pane, then select Properties.  In the window that pops up, click the Client Settings tab and make sure that the box next to Windows Printer is UNCHECKED (read: a check in this box means printer mapping is DISABLED).
  • For Windows 2003 R2: Click StartAdministrative ToolsTerminal Services Configuration. Select the Connections folder and right-click RDP-Tcp and select Properties.  In the window that pops up, click the Client Settings tab and make sure that the box next to Windows Printer Mapping is UNCHECKED (read: a check in this box means printer mapping is DISABLED).  Note:  Rackspace no longer offers Cloud Servers with Windows 2003, but these instructions are here for legacy support purposes.  
  4.  Ensure that the Active Directory user profile has rights to map client printers during login.  
  • Click Start, Administrative Tools, Active Directory Users and Computers.  Locate the user that you wish to edit, right-click the user object and select Properties.  Click the Environment tab and make sure there is a check in the box next to Connect Client Printers at logon.
 

 



Was this content helpful?




© 2011-2013 Rackspace US, Inc.

Except where otherwise noted, content on this site is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported License


See license specifics and DISCLAIMER