Local printers over RDP

[HCHTech]

This is a remote employee of a client. They access their computer with RDP over a VPN connection to the office. Initial report was that they couldn't print to their local printer. It would work one day and then not the next. Reboots on both ends and reconnecting sometimes worked, and sometimes not. When it doesn't work, the work computer sends the job to the redirected printer, but nothing prints and nothing is left in the printer queue.

• Nothing in any of the logs I looked at jumped out as a problem. No RDP errors on connection or anything like that.
• I deleted and re-made the RDP shortcut
• I've tried restarting the print spooler service on both computers as well
• I made sure their home computer was on 25H2, latest drivers, etc. The home computer is a well-specced Dell XPS13. (Speced? Spec-ed?).
• The work computer is a 1 year old Lenovo M70a tiny. Already on 25H2 and drivers are up to date.
• The printer was a 4-year old HP deskjet that they paid all of $69 for, so I just recommended they get a new printer - which ended up being a $250 Brother inkjet MFP. Both printers were installed with the full software package from the vendor.
• The printers both have static IPs

The same problem exists with the new printer. They left the old printer in place (both are wifi, as is the computer - access point is Verizon FIOS residential modem about 8 feet away from the computer and 12 feet away from the printers. One day the old printer will work but not the new one, the next day the new one will work but not the old one. This is where we are now since I'm out of suggestions to offer the guy.

Over time, I'm seeing (copy 1) printer definitions, but that's a problem as old as Windows itself, so I don't think it's related.

Any suggestions on how to troubleshoot this problem further? Or how to make the whole redirection thing more robust?

 

[YeOldeStonecat]

With modern remote desktop solutions...(such as Splashtop Business)....I really started to hate old school clunky VPN with RDP setups.
Splashtop Business..remote printing works like a champ!

But...with this setup...
*Ensure the host printer is on a static IP (I see you have this). Even though windows defaults printers now to WDS which "should" easily adapt to a different IP address for the device, I find it's not all that great. Granted...pain in the butt sometimes doing statics with an ISP gateway...this is where ensuring your own network equip like Unifi is in place saves you time thus saves the client money in the long run.
*I find the "full bundles" of software aren't always the best, often most brands offer a "Universal Print Driver". Granted...although I prefer HPs...I do find that Brother usually has fairly compatible drivers for universal print. But worth a check.
*Ensure the Windows host has "network browsing" enabled. I always drill into File Explorer...Network...and enable that tan banner that pops up to make the network private and explorable in firewall settings. Helps with printers.

 

[Sky-Knight]

See... if you have a local printer attached to your device when you RDP to something that doesn't suck... it "just works".

If it doesn't... replace the printer. Easy Print has been a thing for over a decade, if the printer cannot handle it THROW IT AWAY.

 

[trevm999]

What application are they printing from?

Every time a user connects to RDP with redirected printers new registry entries get added to the User's registry hive. (I think in 2 places) I'd start by clearing them out.