Tom,
You are 100% correct in your statement below, this is why I was at a
loss
Tom Wrote: " You can telnet from a green-screen command line on SystemA to
SystemB, but it only works when you access the command line from a
console session.
If you use a normal Client Access emulator session to access a
green-screen command line on SystemA, then the TELNET command fails
to access SystemB.
In _both_ cases, you are entering a green-screen TELNET command on a
SystemA command line.
Personally, I'm finding that hard to grasp -- the failure, that is
-- if I'm understanding correctly. Please confirm if my
understanding is correct."
Also correct in that on the SystemB console, I did a telnet to SystemBs
address just to make sure I could initially connect, and it came up in
QINTER.
Weird!!!
Pete
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Tom Liotta
Sent: Wednesday, August 12, 2009 8:49 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: Client Access Connectivity and Telenet
Pete Massiello wrote:
So, I tried to connect with Client Access to their other system, and that
worked fine. I then tried to Telnet (from my working Client Access
session)
from the working system to the new system, and that didn't work. Now, here
is where the confusion comes in. I went to the Console (LAN CONSOLE) for
each machine, and I could telnet from one system to another, and I could
telnet on the console of the new system to itself. So, telnet is working.
Pete:
Just to be certain this is clear, is the following correct?
You can telnet from a green-screen command line on SystemA to
SystemB, but it only works when you access the command line from a
console session.
If you use a normal Client Access emulator session to access a
green-screen command line on SystemA, then the TELNET command fails
to access SystemB.
In _both_ cases, you are entering a green-screen TELNET command on a
SystemA command line.
Personally, I'm finding that hard to grasp -- the failure, that is
-- if I'm understanding correctly. Please confirm if my
understanding is correct.
You also mentioned in a later post "I can telnet on the console back
to itself, and the new device does come up in QINTER."
I assume that that's done on SystemB in order to check if telnet
connections are working at all, even though you were able to telnet
from the SystemA console session to SystemB...?
Finally -- "...it actually connects to the machine, and just sits
there with that message on the bottom of the box saying it's
connected waiting on port 23 (or something like that)."
Now, that is something I've seen before.
Under at least one set of circumstances (that I haven't figured
out), the resolution was always to take the menu-bar option
Communication-> Disconnect, followed by Communication-> Connect. I
would usually wait a few seconds just in case it mattered. I never
took the time to find out what was going on on that system. It was
as if a matching virtual device was being created that was somehow
locked until a disconnect/reconnect freed it up. Just a minor
possibility.
I haven't seen that happen for quite a few months. Maybe PTFs have
fixed it in my case.
Tom Liotta
midrange.com
