Share via

Windows RDP User Printer Redirection issue

Anonymous
2023-12-28T12:51:15+00:00

Hi,

we are using RDP User CAL some of users facing issue issue in printing, they are printing in local printers.

then some time its stopped working & will restart server then will work but again that issue is repeating.

then again once we restart it will work again..

Out windows server in 2016 standard and I attached log image also which I'm getting from server ..

Windows for business Windows Server User experience Print, fax, and scan

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments

7 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2024-04-25T21:29:32+00:00

    Hi,

    1. Restart the print spooler: Go to the Services app in Windows, find the "Print Spooler" service, and restart it.

    if we will try to restart printer spooler in server it will give error, then we have to restart server then it will work back printing...

    I have the exact same problem running on Windows Server 2019 Standard.

    all workstations and server are on same network, all printers are USB connected to the workstations.

    half of the workstations stop printing suddenly.

    Restarting spooler service, or resetting spooler does not help resolve this issue.

    Only temporary fix is rebooting the server, which is really annoying to do that in the middle of a work day when everyone is logged on and doing work.

    there must be some other thing causing the printers to stop printing besides the spooler.

    3 people found this answer helpful.
    0 comments
  2. Anonymous
    2024-09-05T05:41:19+00:00

    Just as a workaround: fully logout of remote profile and relog back in. The problem seems to begin once the rdp session profile is locked upon exiting the rdp session. I do not know if this issue is server related as the brother printer I encountered this on is locally connected via usb and not shared over network.

    0 comments