Re: Is DNS running on their 400?

We are running V4R5 ... from CFGTCP take option 20 (Configure TCP/IP
Applications), from that menu roll or page down,
you should see option 18 (Change DNS Attributes)...  If you don't find job
QTOBDNS running under QSYSWRK subsystem then the DNS server is not started.



----- Original Message -----
From: <rob@dekko.com>
To: <midrange-l@midrange.com>
Sent: Tuesday, November 13, 2001 2:38 PM
Subject: Re: Is DNS running on their 400?


>
> There is no option 18 under the ancient V4R5 code.  There have no jobs
> named QTOBDNS.  But again - is that limited to V5R1?
>
> Rob Berendt
>
> ==================
> "They that can give up essential liberty to obtain a little temporary
> safety deserve neither liberty nor safety."
> Benjamin Franklin
>
>
>
>                     "Ron Lang"
>                     <rlang@ruger.com>         To:
<midrange-l@midrange.com>
>                     Sent by:                  cc:
>                     midrange-l-admin@mi       Fax to:
>                     drange.com                Subject:     Re: Is DNS
running on their 400?
>
>
>                     11/13/2001 02:18 PM
>                     Please respond to
>                     midrange-l
>
>
>
>
>
>
> A couple things that you might try  on remote customer ...
>
> On CFGTCP take option 20 then take option 18.   This will show if the
> server
> is auto started and you can also get info from the Debug level (if not
> 0)...
> I have never used so I do not know what info it will give you.  Also, do
> WRKACTJOB, under subsystem QSYSWRK there should be a job QTOBDNS running.
> They may need to start the DNS server.
>
> Hope that this helps...
>
> Ron
> ----- Original Message -----
> From: <rob@dekko.com>
> To: <midrange-l@midrange.com>
> Sent: Tuesday, November 13, 2001 1:27 PM
> Subject: Is DNS running on their 400?
>
>
> >
> > Situation:  Remote customer 400 of which we have access.  Stopped
sending
> > us data and email.  All strictly TCPIP over the Internet.  We can access
> > them using telnet, by their name.  However, from their command line we
> > cannot ping any outside locations, like nra.org.  Message is unknown
> host.
> > I noticed that their address for their DNS under CFGTCP-12 is the same
as
> > their interface under CFGTCP-1.  I question as to whether or not they
are
> > really running DNS on their 400 or if someone's been messing.  They are
> > running V4R5.  I am trying to set up to talk to them before I make the
> > call.  I can't access their system remotely using Op's Nav.  Is there a
> > green screen way of seeing if DNS is configured to run on their 400,
like
> > perhaps netstat, wrkactjob, or whatever?
> >
> > Rob Berendt
> >
> > ==================
> > "They that can give up essential liberty to obtain a little temporary
> > safety deserve neither liberty nor safety."
> > Benjamin Franklin
> >
> > _______________________________________________
> > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> > To post a message email: MIDRANGE-L@midrange.com
> > To subscribe, unsubscribe, or change list options,
> > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> > or email: MIDRANGE-L-request@midrange.com
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
>
>
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
> or email: MIDRANGE-L-request@midrange.com
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.