Is there anything you lose by having it use the HP Driver longer term? Does it matter if you print from the server directly vs a client machine?
-ASB: http://XeeSM.com/AndrewBaker On Tue, Jul 6, 2010 at 2:23 PM, Shawn Everett <[email protected]> wrote: > Thanks Ben for some great ideas. > > Based on your tests, spooling is very fast. Printing is slow. > > Printing to a local port c:\test.prn is also very fast. > > Printing to an "HP Laserjet 4" printer is pretty fast. 3-4 seconds. > > The Konica is configured to use a Standard TCP/IP port. Bidirectional > support is grayed out. Print Spooling is enabled. Network port on the > Cisco switch and the Konica are set to Auto Negotiate. > > Shawn > > > On Tue, Jul 6, 2010 at 12:45 PM, Shawn Everett <[email protected]> wrote: > >> I have a Konica Minolta C353 that does not print quickly. > > > > Pause the print queue and print a job. See if it's slow to spool or > > if that goes fast. Take a look at the size of the spool file(s). > > Then unpause the queue and see how fast that goes. > > > > Create a new port on the print server, type "Local Port", and give > > it an absolute path to a file name, like "c:\test.prn". Then set the > > printer object to print to that "port". See if that goes quickly or > > slowly. > > > > I believe all the Konica printers speak PCL. Add the driver for an > > old HP printer (I'm fond of the LaserJet 4). Change the printer > > object to use that. See if the Konica prints faster that way. > > > > The above will help narrow down where the problem is. > > > >> Both the server and the Konica printer are connected to the same switch. > >> A Cisco Catalyst 2960. Both ports are set to Auto Negotiate. > > > > Use the management features of the Catalyst to look at port > > statistics (frames sent/received, errors, etc.). Compare that to port > > statistics from the Konica (I believe you can get them from one of the > > config report pages, or maybe the Konica web UI). If you see > > significant differences, or high error counts, that implies a network > > problem. > > > > You can try forcing link speed, duplex, and Ethernet flow control, > > but if you do, make sure you do so on the switch *and* the printer. > > Doing only one end is a recipe for future trouble. (And if this > > doesn't help, change everything back to auto.) > > > > Try disabling "bi-directional support" for the printer object. > > > > If Konica is shipping their own port monitor software, try changing > > to the Windows "Standard TCP/IP Port". I've had trouble with HP's > > port monitor before. > > > >> The printer vendor is claiming the printer is OK. > > > > They always do. Something's obviously wrong. Don't let them off > > the hook. If they say it's a computer/network issue, they should > > provide evidence to that effect. Don't let them get away with just > > saying "Well we've tried all the usual things and nothing worked, so > > it must be your problem." > > > > -- Ben > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
