Re: Print to (Canon) ImageRunner from OpenVMS [force telnet]
- From: norm.raphael@xxxxxxxxx
- Date: Fri, 3 Feb 2006 11:14:36 -0500
JF Mezei <jfmezei.spamnot@xxxxxxxxxxxx> wrote on 02/02/2006 05:06:25 PM:
norm.raphael@xxxxxxxxx wrote:
Someone in our shop just swapped an HPLJ5N for a Cannon ImageRunner
xsomethingx,
and is now surprised that print from VMS (Via MULTINET_STREAM_SYMBIONT)
dies.
Sorry to say this but RTFM :-) You need to check the new printer's
manual to find out exactly what its capabilities are and compare them to
what the ols HP printer had, and look and how the HP one had been setup.
It could be that your new printer doesn't support the same port number
for the raw TCPIP connection. It isn't a standard and varies from
printer to printer.
Once you have a good idea, you can use:
Try to TELNET/PORT=xxx ip.ad.re.ss of your printer, then <CTRL>[ to
access the TELNET> prompt
$ telnet ip.ad.re.ss /port=9100
Trying... Connected.
<types <CTRL>[ here]
Terminal Read: %SYSTEM-F-BADESCAPE, syntax error in escape sequence
$
Does not give me a prompt.
and SET LINE_MODE
Then, type
hello world<CR><LF><FF>
and see if your printer ejects a page with "hello world" on it, or if
it spints out some error message etc.
.
- Follow-Ups:
- Re: Print to (Canon) ImageRunner from OpenVMS [force telnet]
- From: stuie_norris
- Re: Print to (Canon) ImageRunner from OpenVMS [force telnet]
- Prev by Date: Re: Print to (Canon) ImageRunner from OpenVMS [solved]
- Next by Date: Re: Memory allocation query
- Previous by thread: Intel hires itanium engineers - at least they are trying!
- Next by thread: Re: Print to (Canon) ImageRunner from OpenVMS [force telnet]
- Index(es):
Relevant Pages
|
