Problem when printing from AS400 to Cannon 550

25 pts.
Tags:
AS/400 printing
Cannon 550
remote printers
Printer was working fine when suddenly it stopped comunicating with the A/S 400. I can ping it from the system, I can print from the network. Message ID . . . . . . : PQT3625 Severity . . . . . . . : 40 Message type . . . . . : Information Date sent . . . . . . : 04/05/10 Time sent . . . . . . : 10:39:38 Message . . . . : Connection with device HTCANON550 is being retried. Cause . . . . . : A session cannot be established with the device at RMTLOCNAME 192.168.1.19, 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. 20-39: A recoverable communications failure occurred. Recovery . . . : The connection is being retried automatically. To change the number of retries performed by PSF, you use a PSF configuration object (CRTPSFCFG or CHGPSFCFG) which must be specified in printer device description HTCANON550 using parameter USRDFNOBJ. Change the value specified More...
ASKED: April 5, 2010  3:49 PM
UPDATED: April 12, 2010  11:53 AM

Answer Wiki

Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Discuss This Question: 4  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • TomLiotta
    The first parts of interest are The error code is 22. and 22: The device did not respond to a connection request. Those indicate that the printer isn't managing to get a response back to your AS/400 when the AS/400 asks if it can send a spooled file for printing. Also -- ...using PORT 5001. That indicates that the AS/400 is trying to set up a connection to port 5001 on the printer. You can successfully ping the printer (from the AS/400, I assume); so there is a network route that runs between the AS/400 and the printer. However, there might be something like an IP filter or a firewall that has been changed to block various ports. Maybe 5001 somehow is now in a range that can no longer get through, and the AS/400 isn't allowed to receive the acknowledgement from the printer. Or perhaps the printer has had an upgrade or update that changed that communication port to a different port. Port 9001 is pretty common as a port for printers, though I don't have an example for Canon handy. You will want to verify that 5001 is appropriate for that printer and that it hasn't changed. Or perhaps the configuration on the AS/400 was updated. Maybe port 5001 isn't the port that it was using earlier. Is this printer associated with a printer device description (*DEVD) on your AS/400? Or is this a simple remote output queue? Tom
    125,585 pointsBadges:
    report
  • Patillasrc
    Tom I have a device description for the printer setup in the A/S 400. The printer uses an I/O box. The printer was working fine, lost communication with the network and when it got connected again, the only thing not working was the printing from the A/S 400. We reset the printer physically and on the system (stop OUTQ, Vary on/off... etc) and no luck.
    25 pointsBadges:
    report
  • TomLiotta
    For some basic troubleshooting, open a Windows command window and also get to an AS/400 command line. For the Windows side:
    > telnet 257.0.1.165 9988
    That is, telnet to the IP address of the printer. I used a fake address of {257.0.1.165} for an example. I also explicitly specified port 9988 as the destination port. You would substitute your printer IP address, but leave port 9988 in place. That port should be empty for your printer, so the telnet attempt should fail in just a couple seconds. Once it fails, you will have a benchmark for how long it takes to fail on your PC. If it actually begins to start a telnet session, the command window will be cleared and should appear to lock up or it will display some kind of welcome or warning text. If 9988 just happens to be a valid telnet port for that printer, try some other random port such as 8899 or 43210. With a failure benchmark available, telnet to the printer again, but specify port 5001. It should only take a few seconds to see if that port also fails or if it will make a connection and try to get a telnet session running. The point of trying two telnet connections is to ensure that (1) port 5001 is understood by the printer and (2) your PC is able to reach that port on that IP address. The differences in times between success and failure should be obvious. At the AS/400 command line:
    TELNET RMTSYS(*INTNETADR) INTNETADR('257.0.1.165') PORT(9988)
    That's essentially an attempt to cause the exact same telnet connection failure to the unopened port at the same IP address. If you changed from 9988 in the PC test, you should use that same same port from your AS/400. It is likely that a connection failure will take a minute or two on your AS/400. I expect that communications re-tries and other settings may cause recovery attempts behind the scenes by the system. You should eventually receive a message similar to "No response from remote host system within open time-out." Then try the AS/400 telnet again to port 5001. It will either timeout in exactly the same way or it will result in a very different message. The message will likely take 2-3 minutes longer if it isn't the same timeout. It may say something like "TELNET session ended. Connection closed." The series of tests should only take a few minutes. The Windows and AS/400 tests can be run concurrently. If Windows connects to port 5001 (and you know what failures look like), we're reasonably certain that port 5001 is the correct port. If it fails on 5001, then that's not the appropriate port and some printer troubleshooting is in order. The printer might not be listening on that port. If your AS/400 times out on port 5001 while Windows manages to connect, then there is an issue somewhere along the route between your AS/400 and the printer. That might commonly be an IP filter/firewall kind of problem. If the AS/400 connects to 5001 and ends up with the "session ended" message, then the route is probably okay and some other element is having trouble. That may be a long comment, perhaps with typos. The actual tests should be easy and fairly quick. Results should narrow possibilities quite a bit. If it's confusing, ask for clarification. If the tests seem okay, maybe things have cleared up and it's time to end the writer, vary the device off/on and try again -- it might simply all start working. Tom
    125,585 pointsBadges:
    report
  • Patillasrc
    Tom thanks for all your help. the problem has been resolved, the printer is comunicating with the A/S 400. I can't still figure out what happen but I switch the old I/O back and the printer started working.
    25 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following