![]() I ended up posting signs around each printer asking the person to check the printer for paper BEFORE printing. So as the application wasn't open and the printer only knew that it had pages to print, it didn't know WHAT to print, and would freak out and spit out all of this garbage. The problem was that because such a great quantity of jobs were sitting in queue, all of the applications used to print were closed long ago, so the print data wasn't in the memory any more. They'd try a bunch without success and leave it for the next person, until finally one responsible person realizes that the printer was OUT OF PAPER! So that responsible individual loads a ream into the printer, and hundreds of pages all start printing from the queue left from all of the other jobs that were sent to the printer, and that's when it'd come out gibberish. So of course as they left this issue for the next guy, that person would try to print, and would run across the same issue, nothing coming out. They'd try another several times there or on other machines, and would eventually give up and go to a PC tied to another printer and get what they needed from there. Same problem, not a single page would print. So they'd hit print about 20 more times, but still.nothing! So they'd go to another computer and try to print from there to that same printer. When they tried to print, nothing would come out. We have a lot of sales staff that are generally in a hurry, so they'd have a client waiting for them, and would go to print something. This was such a bizarre thing to see this many pages being spit out with a few lines of gibberish ascii text on each of them, so every page was ruined and it wasted a lot of paper.Įventually, I found out that it wasn't anything more than user error. The printer would have run out of paper while printing all that junk out, and when they put in more paper it just kept going. We were having the same issue, where someone would go up to a printer and find a good 40 pages of gibberish that didn't make any sense. I originally thought it was a driver issue, and that may be part of it, but I found out something interesting. I've run into this same issue with some of our printers. ![]() Wireshark will most likely pick up on any traffic being received, but again I cannot just walk into his office and plop a laptop down while he is working, I have to wait for him to leave. We have many other printers set up like this on the network and this is the only one that is receiving the gibberish. ![]() My boss told me to just do it during the meeting instead of staying late. I am really leaning toward driver, but I cannot work on it while he is here. Weird, I couldn't copy and paste for some reason. From what I am looking at in spiceworks app, no.ĭoes the CEO have a unique setup (e.g. We keep it on the network because it is one of few color printers and in-case we need one, it is accessible (provided we know the IP which no one else does).ĭoes the CEO use software that other users don't? Yes, he is the only one that is mapped to it. First thing I am going to do during the meeting, which is in a couple of days from what I am told so I will have an answer for these methods by the end of Friday. I'd start with the driver update / uninstall reinstall, then work my way deeper into the problem.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |