13 Jun
2013
13 Jun
'13
10:10 p.m.
On 6/4/2013 2:01 PM, Glen Slick wrote:
On Mon, Jun 3, 2013 at 11:27 PM, Jim Brain <brain
at jbrain.com> wrote:
I did not. Now I do, but I ran into another issue. It
appears telnetd
is broken on new releases of Linux (at least it is on Fedora), so I
can't test as yet.
*sigh* On every thread with folks asking about the inability to get
telnet to work on recent kernels, the first response is "Use ssh". It's
nice advice in general, but not a help when one wants to enable older
units that don't understand newer protocols. What frustrates me more
is, when reading the rest of the responses, the OP would bring this up,
and the commenters suggested upgrading the client to use ssh, basically
not reading or understanding the OP's response at all.
In any event, when telnet can work, or I break down and install an older
distro on a VM, I'll see if this works.
Thanks for the link and the help.
Jim
--
Jim Brain
brain at jbrain.com
www.jbrain.com
One of these nifty Esprit 350C terminals Cindy
was noting a week or so ago
has arrived, but I can't find a manual online anywhere. I have figured out
how to get to the config screen, but can't figure out how to get the
terminal to try to connect to an ip address.
Anyone have a manual or know how to do that?
Did you set Multiple Sessions to ON
in the F4 Comm setup menu?