Yes, the necessary and sufficient capabilities to run ping.net.sys from a
session are IA, NA and NM. [Which is silly since anyone can run ping from
their PC. Plus, giving out NA and NM is VERY dangerous.]

Interestingly, nslookup (/BIND/PUB/bin/nslookup), which came to us thanks to
Mark Bixby's port of BIND and which is on 6.0 and above systems, has a
necessary and sufficient capabilities list of just IA and PH. This makes
much more sense.

Does anyone know of any technical reason why a user of ping on MPE/iX must
have NA and NM?

Combining nslookup with ping.net.sys in a relatively simple command file
gives you a ping utility that is every bit as fast and more versatile then
the ping that comes with WinNT. [The ping module of nettool does name
resolution, but it is excruciatingly slow. nslookup is very fast and
efficient.]

John

> -----Original Message-----
> From: Shawn Duffy [mailto:[log in to unmask]]
> Sent: Thursday, October 26, 2000 6:50 AM
> To: [log in to unmask]
> Subject: Re: [HP3000-L] PING.NET.SYS
>
>
> I contacted the HP Response Center a couple weeks ago with
> this exact question.
> I was told that NA and NM were required. Hope this helps.
>
> Shawn Duffy
> Provider HealthNet Services
>
> ____________________Reply Separator____________________
> Subject:    PING.NET.SYS
> Author: Wolfgang Strobl <[log in to unmask]>
> Date:       10/26/00 8:42 AM
>
> has anyone an Idea, which Capabilities are needed to run
> PING.NET.SYS. Their is no documentiation on the CD.
>
> If I run it under an Non-Sysaccount-User that has the following
> Capabilities AM,AL,GL,OP,ND,SF,BA,IA,PM,MR,DS,PH the neither the
> PING-Input-Screen nor an Error-Message appears.
>
> Help is welcome.
>
> Regards,
> Wolfgang Strobl
> [log in to unmask]
>