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

Pete,

Try removing everything but your default route, which should be pointed to the gateway.

Remember; LAN console is connecting to the 'TCP short stack' that is supported in the LIC. That is not the same network nor connection point that IBM i is using, so having the console work and no other TCP/IP functions work does make some small sense.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 8/1/2012 12:25 PM, Pete Helgren wrote:

This is a lan console and I did have a couple of instances where I
couldn't connect to the i using the console when I was anywhere other
than directly plugged in but it seems to be working fine now.

I can ping the gateway but nothing beyond. I would assume that this is
a Telnet issue only if that was the only thing that didn't work. But, I
cannot connect to another server using FTP, and I cannot connect to the
i using i Navigator even though the first time I connected it DID work.
I didn't use a hard coded device name with 5250 and I have since deleted
the one device description that auto config created but it hasn't
recreated. Something changed or got "stuck" in the TCP/IP stack and
outside of the lan console, I cannot connect to hosts using TCP/IP.

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

On 8/1/2012 10:43 AM, Jack Kingsley wrote:

> Pete, is this a non hmc managed system, are you using lan console, can you
> get solid connectivity to the master console. Your not using a hard coded
> device name possibly on your TN5250 side and it is damaged.

--