|
Being a PC Network manager I'm not sure that I would answer the question of TCP/IP printing problems with "just something you have to live with". We have some HP LJ4, 4+, 5, and 4000N's, some with external jet directs and some with internal. Varying amounts of memory, timeout settings vary widely (something we've played with). Some of our printers have both Novell print queues and AS400 TCP/IP based connectivity, and some are serviced directly by tcp/ip from NT workstations running jetprint, some are serviced by our RS6000's using AIX with TCP/IP. There doesn't seem to be any rhyme or reason, some of these printers are connected only to the AS400 and no other service and still do it. We have a 100MB switch that services our server farm, and then we drop into our backbone fiber switch which delivers 10MB to the racks that distribute to the workstations and printers @ 10MB, we also have a frame relay network with printers on the remote sites that do the same thing. It seems to me to be a spooling issue of some kind. We see it primarily with the larger jobs that we run..... Terry Callum -----Original Message----- From: Buck Calabro <mcalabro@commsoft.net> To: 'MIDRANGE-L@midrange.com' <MIDRANGE-L@midrange.com> Date: Tuesday, August 17, 1999 2:44 PM Subject: RE: TCP/IP printers >I haven't got a cure, but our setup is similar, and fails the same way. >I've noticed that it's most likely to hiccough when one (or more) of the >AS/400's try to spool output to it at the same time that the NT network is >printing a PC document. Our PC guys claim that this is "just something you >have to live with" on a TCP/IP network. Vague mumbling follows about an >inability of the printer to handle packets from multiple sources >simultaneously, but I'd be surprised if the printer can't send feedback >about the "rejected" packets rather than locking up. > >btw, I don't think it is related to the specific printer, as we have several >HP and IBM printers that this happens with. > >Buck Calabro > >> -----Original Message----- >> From: Kellems, Cary >> Sent: Tuesday, August 17, 1999 10:31 AM >> To: 'MIDRANGE-L@midrange.com' >> Subject: TCP/IP printers >> >> We support an environment that has an as/400 170 at v4r2 in a TCP/IP >> Ethernet LAN with various P.C., thin clients and laser printers connected. >> The problem is that the remote outques defined for the 1855 Lexmark laser >> printers intermittently stop working. >+--- >| This is the Midrange System Mailing List! >| To submit a new message, send your mail to MIDRANGE-L@midrange.com. >| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. >| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. >| Questions should be directed to the list owner/operator: david@midrange.com >+--- > > +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.