Re: SNDPTFORD resolving to strange, unknown local IPs -- MIDRANGE-L

× 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: SNDPTFORD resolving to strange, unknown local IPs
From: Marc Rauzier <marc.rauzier@xxxxxxxxx>
Date: Fri, 31 Jul 2015 21:10:55 +0200
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Le 31/07/2015 17:00, Steinmetz, Paul a écrit :

In the TRCINT, whenever I do a SNDPTFORD, the local IP is populated with a strange, unknown local IPs, 198.74.64.168, 198.74.64.38, 198.74.64.52
Shouldn't it be one of two IPs that I have assigned to this LPAR.
Can anyone explain this?

Are you using a VPN connection ?
If yes, this may be the local IP inside the VPN tunnel.

The joblog should tell you more about this local IP.

Marc

As an Amazon Associate we earn from qualifying purchases.

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.