Re: Operations Console Connection Problem

[Kirk Goins <kirkgoins@xxxxxxxxx>]

OK.. see if this helps...
First the Users Must Be On the T6 Port
Next Sign in to SST
8. Work with service tools user IDs and Devices
3. Select console
set Allow console recovery and console can be taken
    over by another console  . . . . . . . . .  1   1=Yes,
set Console Type to 3. Operations console(LAN)
press Enter
Select 4. Configure service tools LAN adapter
Set the IP, Mask Gateway etc.
Set the parm to allow the Internal GB port to be used
Be sure to F7 ( I think that is right ) to STORE the config.
Make sure your Console connection ( LAN Console ) is set to use device
QCONSOLE and Partition '1'
IPL and it should work






On Tue, Jul 16, 2013 at 1: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.