newfocus1
asked on
Terminal server 2003 print spooler hangs
I have a client that has a Dell server. 40gb front end 100gb back end. He has 12gb left on c partition. 4gb ram. The server is a DC and terminal server. I know it is not the best but the client wanted to save money. He is sharing windows office 2007 and Quickbooks. What occasionally happens is some one will send print job through terminal server and terminal session will lock up. In some instances i can just restart the print spooler in other cases i have to restart server. The remote users have many print drivers because they go to different clients.
There are about 20 people internally and 10 people remotely.
Thanks for your help
There are about 20 people internally and 10 people remotely.
Thanks for your help
Any event log errors we can see? This sounds like a bad print driver that needs to be replaced / reinstalled. Look through the event log and see what happening right before the server locks up.
ASKER
Thank's Axyre. I should have thought of that. When I look at the event log the terminal server errors point to numerous printers. Stating that the driver is not loaded. These look like printers that are out at remote sites. Do i have to load the correct print driver for each one of those printers on the laptops that are communicating remotely?
Thanx
Thanx
Hi
Does the printer spooler use a lot of memory? This might be cause of bad printer drivers and old print jobs that are trying to print; check %windir%\system32\spool\PR
The safest route with print drivers is trying to find MS certified drivers. We had alot of issues with insession printers and UNC printers. We disallowed these methods and installed the printers locally. This more IT overhead, but the drivers cannot bring down the spooler or the server since the drivers have to be installed by us.
Avoid drivers that want to intstall software, espcecially the MFP or AIO printers. Theses apps are not TS friendly.
Does the printer spooler use a lot of memory? This might be cause of bad printer drivers and old print jobs that are trying to print; check %windir%\system32\spool\PR
The safest route with print drivers is trying to find MS certified drivers. We had alot of issues with insession printers and UNC printers. We disallowed these methods and installed the printers locally. This more IT overhead, but the drivers cannot bring down the spooler or the server since the drivers have to be installed by us.
Avoid drivers that want to intstall software, espcecially the MFP or AIO printers. Theses apps are not TS friendly.
ASKER
thank's Johannortje. It sounds like a great idea. When you say locally you are talking about the server correct?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.