Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 10 Mar 2005 09:56:29 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: 1.0-1 ping problem Message-ID: <20050310085629.GV2839@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2i On Mar 7 15:13, Paul G Cantalupo wrote: > Hello, > > When I run ping as the administrator on my Win2K box, it works fine but as > a regular user, I get the following. > > ping: socket: operation not permitted I just had a look into the sources. Cygwin's ping is using raw sockets. This only works for admin accounts, according to MSDN: Note Raw socket support requires administrative privileges. Users running Winsock applications that make use of raw sockets must have administrative privileges on the computer, otherwise raw socket calls will fail with an error code of WSAEACCES. Use Windows' native ping instead. > I added the u+s permission to the ping executable and now I get (from a > regular user account): The s-bits are just faked. Cygwin doesn't support switching to another user context by setting them. I'm planning to implement that for years but time goes by... Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/