Re: Operations Console Connection Problem -- MIDRANGE-L

You are mixing console types.
You currently have serial "direct attach" console configured.
You must go into DST from the current console and configure the LAN
adapter, IP address, Console device and etc for Lan Console. Finally,
change the console type and it should work. It's not really complicated but
it can be bothersome.
Ignore the "ip adress" that was on the serial connection, that is NOT a lan
connection. Its a weird TCP over Serial thing, so weird that it was
deprecated on windows vista and you cant use it anymore.
If you still have the direct attach console working, do a B-M type IPL and
change the console from there. IBM's infocenter has lots of info on how to
set up LAN Console when another one is working. Make sure you either have a
second network card on the pc that will be lan console or you select an IP
address from your local lan's pool (no dhcp AFAIK).

Best Regards

On Tue, Jul 16, 2013 at 5:19 PM, Jeff Glenn <j.glenn@xxxxxxxxx> wrote:

Hello,

I'm hoping you can help with a connection to an older iSeries. We have a
9406-520 that was decommissioned around 2010. I believe it's at V5R3. We're
now trying to start using it for non-production work such as training and
testing. It's not on maintenance. It's now up but we can't connect to it.
It's on a separate network from everything else to keep it isolated. We
can't get an Operations Console session to start and we can't get a
successful ping. It is directly connected from T5 to the PC running
Operations Console. A serial connection was used previously when it was the
production box and the serial cable is still in place connecting it to the
same PC running Ops Console. The PC running Ops Console connects just fine
to our production box as a LAN connection. A consultant is helping with
this - he previously came in to verify it was up and running and changed
the IP address for us (a console session was not part of the original
request), but he is now in a different loca
tion and we're playing a bit of phone tag.

Some things we've tried:
-Created a new LAN connection in Operations Console using the IP address
as the system name. Sticks in a "Connecting console / Connecting remote
control panel" status.
-Swapped the cable from T5 to T6 and back.
-Tried changing the IP address from the existing old connection in Ops
Console to match the new IP address. This connection has a check box for
Use console (COM1) with an IP address next to it. Creating a new connection
does not give this option.
-Disconnected the serial cable from the PC.
-Telnet from the PC.
-Changed to manual mode and tried 65+21 functions from the control panel
expecting SRC codes to be echoed back, but never received SRC codes. Must
not have done this correctly.

Here's the log from one of the cwbping attempts:

IBM System i Access for Windows
Version 6 Release 1 Level 0
Connection Verification Program
(C) Copyright IBM Corporation and Others 1984, 2008. All rights reserved.
U.S. Government Users Restricted Rights - Use, duplication or disclosure
restricted by GSA ADP Schedule Contract with IBM Corp.
Licensed Materials - Property of IBM

To cancel the CWBPING request, press CTRL-C or CTRL-BREAK
I - Verifying connection to system 10.xx.x.x...

I - Connection requested for server application: as-central
I - CWBCO1009 - Communications provider: WinSock 2.0
I - System name is a valid address
I - CWBCO1040 - Using remote port lookup mode: Always use remote server
mapper
I - CWBCO1044 - Remote address 10.xx.x.x
I - Attempting to establish a connection...
E - CWBCO1003 - Sockets error, function connect() returned 10060
E - CWBCO1048 - A firewall blockage or time-out occurred trying to connect
to the System i
E - CWBCO1006 - Unable to connect to server mapper
E - CWBCO1011 - Remote port could not be resolved
E - CWBCO1008 - Unable to connect to server application Central Client,
returned 10060

I - Connection requested for server application: as-file
I - CWBCO1009 - Communications provider: WinSock 2.0
I - System name is a valid address
I - CWBCO1040 - Using remote port lookup mode: Always use remote server
mapper
I - CWBCO1044 - Remote address 10.xx.x.x
I - Attempting to establish a connection...
E - CWBCO1003 - Sockets error, function connect() returned 10060
E - CWBCO1048 - A firewall blockage or time-out occurred trying to connect
to the System i
E - CWBCO1006 - Unable to connect to server mapper
E - CWBCO1011 - Remote port could not be resolved
E - CWBCO1008 - Unable to connect to server application Network File,
returned 10060

