Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!mailrus!ncar!boulder!stan!dancer!imp From: imp@dancer.Solbourne.COM (Warner Losh) Newsgroups: comp.protocols.tcp-ip Subject: Re: Wollongong TCP/IP ping question, VMS Message-ID: <1990Jul9.210637.4761@Solbourne.COM> Date: 9 Jul 90 21:06:37 GMT References: <2509@nems.dt.navy.mil> Sender: news@Solbourne.COM Organization: Solbourne Computer, Inc. Lines: 28 In article <2509@nems.dt.navy.mil> lumsdon@dtoa1.dt.navy.mil (Esther Lumsdon) writes: >Under VMS (version 5.2), what privileges does PING require? It requires CMKRNL and SYSPRV on all version of VMS and all version of WIN/TCP for VMS through at least 5.1. >Tech Support at Wollongong told me it was cmkrnl, but, when ping image >is installed with that privilege, this message appears when trying to >use ping (from regular user account; works fine from system account): > $ ping _node_ > ping: socket: Permission denied > >I've played with it, and, will ping work when installed with only the >sysprv privilege? The problem is that Technical support gave you incomplete information. WIN/TCP PING requires that you have both CMKRNL and SYSPRV in order for certain calls that it makes to succeed. If you don't have both of these privs enabled, then you will get the error message that you see above. The good news is that as of release 5.1 you are supposed to be able to install ping with privs. Everything should work OK if you install the ping image with CMKRNL and SYSPRV. -- Warner Losh imp@Solbourne.COM Boycott Lotus. #include