Re: Cannot connect with Telnet client, other TCP/IP clients

[Pete Helgren <pete@xxxxxxxxxx>]

So here is the solution in case somebody runs into this (but this is a 
such a corner case I doubt it'll come up).

There WAS a warning in the QTCPWRK job that I  chose to ponder and then 
ignore because I *thought* I knew what the cause was.  The warning was:

WARNING: Host 420000247EDB also using IP 192.168.200.210.

Now a couple of things led me down the wrong path here.  First, the MAC 
address is clearly one from IBM i.  And I assumed (wrongly) that the MAC 
address must have been local to the new 720 since it seemed like TCP/IP 
wasn't getting off the box.  As it turned out the MAC address was from 
an adapter on the old 520 and it was a virtual adapter that wasn't even 
on my radar because it was part of an old Linux partition that I had 
long since deleted (yet, the line was varied on and active so......)

Interesting note: The interface associated with the adapter was 
192.168.200.220 (which is why the warning on the 720 didn't register).  
However, it was subnetted to 255.255.255.240  (I think) and I think that 
was the issue (although it has been 15 years since I sat in TCP/IP 
class...).  In any case, I was told to run this in STRSQL:

select internet, lind, cnntype  from qusrsys/qatocifc

And the virtual adapter was listed as a type 'p' and was apparently the 
culprit.

Once we varied off the adapter (which I subsequently deleted), stopped 
and restarted the interface and then cleared the arp cache on my PC, 
BANG ZOOM! I connected immediately.....

Self inflicted wounds are always the most painful.....

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

On 8/1/2012 12:06 PM, Jim Oberholtzer wrote:
> CFGTCP; option 2.
>
> You may have to stop the IP interfaces using option 1 (and very
> potentially remove all of them too)  before removing the routes.  The
> *DIRECT routes have always gone away when I delete the line
> configuration.  (copy it to source first to recover it easily)
>
> While Larry and others are much better at networking than I, when
> configuring IP on IBM i I always get just the base IP address and route
> correct first, then start adding the other stuff that's needed for all
> the communications types, adding each one at a time to pinpoint when
> something goes wrong.
>
>
> Jim Oberholtzer
> Chief Technical Architect
> Agile Technology Architects