Tag Archives: desktop

Setup local printer to use through Remote Desktop Connection (RDP) – KB1039900

KB1039900

Description:  Print to local computer through remote desktop session.

Common customer description: I can’t print to my local printer from my Remote Desktop.

Probing questions:

Were you able to print and now it no longer works?
Has anything changed recently?
Did you get a new printer?

Steps to isolate: Make sure the local computer can print to the local printer.

Steps to resolve:

To make a local printer available in a Remote Desktop session:

  1. Click Start, point to All Programs, point to Accessories, point to Communications, and then click Remote Desktop Connection.
  2. Click Options in the Remote Desktop Connection dialog box.
  3. Click the Local Resources tab.
  4. Click Printers in the Local Devices box.
  5. Click Connect.

Additional considerations:

There are some limitations to this feature.  The printer in question must be capable of having its drivers installed remotely.  A lot of store bought “office” printers that are on the low cost scale cannot do this.

Example: HP LaserJet Pro P1102W is a sub $100 printer.  This printer will not install drivers remotely.  The drivers, while installing, will ask to have the printer connected to the computer you are installing the drivers on.  If you are remotely connected to another computer that does not have a physical connection with the printer the drivers will not install.

Sometimes there is a work around to this problem.  If the client is willing to have the printer taken to the remote desktop location, and install the drivers while the printer can obtain a physical connection, some of the lower priced printers will work via RDP connections.  But not all will.

Good way to make sure is, can the drivers be installed remotely and/or is the printer above $400 in price?  If you answer no to either or both it probably cannot perform printing through RDP.

Cannot connect to Desktop PC – KB1039773

KB KB1039773

Cannot Connect to Desktop PC

If you can’t connect to a person’s computer through Go To Assist or Logmein Rescue, there are a few things you can try in order to connect.

1. Remote Desktop – This is usually the first thing to try in order to connect. You will need to know either the IP address or name of the machine. If the user doesn’t know the name or IP, have them open a Command Prompt and type ipconfig. Look for IPv4 address. For finding the name, in a Command Prompt type hostname and hit enter. The result is the computer’s name. Then just log on to the OM -> go to Start -> Run -> type mstsc -> hit Enter -> type in the computer name or IP address -> click Connect. You may need to specify the Fully Qualified Domain Name (FQDN). It would look like computername.domain.local.

2. Service Center – If the computer is listed in Service Center, try connecting to it there. Otherwise see if you can connect to the remote Command Prompt or remote Services.

3. VNC – From the OM, go to D:TechAdvantageToolsVNC. Choose one of the VNC options, Push VNC, RealVNC, or UltraVNC. Push VNC does not need to be installed. Enter the computer’s name or IP, then user and password. Once you have those in, try connecting.

4. Safe Mode with Networking – If nothing else works, try turning the computer off. Boot it back up, but immediately start tapping the F8 key at a quick pace. This should load up some boot options. Choose Safe Mode with Networking. See if you can connect to their machine now.

5. If none of these worked, chances are we will need to onsite the issue. Speak with Tier 2.