|
Jeff, Wish I could be of more help, but I don't actually have anything using IPP yet. Have you checked recommend PTFs? http://www-912.ibm.com/s_dir/slkbase.NSF/10aab18fc58a76b486256838006ae1e0/1c c2223a51d8dfda86256a5b005b098c?OpenDocument If you've got all of those and have a support line contract, I'd go ahead and call IBM. Sorry, let us know what results you end up with. Charles > -----Original Message----- > From: Jeff Crosby [mailto:jlcrosby@xxxxxxxxxxxxxxxx] > Sent: Friday, February 20, 2004 10:53 AM > To: 'Midrange Systems Technical Discussion' > Subject: RE: Okidata w/jet direct > > > > I did a little more checking. The HP 500x and 300x series > > both support IPP while the HP 170x series does not. > > Bear with me, here's the latest: > > I got an HP 500x print server and hooked it up. Installed > latest firmware. > Attached an Okidata ML380 to it. I can install and print to > it just fine > from my W2K machine. > > This printer emulates an Epson 2550 by default. I set up an iSeries > lan-attached device (not a remote outq) to test. Made it > *IBMIPPDRV for now > with manufacturer type/model *EPLQ2550. > > When I send an iSeries print job it doesn't work. I get: > > POST / HTTP/1.1 > Host: 192.168.0.103 > Connection: close > Content-Type: application/ipp > Content-Length: 199 > Accept: application/ipp > User-Agent: OS400 > > After that it slowly turns to garbage, then the printer > writer ends. The > joblog has: > > CPD338D Diagnostic 40 02/20/04 > 10:23:20.281600 QWPIPPDR > QSYS *STMT QWPIPPDR QSYS *STMT > >From module . . . . . . . . : WPIPPDR > >From procedure . . . . . . : Recv_Data > Statement . . . . . . . . . : 63 > To module . . . . . . . . . : WPIPPDR > To procedure . . . . . . . : _C_pep > Statement . . . . . . . . . : *N > Message . . . . : An error occurred while receiving data. > Cause . . . . . : A communications error occurred while > receiving data > from > remote device at RMTLOCNAME 192.168.0.103. The error code is > 2329600. This > error can also occur when the system attempts to print to the > remote device > after it has been powered off and on while the printer writer remains > active. Recovery . . . : Try the request again. If the > problem continues, > end TCP/IP using the End TCP/IP (ENDTCP) command, start > TCP/IP by using the > Start TCP/IP (STRTCP) command, and then try the request again. > > Question: Do you feel confident that this is far enough along I will > eventually get it to work with a new Okidata 491? I was only > trying the > ML380 because I had it lying around. It's really old and I > have no clue as > to how that is affecting things. There are so many options > and settings to > printer setup on an iSeries that if this is going to be a > time consuming > test and test and test, I'd just as leave do it with the OKI > 491 that I > would ultimately use. > > I just want to hear someone else say they feel confident that > this would > ultimately work before I buy this printer. > > Thanks. > > -- > Jeff Crosby > Dilgard Frozen Foods, Inc. > P.O. Box 13369 > Ft. Wayne, IN 46868-3369 > 260-422-7531 > > The opinions expressed are my own and not necessarily the > opinion of my > company. Unless I say so. > > > > -----Original Message----- > > From: midrange-l-bounces@xxxxxxxxxxxx > > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Crosby > > Sent: Thursday, February 19, 2004 8:28 AM > > To: 'Midrange Systems Technical Discussion' > > Subject: RE: Okidata w/jet direct > > > > > > This used to be a 391 but it fried and was replaced by a 420. > > > > Connected to a HP 500x > > > > > > The 500x supports up to 3 attached printers while the 300x > supports 1. > > > > -- > > Jeff Crosby > > Dilgard Frozen Foods, Inc. > > P.O. Box 13369 > > Ft. Wayne, IN 46868-3369 > > 260-422-7531 > > > > The opinions expressed are my own and not necessarily the > > opinion of my company. Unless I say so. > > > > > > > > _______________________________________________ > > This is the Midrange Systems Technical Discussion > > (MIDRANGE-L) mailing list To post a message email: > > MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change > > list options, > > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > > or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, > > please take a moment to review the archives at > > http://archive.midrange.com/midrange-l. > > > > > > > > _______________________________________________ > This is the Midrange Systems Technical Discussion > (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. >
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.