Major Printer Server Problems
-
-
@aaronstuder said:
@wirestyle22 said:
How many printers and how many different models?
Almost all HP.
Are they all the same model of HP though ie all the same driver?
-
It's like the print server doesn't see the printer. It can ping it fine.
I just tried to add one direct IP and that isn't working... What is going on here?
-
@Jason said:
@wirestyle22 said:
@aaronstuder said:
@coliver said:
Did you turn it off and on again?
Yes, the server, the printers, the computers. Everything.
How many printers and how many different models?
So the computers are connected to the print server just fine.. So it's something between the file server and the printers.. since it's all of them doing it. to me the network is the first place I'd start.
It could be but we have no way of knowing. There is very little information about anything.
-
@aaronstuder said:
Almost all HP.
You are using JetDirects? Haven't seen those in a decade. Not using regular servers? I have no idea how to manage those anymore.
-
@wirestyle22 said:
Are they all the same model of HP though ie all the same driver?
Yes, HP Universal.
-
-
@aaronstuder said:
@wirestyle22 said:
Are they all the same model of HP though ie all the same driver?
Yes, HP Universal.
That might be your issue actually. Try to install a different driver.
As a side comment you can use Web Jet Admin to manage the jet directs.
-
Ah. HP's.
Make sure SNMP is disabled on the printers. I've seen HPs stop talking when SNMP was enabled.
-
@wirestyle22 said:
@aaronstuder said:
@wirestyle22 said:
Are they all the same model of HP though ie all the same driver?
Yes, HP Universal.
That might be your issue actually.
As a side comment you can use Web Jet Admin to manage the jet directs.
Nah, Universal drivers are the best. Especially when deploying drivers from a print server.
-
Windows Update? We did just get new ones....
-
@Jason said:
@wirestyle22 said:
@aaronstuder said:
@wirestyle22 said:
Are they all the same model of HP though ie all the same driver?
Yes, HP Universal.
That might be your issue actually.
As a side comment you can use Web Jet Admin to manage the jet directs.
Nah, Universal drivers are the best. Especially when deploying drivers from a file server.
I don't mean they are bad I mean they might not be working. Changing it would take practically no time and would show whether or not it's a driver issue.
-
Direct IP does seem to be working.....
-
Do the printers print if you add one direct instead of going through the print server?
-
@aaronstuder said:
Direct IP does seem to be working.....
Meaning installing the printer locally on a computer by IP works? Signifying it's more likely to be a driver issue on the print server.
-
@aaronstuder said:
Direct IP does seem to be working.....
Try Stopping spooler on the print server
del c:\windows\system32\spool\printers*.*
Then Starting Spooler -
@Jason said:
@aaronstuder said:
Direct IP does seem to be working.....
Try Stopping spooler on the print server
del c:\windows\system32\spool\printers*.*
Then Starting SpoolerI assume that he already looked at the event log though. He would've seen the spooler crashing.
-
Logs seems clean.
-
Print spooler is running.
-
@aaronstuder said:
Logs seems clean.
Based on the information I have currently I think it's a driver issue.