× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  • Subject: Re: MIDRANGE-L Digest V4 #62
  • From: Jim Langston <jimlangston@xxxxxxxxxxxxxxxx>
  • Date: Mon, 22 Jan 2001 09:04:46 -0800
  • Organization: Pacer International

Sounds like a routing issue on your AS400.

Can you ping the NAT router from your AS/400? I suspect not.  I don't think
your AS/400 can see the IP address 63.64.65.66 (as per your example).  Your
AS/400 is on the 10.10.10.x subnet (as per your example).

Your first job is going to be to get your AS/400 to successfully ping you NAT
router.  After you can do that, things should work fine.

Regards,

Jim Langston

------------------------------------------------------------------------------------

Date: Sun, 21 Jan 2001 12:06:39 -0600
From: "Joe Pluta" <joepluta@plutabrothers.com>
Subject: RE: Overlays and page segments

This is a cross-post.  I've posted it in a couple of other places, mostly
because I am completely baffled and have no idea where to turn.

Here's the issue:

<SNIP>

And regardless of the WHY, this is how it works. So, rather than try to
figure it out, I decided to go the next step. And that next step is to try
and figure out why the AS/400 wasn't responding. And pure and simple, the
AS/400 was ignoring those packets. Here's the trace:

10.10.10.104 --> 63.64.65.66 (initial request)
63.64.65.66 --> 10.10.10.103 (request forwarded to AS/400)
(delay)
10.10.10.104 --> 63.64.65.66 (initial request)
63.64.65.66 --> 10.10.10.103 (request forwarded to AS/400)
(delay)

That goes on until the browser times out. Remember, communications work fine
on the intranet, and if I watch the communications, it's fine:

10.10.10.104 --> 10.10.10.102 (request)
10.10.10.102 --> 10.10.10.104 (response)

So, the issue seems to be that the AS/400 doesn't want to communicate with
the external address. Now, where in the world is this configured? Due to a
different problem (which I'll outline when I get a chance), I did a
RMVTCPTBL TBL(*ALL), so that should have gotten rid of any latent IP
filtering. So where else is IP filtering defined? In the HTTP configuration?
In the line description? WHERE??!?!?!?

<sigh>

Thanks a million for listening to the frustrations of a beaten man... <wry
grin>.
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.