|
This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] Thanks. Looks like you're right. Dave -----Original Message----- From: Mark A. Manske [mailto:mmanske@minter-weisman.com] Sent: Thursday, June 20, 2002 2:10 PM To: midrange-l@midrange.com Subject: RE: IBM 3116 I am not sure about this printer, but our IP printers work with port 9100. (mostly HP some LexMark) HTH Mark -----Original Message----- From: midrange-l-admin@midrange.com [mailto:midrange-l-admin@midrange.com]On Behalf Of Leland, David Sent: Thursday, June 20, 2002 2:05 PM To: 'midrange-l@midrange.com' Subject: IBM 3116 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. -- [ Picked text/plain from multipart/alternative ] I'm trying to configure an Ethernet attached IBM 3116 (with IPDS feature). (We have other newer model IBM laser printers we've setup to print via Ethernet and they work fine). Everything seems to be okay up to the point of it actually printing. (I can ping to it.) The spool files just stay in a PND status in the outq and I get the following message in QSYSOPR: Message ID . . . . . . : PQT3625 Severity . . . . . . . : 40 Message type . . . . . : Information Date sent . . . . . . : 06/20/02 Time sent . . . . . . : 13:25:03 Message . . . . : Connection with device HTAPCHECK is being retried. Cause . . . . . : A session cannot be established with the device at RMTLOCNAME 192.168.1.29, using PORT 5001. The error code is 22. This indicates one of the following conditions: 15: The activation timer (ACTTMR) value configured for the device expired before the device was available. 22: The device did not respond to a connection request. My suspicion is the PORT should not be 5001 but I can't find anywhere in the manual or on the web as to what port it should be. Any ideas? Thanks, Dave _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com 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@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-L-request@midrange.com 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-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.