Printing in Telnet session.

English Applications
#1

Hi,

                          I have two opensuse desktops A & B each with same configuration i.e OpenSUSE 12.3 and telnet server installed on 1 machine A.Now I have connected a printer to B and I will connect to machine A through telnet client.Is there a way to take print in the telnet session without adding the printer in machine A i.e in the telnet server machine.

thanks in advance

#2

Should be able to use lp command check out man lp for detailed info

#3

When B has the printer, you can print when you are loged in in B (telnet or direct).

When you are loged in in A, regardless if you did that from the console or by telnet from B, and A has no printer, you can not print from any session loged in in A.

#4

Actually I don’t want to add a printer in telnet server machine.I want to connect to telnet server and print to local printer.In other words I need printer redirection to telnet session.
If I use lp or lpr the printer should be added in telnet server otherwise it returns an error “lp:error no default destination available”

#5

So would you mean to say that printing redirection to telnet session is not possible.

#6

You should be able to run lp on the remote machine to print stuff from the remote machine.

But if you want to print on the remote from a local source then no telnet will not work.

You need to setup remote printing which is not telnet. Should be able to do that from yast printers. If the two machines are not on a local net you can still do it but you may have to open some ports to the Internet

#7

On 2013-08-17 21:06, nishanth9042 wrote:
>
> gogalthorp;2579847 Wrote:
>> Should be able to use lp command check out man lp for detailed info
>
> Actually I don’t want to add a printer in telnet server machine.I want
> to connect to telnet server and print to local printer.In other words I
> need printer redirection to telnet session.

I never heard of such a feature.

You either set the telnet server to print via any other machine, local
or remote (does not need to be the default printer), or print to file,
download the file to client machine, and print it locally.

By the way, I really hope you are not using telnet over Internet: the
password travels in clear, as well as all the data. Use ssh instead.

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

#8

Exactly…

#9

This was many moons ago, I worked for a billing company that had two version of billing software. 1. sofrrun locally on a SCO box at the customer site, or 2. for people who don’t want the expense of a SCO Unix box, dial into the HP9000 box at our office, using dumb-terminal or hyperterm with Windows.

The people with the hosted solution wanted to print locally. We found a solution by embedding ASCII code in the billing software!

if my memory serves me right, send the following ASCII code to start/stop local printing.

DC1 0x11, start local printing
DC3 0x13, stop local printing

We got it to work on Win98 and dumb terminal at the time. Not sure if it’ll work on recent version of any OS. Have fun!

#10

First,
Carlos’ observation should not be overlooked. Even in a “protected network” there is probably no good reason to deploy a telnet server for anything more than a very temporary exercise. Telnet clients continue to be used for a variety of reasons, but telnet servers should be replaced with ssh in general.

As for what the the OP is requesting, regardless of the technology you should be able to break down the objective into its most basic possibilities…

  • You can proxy the request. This means that the actual request to the service (printer) is executed by the proxy instead of the original requestor. When this is configured, the originator only needs to initiate some trigger for the actual task to be kicked off on the proxy. Note that depending on the configuration, it may or may not be possible to pass special configuration to the service (printer) like printing a specific file. An example of this is knocking
  • You can re-direct. This means that the initial connection does not terminate at target machine, but is passed to a new target. You can do stuff like this at the networking level, eg vlan or other tunnel, ip translation using something like iptables, or at the application level or some other way. The initial target does nothing more than pass the command on. In this case, some apps like Telnet probably can’t do the re-direction by itself but any of many other apps can do this kind of redirection if the telnet session (in this case) can be consumed and modified, then resent.

So, to the OP,
If you break down your objective and problem this way it might provide some clarity about how to go about designing your solution, and this of course is aside from why you would even need to re-direct instead of simply configuring a direct connection to the network service.

TSU

#11

On 2014-11-23 01:26, tsu2 wrote:

> So, to the OP,

He posted 17-Aug-2013 :wink:

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)