Major Printer Server Problems
-
@wirestyle22 What one should I try?
-
@aaronstuder said:
@wirestyle22 What one should I try?
I don't know what models you are currently using but if hypothetically you have an hp 4250, install the actual drivers for that printer and see if it works. That would prove that it is in fact a driver problem. Then download the latest Universal Drivers and 'replace' them on the server. Even if they are the same version I have run into similar problems and reinstalling the drivers has worked. I hope this is the case for you.
-
I would restart the print spooler service as my first step.
-
@brianlittlejohn said:
I would restart the print spooler service as my first step.
Yep even if it's running you should stop it, clear it and restart it.
-
@aaronstuder said:
@scottalanmiller said:
You are using JetDirects?
No, just the built-in cards.
HP Printers if they have built in print servers are JetDirect.
-
@Jason said:
@brianlittlejohn said:
I would restart the print spooler service as my first step.
Yep even if it's running you should stop it, clear it and restart it.
Have, a bunch of times.
-
@aaronstuder said:
@Jason said:
@brianlittlejohn said:
I would restart the print spooler service as my first step.
Yep even if it's running you should stop it, clear it and restart it.
Have, a bunch of times.
Did you delete those files in the directory?
-
@Jason said:
@aaronstuder said:
@Jason said:
@brianlittlejohn said:
I would restart the print spooler service as my first step.
Yep even if it's running you should stop it, clear it and restart it.
Have, a bunch of times.
Did you delete those files in the directory?
Also there may not be any files in there FYI. It's not a guarantee that they will be in there.
-
@wirestyle22 said:
@Jason said:
@aaronstuder said:
@Jason said:
@brianlittlejohn said:
I would restart the print spooler service as my first step.
Yep even if it's running you should stop it, clear it and restart it.
Have, a bunch of times.
Did you delete those files in the directory?
Also there may not be any files in there FYI. It's not a guarantee that they will be in there.
Yes. But they should be deleted if they are to help with troubleshooting.
-
@Jason said:
@wirestyle22 said:
@Jason said:
@aaronstuder said:
@Jason said:
@brianlittlejohn said:
I would restart the print spooler service as my first step.
Yep even if it's running you should stop it, clear it and restart it.
Have, a bunch of times.
Did you delete those files in the directory?
Also there may not be any files in there FYI. It's not a guarantee that they will be in there.
Yes. But they should be deleted if they are to help with troubleshooting.
Absolutely.
-
and have you tried to print directly from a workstation to the printer? set it up local via IP and see if it works. This almost seems like a joke post? or maybe you've already started drinking?
-
-
IMO it's not a driver issue if it can't serve the printers. Driver issues will occur after you try adding the printer from your workstation
-
Have you tried deleting the printers and ports on the server. Then re-adding them?
-
@IRJ said:
IMO it's not a driver issue if it can't serve the printers. Driver issues will occur after you try adding the printer from your workstation
The question is.. Can the Print server itself print?
I don't think it's a driver issue either. Depending on how you install the new driver it might solve your issue, but I don't think the driver itself is the root cause.
-
Are the printers showing offline?
A Major break in all printers at once like this almost points to Windows Update, or a setting change on the server itself. You just dont see 50 printers all not work at the same time.
I'd restore yesterday's backup. There is no reason not to do it. It's not like you have any critical data on the print server (at least I hope not.)
-
@IRJ said:
IMO it's not a driver issue if it can't serve the printers. Driver issues will occur after you try adding the printer from your workstation
There is very little information. You may be right. I know that I have run into similar problems and it's been driver related.
_(ツ)_/¯
