|
Whoops....guess I didn't read it right. Sorry.....your right. In that case CHGDNSA <f4> will help you out. And it seems you can also do a STRTCPSVR *DNS or ENDTCPSVR *DNS to bounce it. And if you look on the help screen it will tell you where the debug file (if used) is located. -----Original Message----- From: rob@dekko.com [mailto:rob@dekko.com] Sent: Tuesday, November 13, 2001 1:33 PM To: midrange-l@midrange.com Subject: RE: Is DNS running on their 400? Jim, I was looking for DNS not DHCP. Big difference. Rob Berendt ================== "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin "Norbut, Jim" <Jim.Norbut@Grubb-E To: "'midrange-l@midrange.com'" <midrange-l@midrange.com> llis.com> cc: Sent by: Fax to: midrange-l-admin@mi Subject: RE: Is DNS running on their 400? drange.com 11/13/2001 02:04 PM Please respond to midrange-l Also..there's a CHGDHCPA command. And if you do an <f4> on it will say if it is set to start when TCP/IP is. If it's set to *NO.....you can change it....and then do a STRTCPSVR *DHCP to start it up again. Or do an ENDTCPSVR *DHCP to "bounce" it. HTH. Jim Norbut Systems Administrator Grubb & Ellis Company Phone (847) 753-7620 Fax (847) 753-9854 -----Original Message----- From: Fritz Hayes [mailto:fhayes@spiritone.com] Sent: Tuesday, November 13, 2001 12:52 PM To: midrange-l@midrange.com Subject: RE: Is DNS running on their 400? Also check to see that you can ping the IP address and not just the name. If you can ping the IP, then DNS or local name resolution is the problem. If no ping on the IP, then the routing entries on the AS/400 or on the core router may be the problem. If you want to check on DNS, look for the ??DNS?? jobs under the QSYSWORK subsystem. Best Regards Fritz Hayes Atwater Associates 503-636-5914 |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 _______________________________________________ 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.
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.