× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Needed to go in with 5250e  to SST and deactivate and then activate console.

Now working.

Thx,

Jerry

On 2/29/2024 11:52 AM, Jerry Draper wrote:
We are connecting with ACS (version as shown below) and definitely NOT simple 5250e telnet client.

We followed items 1-4 on your list below.

Using ACS we can connect to Integrated File System, 5250e Telnet, and file transfer all of which are on 192.168.45.13.

The ACS console locater does NOT find a console which is at 192.168.45.15

We are thinking that something is awry with that port.  It's like the console is NOT on the network.

Jerry


On 2/28/2024 5:24 PM, Evan Harris wrote:
Hi Jerry

you don't say how you are trying to connect... are you by any chance just
trying to use a 5250 telnet connection to the LAN Console address ?

On the off chance that is the issue:
- on the Solutions menu click System Configurations
- add a configuration or edit the appropriate configuration
- click the console tab
- add the IP address of the service tools adapter into the service host name
- once that is done the 5250 console link should get you a console

You could also try the locate console button on the systems screen if you
know the ip address or range (this has helped me a few times)

How do you know the pc you are using can reach the service tools address..
assigning an ip address and connecting via a direct cable can be helpful as
a last resort
-


On Thu, Feb 29, 2024 at 11:34 AM Jerry Draper<midrangel@xxxxxxxxxxxxx>
wrote:

We have a  Express 720 (8202-E4D) that is not connecting to the LAN
console using ACS

IBM i Access Client Solutions
(64-bit)
Version: 1.1.9.4
Build id: 3480
2023-11-28 10:16:55

We verified the address and resource in SST and confirmed cable is in
the correct port.

We cannot ping the console interface but we can telnet into the machine
no problem.

We tried from two different PC's to no avail and swapped ethernet cables.

Yes, it used to work fine.  What are we missing?

Thanks,

Jerry


--
Jerry Draper, Trilobyte Software Systems, since 1976
IBM I, Network, and Connectivity Specialists, LAN/WAN/VPN
Representing WinTronix, Synapse, HiT, and others .....
(415) 457-3431 .www.trilosoft.com
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email:MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit:https://lists.midrange.com/mailman/listinfo/midrange-l
or email:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
athttps://archive.midrange.com/midrange-l.

Please contactsupport@xxxxxxxxxxxxxxxxxxxx  for any subscription related
questions.





As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.