MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » October 2012

RE: connection issue



fixed

What command are you suggesting to check the routing tables on the system I?
Below is the traceroute commands for both the 249 and 250 address from both
my PC and the system I.

tracert 10.50.130.249 (from my PC same subnet as system I)

Tracing route to CONNECTOR [10.50.130.249]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 10.50.101.1
2 1 ms 1 ms 1 ms 10.50.101.207
3 14 ms 14 ms 14 ms 10.0.0.2
4 14 ms 14 ms 14 ms CONNECTOR [10.50.130.249]

Trace complete.
----------------------------------------------------------------------------
--------------------------------
4 > TRACEROUTE RMTSYS('10.50.130.249') (From System I)

Probing possible routes to 10.50.130.249 using *ANY interface.
1 10.50.101.207 0.966 0.788 0.804
2 10.0.0.2 14.2 14.1 14.2
3 10.50.130.249 13.9 14.2 14.0
----------------------------------------------------------------------------
--------------------------------

tracert 10.50.130.250 (from my PC same subnet as system I)

Tracing route to LAP102611 [10.50.130.250]
over a maximum of 30 hops:

1 <1 ms <1 ms 1 ms 10.50.101.1
2 1 ms <1 ms <1 ms 10.50.101.207
3 14 ms 14 ms 14 ms 10.0.0.2
4 14 ms 14 ms 14 ms LAP102611 [10.50.130.250]

Trace complete.

----------------------------------------------------------------------------
--------------------------------
4 > traceroute '10.50.130.250' (from system I)

Probing possible routes to 10.50.130.250 using *ANY interface.
1 * * *
2 * * *
3 * * *

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Chris Bipes
Sent: Wednesday, October 17, 2012 10:54 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: connection issue

Yes the .250 reached the iSeries but the iSeries response did not make it
back to the .250 address. Can you set up two PC's, one at .250 and one at
.249 Login from the .249 and trace from the iSeries to the .250 address.
Check your routing tables on the iSeries to see if there is some special
route for the .250 or a misconfigured subnet mask.

--
Chris Bipes
Director of Information Services
CrossCheck, Inc.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Elam
Sent: Wednesday, October 17, 2012 7:42 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: connection issue

I can verify it had the 250 address because I was connected to that PC
through VNC. I changed it myself to the 249 and had to reconnect. IT's
connected to the I now under the 249. It will be a bit later, but I'll
change it back to the 250 address and try the traceroute from my PC which is
on the same subnet as the I (I should have thought of that earlier).

The 250 address does not show in netstat unless I initiate a connect from
that PC and it only shows

10.50.130.250 50665 telnet 000:00:11 SYN-received which
disappears after a short while.

I verified there is currently nothing out there now for the 250 although he
shows being connected under the 249.

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









Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact