Link to home
Start Free TrialLog in
Avatar of robtheplod
robtheplodFlag for United Kingdom of Great Britain and Northern Ireland

asked on

Printers crash whilst spooling on Windows 2016 Remote Desktop server.

Hello all.

We have a Window's 2016 server with remote desktop and are having some issues with printers dropping out. We have a remote desktop environment with multiple printers. The model of the printers are as follows, UTAX P-4530DN, UTAX P-4530DN, UTAX P-4530DN KX, those are the main three with the problem. The issue originally was that they were disappearing from the RDS servers whilst users were signed in. However we managed to resolve this problem we adding it manually to each of the RDS servers. Unfortuantely this sparked another issue, and now the jobs get half way through spooling and the printers have to have their queues cleared and then have to be restarted. Once that has been done it will start to work again. They are added via IP address, and the printers have a physical connection to the network which is on the clients site.

I was wondering if anyone else had this issue, and if anyone could suggest why this might be happening? Please ask my anything if I have not been clear enough.

Thanks,

Kieran
Avatar of Sajid Shaik M
Sajid Shaik M
Flag of Saudi Arabia image

did you installed the proper printer drivers all the printer drivers on the terminal server ?

did you check print spooler crash logs on the event viewer ?

delete all drivers and re install all

go to devices and printers select any printer on the top bar will appear ..click print server properties - drivers - select all one by one and click remove...

and re install the latest drivers using windows update as first priority ... if not then manufacturer web site...

all the best
This question needs an answer!
Become an EE member today
7 DAY FREE TRIAL
Members can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.