Solved

cannot see local printers through remote desktop

Posted on 2007-11-15
2
1,421 Views
Last Modified: 2012-08-13
I regularly remotely access two different Windows 2003 Terminal Servers using either the standard Microsoft RDP client software or though a Remote Desktop MMC at two completely different offices (lets call then site A and site B).  For some reason when signing into site B i cannot see the printers installed on my local machine .. neither network printer can be seen (Brother HL5250 laser, Brother MFC9180) which are connected via USB to a server in our local network and shared out ... strangely enough though I CAN see the Microsoft Document Image Write as well as a 3rd party PDF printer.

Initially neither site would work at all however after applying this patch from microsoft http://support.microsoft.com/?kbid=302361  , everything works when signing into site A

Further detail if required .. The working site (A) connects to the internet using a Draytek 2800VG and I simply redirect port 3389 to the terminal server .. the non working site (B) connects using a Draytek 2600V with the same port redirection method.  The local site I'm dialiing out from using a Draytek 2800VG also.

Any ideas anyone?  Thanks in advance for any asistance, let me know if anymore detail is needed
0
Comment
Question by:bytemeal
2 Comments
 
LVL 4

Accepted Solution

by:
moondist earned 500 total points
ID: 20295641
Check the event logs for errors. The server has to have the drivers installed for the printer on the RDP client. If not it will post an error in the system log. If that is the case install the printers on the server to a "null" local port. Then the server will have the drivers.

If that is not the issue, check the Terminal services Manager configuration and the user account on the server you are logging in with. Make sure the both have the connect printer ability enabled.

Post your findings.
0
 
LVL 1

Author Closing Comment

by:bytemeal
ID: 31409489
Got it in one!  the working remote site has identical printers to our local site so the server already carried the correct drivers .. inital driver installation to a null port and then logging out and back in again resolved the issue.   Thanks heaps for your help!
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

On July 14th 2015, Windows Server 2003 will become End of Support, leaving hundreds of thousands of servers around the world that still run this 12 year old operating system vulnerable and potentially out of compliance in many organisations around t…
Use of TCL script on Cisco devices:  - create file and merge it with running configuration to apply configuration changes
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

776 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question