![]() ![]() I don't have anything running with JetDirects so it would probably be trivial to turn it off. What makes even less sense is that this was never an issue before a couple weeks ago. I was kind of disheartened to find out that my SW installation was sort of DoS'ing my print server simply by opening and closing port 9100 with the TCP description "hp-pdl-datastr" again, and again, and again.not sure why SW needs to make a million connections a second to this host that has 3 Data Max O'Neil printers that get print jobs sent out from the server on port 9100. ![]() I have went through this scenario multiple times and found this thread that seems to explain why. Brought the SW system down and no more laggy print jobs. I ran numerous packet captures on the system itself and after pouring through them I found that there was an inordinate amount of traffic coming from my SW system. There are no delays on the business machines like this (random).įound the source of the issue today.my Spice Works PC. None of my normal printers in the office do this kind of thing. One of these three printers is brand new and out of the box for only a couple of weeks. I just am baffled by how on all 3 Datamax printers that printing time is randomly delayed and its not based on what labels you print, time of day, quantity of labels, or anything logical that I can see. None of the workers told me about it until much after that but that can't be helped now. I'll be making another call to them tomorrow.Īny ideas? This just randomly started happening a couple weeks ago on a Wed. See if truetype is turned on (I doubt it would have an effect)īartender (Seagull Scientific Support) has been sort of helpful but they didn't see anything wrong with my files I sent them. Thing I thought to try on Monday (today.sigh.) Turn off Trend Micro Antivirus to rule that out. Restarting the print spooler service and the computer its running on. Restarting the printer and consequently re-initializing it's DMXNET interface Print directly to the printer bypassing windows print spooler.Ĭleaning out the directory of generated trigger files ![]() Turn off advanced printing features (advanced tab) ![]() Yellow exclamation point appears when the jobs do not print within a certain amount of time.įinally the jobs always print and the spooler is cleared out. Print job may print right away or hang for 30 seconds, sometimes 1 minute. DAT and sends the job to the Windows print spooler and starts waiting for the next file Text file is generated and dumped into a shared directory by our hosted ERP software.Ĭommander changes the extension. Jobs are sent to these three printers (Datamax O'Neil -I 4208) from this one Windows 7 computer running Bartender 10.0 This is happening on all 3 printers that are standalone with thier own IPs on the network. Bartender 10.0 monitors a directory for a trigger file with it's Commander service. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |