• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1442
  • Last Modified:

cannot see local printers through remote desktop

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
bytemeal
Asked:
bytemeal
1 Solution
 
moondistCommented:
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
 
bytemealAuthor Commented:
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

A Cyber Security RX to Protect Your Organization

Join us on December 13th for a webinar to learn how medical providers can defend against malware with a cyber security "Rx" that supports a healthy technology adoption plan for every healthcare organization.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now