Re: TCP/IP Trace -- MIDRANGE-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: TCP/IP Trace
From: Jim Oberholtzer <midrangel@xxxxxxxxxx>
Date: Mon, 27 Sep 2010 12:48:16 -0500
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/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Jeff,

The command is NSLOOKUP (you may have typed the first character wrong).

Since the inbound appears to work, I am guessing Pete might be right and there was a change in the gateway address somewhere. Check with the LAN guys to be sure what the gateway address is and then check that on your box.

Jim Oberholtzer
CEO/Chief Technical Architect
Agile Technology Architects, LLC

On 9/27/2010 12:29 PM, Jeffry A. Kennedy wrote:

Trace rout shows the correct stuff going to my LPAR and get no response on the Target Box. I couldn't find LSLOOKUP on my box (V5.4)

This mailing list archive is Copyright 1997-2026 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.