Re: STRPASTHR using TCP/IP

[tomh@xxxxxxxxx]

A good suggestion, which I hadn't really thought of for this situation.

"Laurin Bruck" <lbruck@pmigroup.com> Sent by: owner-midrange-l@midrange.com 03/16/01 09:09 AM Please respond to MIDRANGE-L

To:        <MIDRANGE-L@midrange.com>         cc:                 Subject:        Re: STRPASTHR using TCP/IP

try using TELNET instead of STRPASTHR.  You get the same thing without having to configure APPC controllers and devices.

Laurin Bruck
Technical Infrastructure
pmi Mortgage Insurance
415-291-5329
415-393-6412(fax)
lbruck@pmigroup.com

>>> tomh@simas.com 4:56:13 AM 3/16/01 >>>
I can ping both ways.  New setup, both boxes are sitting next to each
other on the same hub, same subnet (192.168.30.11, 192.168.30.13).





"Jim Franz" <franz400@triad.rr.com>
Sent by: owner-midrange-l@midrange.com
03/15/01 03:47 PM
Please respond to MIDRANGE-L


        To:     <MIDRANGE-L@midrange.com>
        cc:
        Subject:        Re: STRPASTHR using TCP/IP



can you ping the other 400? I saw this same msg  quite a bit last week,
only to find that the router in between was  allowing
each box to send out traffic, but 1 box never  received the response to
the exchange id request. The router was  receiving
it, but not passing it to the local lan where the  400 was. We had a
simultaneous trace on both 400s, a trace at the  hub
each 400 was connected to, and an internal router  trace.
Is this a new setup, or just not working  now?
jim
----- Original Message -----
From:  tomh@simas.com
To: midrange-l@midrange.com
Sent: Thursday, March 15, 2001 7:06  PM
Subject: STRPASTHR using TCP/IP


I'm having some trouble  getting the STRPASTHR to work over TCP/IP.
 Whenever I issue the command  'STRPASHTR S1055PNX', I see the Display
Station Pass-Thru screen come up for a  few seconds, then it errors out
with: APPC failure. Failure code is  X'0009000000000000'.  F1 on the error
message tells me that 'Activate  session timed out.'  I get exactly the
same error whenever I initiate  STRPASTHR on the remote system.

I'm not sure what this is telling me, or how to go about fixing it.   Any
ideas?

Also, will I be  able to use this TCP/IP connection to SNDNETF (once I get
it working, that  is)?