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


  1.  Home
  2. MIDRANGE-L
  3. November 2000

TCP Problem

  • Subject: TCP Problem
  • From: Jon.Paris@xxxxxx
  • Date: Mon, 13 Nov 2000 19:37:15 -0500
 

 >> You need to setup up a mapping of one of your "external" (official)
addresses to match the desired "internal" (private) addresses.

Thanks for the web references Philipp, they will come in handy.  As to the
rest of your note I'm afraid it doesn't answer the problem as what you
describe above is exactly what we have configured.  One of our "real"
external addresses is mapped to one of our 192.168.... internal addresses.
When the machine outside the wall attempts to ping any of the other PCs
(also having 192 series IPs) it works just fine - only the AS/400 refuses
to respond.

+---
| 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-Ups:
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.