I - Connection requested for server application: as-netprt
I - CWBCO1009 - Communications provider: WinSock 2.0
I - System name is a valid address
I - CWBCO1040 - Using remote port lookup mode: Always use remote server
mapper
I - CWBCO1044 - Remote address 10.xx.x.x
I - Attempting to establish a connection...
E - CWBCO1003 - Sockets error, function connect() returned 10060
E - CWBCO1048 - A firewall blockage or time-out occurred trying to connect
to the System i
E - CWBCO1006 - Unable to connect to server mapper
E - CWBCO1011 - Remote port could not be resolved
E - CWBCO1008 - Unable to connect to server application Network Print,
returned 10060

I - Connection requested for server application: as-database
I - CWBCO1009 - Communications provider: WinSock 2.0
I - System name is a valid address
I - CWBCO1040 - Using remote port lookup mode: Always use remote server
mapper
I - CWBCO1044 - Remote address 10.xx.x.x
I - Attempting to establish a connection...
E - CWBCO1003 - Sockets error, function connect() returned 10060
E - CWBCO1048 - A firewall blockage or time-out occurred trying to connect
to the System i
E - CWBCO1006 - Unable to connect to server mapper
E - CWBCO1011 - Remote port could not be resolved
E - CWBCO1008 - Unable to connect to server application Data Access,
returned 10060

I - Connection requested for server application: as-dtaq
I - CWBCO1009 - Communications provider: WinSock 2.0
I - System name is a valid address
I - CWBCO1040 - Using remote port lookup mode: Always use remote server
mapper
I - CWBCO1044 - Remote address 10.xx.x.x
I - Attempting to establish a connection...
E - CWBCO1003 - Sockets error, function connect() returned 10060
E - CWBCO1048 - A firewall blockage or time-out occurred trying to connect
to the System i
E - CWBCO1006 - Unable to connect to server mapper
E - CWBCO1011 - Remote port could not be resolved
E - CWBCO1008 - Unable to connect to server application Data Queues,
returned 10060

I - Connection requested for server application: as-rmtcmd
I - CWBCO1009 - Communications provider: WinSock 2.0
I - System name is a valid address
I - CWBCO1040 - Using remote port lookup mode: Always use remote server
mapper
I - CWBCO1044 - Remote address 10.xx.x.x
I - Attempting to establish a connection...
E - CWBCO1003 - Sockets error, function connect() returned 10060
E - CWBCO1048 - A firewall blockage or time-out occurred trying to connect
to the System i
E - CWBCO1006 - Unable to connect to server mapper
E - CWBCO1011 - Remote port could not be resolved
E - CWBCO1008 - Unable to connect to server application Remote Command,
returned 10060

I - Connection requested for server application: as-signon
I - CWBCO1009 - Communications provider: WinSock 2.0
I - System name is a valid address
I - CWBCO1040 - Using remote port lookup mode: Always use remote server
mapper
I - CWBCO1044 - Remote address 10.xx.x.x
I - Attempting to establish a connection...
E - CWBCO1003 - Sockets error, function connect() returned 10060
E - CWBCO1048 - A firewall blockage or time-out occurred trying to connect
to the System i
E - CWBCO1006 - Unable to connect to server mapper
E - CWBCO1011 - Remote port could not be resolved
E - CWBCO1008 - Unable to connect to server application Security, returned
10060

I - Connection requested for server application: drda
I - CWBCO1009 - Communications provider: WinSock 2.0
I - System name is a valid address
I - CWBCO1040 - Using remote port lookup mode: Always use remote server
mapper
I - CWBCO1044 - Remote address 10.xx.x.x
I - Attempting to establish a connection...
E - CWBCO1003 - Sockets error, function connect() returned 10060
E - CWBCO1048 - A firewall blockage or time-out occurred trying to connect
to the System i
E - CWBCO1006 - Unable to connect to server mapper
E - CWBCO1011 - Remote port could not be resolved
E - CWBCO1008 - Unable to connect to server application DDM, returned 10060

I - Connection requested for server application: telnet
I - CWBCO1009 - Communications provider: WinSock 2.0
I - System name is a valid address
I - CWBCO1040 - Using remote port lookup mode: Always use remote server
mapper
I - CWBCO1044 - Remote address 10.xx.x.x
I - Attempting to establish a connection...
E - CWBCO1003 - Sockets error, function connect() returned 10060
E - CWBCO1048 - A firewall blockage or time-out occurred trying to connect
to the System i
E - CWBCO1006 - Unable to connect to server mapper
E - CWBCO1011 - Remote port could not be resolved
E - CWBCO1008 - Unable to connect to server application Telnet, returned
10060

E - CWBCO1016 - Connection verify to system 10.xx.x.x failed

Thanks,
Jeff
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.