|
Thank you very much for your clear and helpful answer. I'll go to check the customer's printer and it's setup, otherwise the printer seems to work properly when a user send a spool file. Best regards, Eric Panissard IDT - Informatique de Tahiti -----Message d'origine----- De : midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de Mark.Hammett Envoyé : lundi 20 mars 2006 15:33 À : Midrange Systems Technical Discussion Objet : RE: Problem with an IP printer It is possible that the printer is rejecting the connection request. Be sure the printer's jet direct card is working properly and that it accepts the ddl/llc downloads from foreign devices on the network. Also be sure its setup for port 9100 as a valid port number. Sometimes they are set to only receive port 512 (Line print daemon - LPD). Most of these are manually adjustable at the printer, unless you have a printer management GUI and the access to the printer is secured. Some jet-direct cards allow direct - port 23 sessions to list the current option sets. The retries are generated by the 400 on a set interval (apparently to 10 minutes). Good luck! Mark Hammett TTS - ENG - ST - Tandem & AS/400 612-304-5355 -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Eric Panissard Sent: Monday, March 20, 2006 6:47 PM To: MIDRANGE-L@xxxxxxxxxxxx Subject: Problem with an IP printer Hi everybody, I have a problem with an IP printer : "TCP/IP connection to remote system 10.11.44.63 closed, reason code 2" Cause . . . . . : The TCP/IP connection to remote system 10.11.44.63 has been closed. The connection was closed for reason code 2. Full connection details for the closed connection include: - local IP address is 10.11.44.103 - local port is 5186 - remote IP address is 10.11.44.63 - remote port is 9100 Reason codes and their meanings follow: 1 = TCP connection closed due to expiration of 10 minute Close Wait timer. 2 = TCP connection closed due to R2 retry threshold being run. ... I can see this message a lot of time in the system log, every 10 minutes. For each message the local port change. What is wrong ? Eric Panissard IDT - Informatique de Tahiti
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.