|
We have similar config for our NP17's, but we use port 5001. Were using IPDS so that may be talking through a different port. My biggest suggestion is that you have the very latest manuals for the printers. They can be found at http://www.printers.ibm.com/manuals.html
There were significant updates from the manual we received with the
printer and the one on the web. It also goes into the printer settings
required as well as /400 config.
Neil Palmer wrote:
Paul,Thanks for the reply. I was at that very web page last night but didn't
see anything I didn't already know (and it's about time they posted an
example using the *IBMPJLDRV option there isn't it !).
Figure they must have the printer configured wrong, because everything
looks OK on the AS/400 side.Would anyone using this type of setup happen to have a configuration
page from a 4317 printer itself they would be willing to fax me, so I
can compare what they did to their printer ?Neil Palmer AS/400~~~~~
NxTrend Technology - Canada ____________ ___ ~
Thornhill, Ontario, Canada |OOOOOOOOOO| ________ o|__||=
Phone: (905) 731-9000 x238 |__________|_|______|_|______)
Cell.: (416) 565-1682 x238 oo oo oo oo OOOo=o\
Fax: (905) 731-9202 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
mailto:NPalmer@NxTrend.com AS/400 The Ultimate Business Server
http://www.NxTrend.com> -----Original Message-----
> From: pault@praim.com [SMTP:pault@praim.com]
> Sent: Tuesday, April 07, 1998 2:41 PM
> To: 'midrange-l@midrange.com'
> Subject: Re: IBM 4317 Network Printer Config
>
> Neil Palmer wrote to midrange-l:
>
> Anyone have one of these configured via CRTDEVPRT using the *IBMPJLDRV
> support ?
> Have a customer on V4R1 at cum C8013410 with a device created using
> port 2501 and when you do a STRPRTWTR you get a CPF337F Remote
> device rejected an attempt by the writet to open a connection. Which
> sort of implies that the NP17 isn't listening on port 2501 like it's
> supposed to.
> Maybe they have it configured wrong ?
> As a fallback we configured Remoute Output Queue support and did
> STRRMTWTR. Report just sits forever in *SND state - although
> everytime you PING the printer it responds fine.
>
> (Of course, the HP LaserJet 5 configured same way with *HPPJLDRV
> worked
> right first time !). :-(
> Neil Palmer
>
> Dear Neil,
>
> The AS/400 *LAN device description supports a TCP/IP sockets
> connection to the target IP device. This means it tries to write to a
> particular port in the ethernet or token ring adapter in the target
> printer.
>
> When you use the remote output queue method, the AS/400 uses the
> parameter "Remote printer queue" to determine the name of the
> destination queue it will request when sending data to the target IP
> device. This means it passes the printable data to a pre-defined
> internal print queue that exists in the ethernet or token ring adapter
> that is installed in the target printer.
>
> Since both of these methods have failed, it sounds like the network
> interface card in the IBM printer may not be set to its default
> configuration.
>
> You might find some useful information at the IBM System Printer Co.
> website listed below.
> http://www.printers.ibm.com/pbin-psc/faqhuic?A+4317
>
> HTH
>
> /Paul
> --
> Paul Tykodi, Technical Director E-mail:
> pault@praim.com
> Praim Inc. Tel: 603-431-0606
> 140 Congress St., #2 Fax: 603-436-6432
> Portsmouth, NH 03801-4019
>
>
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@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-2024 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.