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

My remote user's printer won't link into a remote desktop session, tried everything

I have a remote user who needs to run an application on a server at our site but print from their local computer.  

No matter what I do, the remote user's printer will not show up in a remote desktop session.    I wonder if anyone else knows of something to try.

Remote computer -> VPN tunnel-> firewall->server

-- checked "printers" and "ports" in RDC options Local Resources tab
-- installed the printer driver on the server and the same printer driver on the remote computer
-- added FilterQueueType registry hack

I've even created a test setup on a machine I have access to: Downloaded the driver, created a dummy print queue , then connected through the same series of connections. My wn RDC session on the server links the dummy printer.   So it's not the VPN tunnel or the firewall.

If the remote user temporarily binds the printer to LPT1 it still won't show up for them.

There are two differences between my test setup and the remote user's:

- The remote user's printer is accessed across the network (physically connected to their wireless router; my dummy print queue is bound to LPT1
- The remote user has Windows 7 Home Premium (64-bit); I have Windows 7 Pro (64-bit)

Another possibility is that we're simply not waiting long enough; I don't know what quality of internet connection the remote user has.   My test setup went through a 4G connection.
Spencer Simpson
Spencer Simpson
3 Solutions
Please check the server's event log for printer messages (around the same time the user connects through rdp), maybe copy and paste here.
☠ MASQ ☠Commented:
Which printer are they trying to use? Any chance it uses Host-Based printing and so is unsupported in an RDC environment?

For example is it on HP's supported list?
Lionel MMSmall Business IT ConsultantCommented:
make sure they have the printer turned on and also check the security on the printer. you may save a lot of time by simply removing the printer and then reinstalling it. can you remote into this user's desktop and use the printer in question?
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Spencer SimpsonInformation Technology CoordinatorAuthor Commented:
It's a Brother HL-5370DW, and I see comments that specifically say it doesn't use host-based printing.   And this is Microsoft Remote Desktop so I'm not sure how a Citrix compatibility list will help.

Plus, as I said, I could get the dummy print queue to link in my test setup.

The only meaningful PrintService events I see are the successful default printer changes from my test environment connections.  

There is also a set of error messages from earlier in the day:

Installing printer driver - failed, error code 0xBC8, HRESULT 0x80070BC8.
Installing printer driver Microsoft enhanced Point and Print compatibility driver failed, error code 0xBC8, HRESULT 0x80070BC8.
Installing printer driver Microsoft enhanced Point and Print compatibility driver failed, error code 0x661, HRESULT 0x80070661.

and about 6 more like this all within 3 seconds of each other.   This is not the driver for the printer in question.

The RemoteDesktopServices-RDPCoreTS log contains a lot of events surrounding the RDC session connection and disconnection, but nothing I can decipher as a printer redirection.
Spike99On-Site IT TechnicianCommented:
Does the name of the driver on the local Windows 7 machine match the name of the driver on the server exactly? If it's even 1 space or letter off, printer redirection won't work and you will get Event ID 1111 errors in the event log.

I checked the downloads page for the Brother HL-5370DW, Brother's generic PCL driver is compatible with that model.  Have you tried the generic PCL driver?

I found the downloads on this page:
Spencer SimpsonInformation Technology CoordinatorAuthor Commented:
The remote user is using the same driver as the one installed on my dummy test queue, which links successfully through the tunnel.
Spencer SimpsonInformation Technology CoordinatorAuthor Commented:
It turns out there's nothing like doing it yourself.   When the remote user installed the driver, Windows kept the existing driver.   When I got (remote) access to their computer and installed the driver I downloaded myself  (a new queue to the existing wireless port using my driver), a remote desktop session was able to link the printer and the user was able to print.
Spencer SimpsonInformation Technology CoordinatorAuthor Commented:
After not succeeding with guiding the user, I realized I'd need access to the remote user's computer, and lionelmm suggested that too.  Alicia suggested I double-check that it was really the same driver as I had asserted.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

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