Okay. Had this happen once. IBM support said to do a CWBPING from a PC command line. Mine looks like this.
To cancel the CWBPING request, press CTRL-C or CTRL-BREAK
I - Verifying connection to system 192.168.1.10...
I - Successfully connected to server application: Central Client
I - Successfully connected to server application: Network File
I - Successfully connected to server application: Network Print
I - Successfully connected to server application: Data Access
I - Successfully connected to server application: Data Queues
I - Successfully connected to server application: Remote Command
I - Successfully connected to server application: Security
I - Successfully connected to server application: DDM
I - Successfully connected to server application: Telnet
I - Connection verified to system 192.168.1.10
Based upon these successful connections, Rochester said it had to be a network issue. And it was (someone connected two ports on the same switch together, creating a loop).
I would concentrate on the network.
Bryan Burns
iSeries Specialist
ECHO, Incorporated
Lake Zurich, Illinois
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Massiello
Sent: Wednesday, August 12, 2009 9:59 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Client Access Connectivity and Telnet
I thought the same thing last night, and I tried that as well, and nothing.
Pete
Pete Massiello
iTech Solutions
http://www.itechsol.com
Add iTech on Facebook:
http://www.facebook.com/group.php?gid=126431824120
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Burns, Bryan
Sent: Wednesday, August 12, 2009 10:42 AM
To: Midrange Systems Technical Discussion
Subject: RE: Client Access Connectivity and Telenet
Try STRHOSTSVR *ALL.
Bryan Burns
iSeries Specialist
ECHO, Incorporated
Lake Zurich, Illinois
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Massiello
Sent: Wednesday, August 12, 2009 7:25 AM
To: 'Midrange Systems Technical Discussion'
Subject: Client Access Connectivity and Telenet
I was at a customer last night that had two systems. I upgraded one of their
systems last night from a 9406-520 to a Power6 520. The old system didn't
have client access. I installed Client Access and the license keys on the
new system. I started Host Servers for *SIGNON and *SRVMAP. I started TCP
Server *TELNET, but I still couldn't connect via Client Access.
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.
I made sure QAUTOVRT was set high enough to create virtual devices, and I
had QAUTOCFG on. Telnet is working from above, but I can't telnet from
another system's client access session to the new system, and I can't
connect using Client Access to the new system.
The system is running V6R1 with the latest cumulative package. I am running
Client Access 6.1 on my pc. Anyone seen this before? Why would telnet work
from the other systems Console but not from another systems client access
session? I am not using named devices on the Client Access sessions.
Pete
Pete Massiello
iTech Solutions
http://www.itechsol.com
midrange.com
