RE: Can't Connect

I had the same thought, Pete. I'm not a hardware guy (hell I'm starting to
doubt that I'm a software guy), but I went into the "closet" where the comm.
equipment resides. There are wires everywhere, but all of the lights on the
Comcast modem and our router were flashing (and still are), and I didn't see
any loose, unconnected Ethernet cables.

As I said earlier, things mysteriously began to work after I did a Retry on
the "Ethernet line failed" message for the sixth time today.

Jerry C. Adams
IBM i Programmer/Analyst
About the only problem with success is that it does not teach you how to
deal with failure. -Tommy Lasorda
--
A&K Wholesale
Murfreesboro, TN
615-867-5070


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Pete Helgren
Sent: Monday, February 13, 2012 12:59 PM
To: Midrange Systems Technical Discussion
Subject: Re: Can't Connect

The ONLY time I get that error is when the physical connection between my i
and the switch is broken.

Bad cable or failing switch between you and the network would be my guess.

Pete Helgren
Value Added Software, Inc
www.petesworkshop.com
GIAC Secure Software Programmer-Java


On 2/13/2012 8:21 AM, Jerry C. Adams wrote:

On V5R1 and DNS sitting at Comcast.net.



All day Friday we lost internet connection. Web browsing and email
were not existent; connections to the System i via iSeries Access for
Windows were down. Only twinax devices (displays and printers) worked.



This morning, when I came in there was an error message (CPA58EE -
Line Ethernet failed) to which I replied 'R'. iSeries Access could
then connect, and I was working fine from my PC. Remote locations could

signon.

Comcast came out this morning to work on it. Now browsing and email
work, but iSeries Access connections (local and remote) do not. In
WRKCFGSTS *LIN the Ethernet is showing "Active".



I have since gotten the CPA58EE error three more times, and replied
'R'; once that failed but the next retry seemed to take



Obviously I'm missing something else, but what?



In Work with TCP Interfaces and Routes only the specific IP address
(plus the Loopback) are defined. For local connection could I add a
10.0.0.xxx IP address and change the iSeries Access connections to use
that address rather than the 173.xx.xx.xx address? This would not
help the remote locations, of course, so I'm still missing something.



Thanks.



Jerry C. Adams

IBM i Programmer/Analyst

--

A&K Wholesale

Murfreesboro, TN

615-867-5070

--
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.