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

If you created a connection, even just once, then the routing is most
likely fine since a successful connection indicates that the route was
traversed in both directions.

Have you checked the system values related to devices? See
http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/topic/rzakz/rzakzdevicesoverview.htmwith
attention on QAUTOCFG and QAUTOVRT.


On Wed, Aug 1, 2012 at 6:14 AM, Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx

wrote:

Pete;

Yesterday I had very similar difficulties at a client. Differences are
this is P6, HMC console, and LPARs but I don't think that's a factor
since you were able to get in with the LAN console. Routing on this box
is correct, although that could be a problem for you as well. We just
restarted the telnet server and it started working without having to
recreate anything. We have experienced similar problems with the SMTP
server as well. I'm starting to wonder if there is a fault somewhere
deep in TCP. We have a PMR open and are working it actively however
every time we try to trace it, we do not see a failure.

We were planning on getting all the most recent PTFs/Groups etc hoping
there was a problem that was fixed but it seems you have debunked that
theory. That system is not that far back in PTFs anyway but it never
hurts to hope...

In the mean time try a telnet server restart. Have you tried NETSTAT
to see if the route is valid?

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 8/1/2012 2:10 AM, Pete Helgren wrote:

Got a brand spanking new 720 up and running. Initially I had the
operations console connected, I configured an Ethernet line and
connected via telnet (5250). I also connected via IBM i navigator. I
even FTP'd a file from the old iSeries over to the new 720 (both running
IBM i 7.1) All seemed well. I disconnected the telnet session after
signing off. Ended the navigator session and moved on to other things.
I went back to check on something but the 5250 session wouldn't
connect. So I started ops console and check for errors and saw none.
After playing around with various settings, routings, and decided to
completely retrace my steps. I deleted the all the configuration
objects. Started from scratch.

I created new Ethernet line description, added the interface, added the
default route, varied on the line, started the interface and then
started the telnet server. Still, no joy. I downloaded the TCP/IP
group PTF and applied it. No change.

The first time I connected with telnet, a new virtual device description
was created. I deleted it to see if it would be recreated. It has
not. So I am not sure just where the issue is. I can ping the default
gateway but I can't reach any other device on the subnet.

I'm stumped. It seems like a routing issue but......

I*think* I saw something similar recently on this list but the archives
are offline at the moment. Any ideas where to look next?

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

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