I installed Option 31 today and this is what NSLOOKUP Gives me: Remote host - 172.20.1.6
Default Server: ver-server-dc.certco.local
Address: 172.16.2.150
Press ENTER to end terminal session.
Server: ver-server-dc.certco.local
Address: 172.16.2.150
Name: qb102lwxm.certco.local
Address: 172.20.1.2
Press ENTER to end terminal session.
Server: ver-server-dc.certco.local
Address: 172.16.2.150
Name: qs102lwxm.certco.local
Address: 172.20.1.6
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, September 28, 2010 8:19 AM
To: Midrange Systems Technical Discussion
Subject: Re: TCP/IP Trace
1 - He has NSLOOKUP in QSYSV5R3 and QSYSV5R2 so he probably has it installed.
2 - If he has an invalid host table entry that could explain the ping failure.
Rob Berendt
--
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 09/28/2010 03:34 AM
Subject: Re: TCP/IP Trace
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Maybe he simply doesn't have the DNS server installed?! (NSLOOKUP is
installed as part of the DNS server.)
Why is this thread so fixated on DNS. Is he having trouble with DNS
resolution? I thought he was having trouble with PING?
On 9/27/2010 7:05 PM, rob@xxxxxxxxx wrote:
Someone had a typo and instead of using SLTCMD NSLOOKUP used DLTCMD
NSLOOKUP.
NEVER USE SLTCMD! IT'S TOO PRONE TO TYPO'S!
You can type in partial commands with no action verb. ie
WRK* will bring up a list of WRK... commands.
As an Amazon Associate we earn from qualifying purchases.