Re: IdIcmpClient problem with NT4

Giganews Newsgroups
Subject: Re: IdIcmpClient problem with NT4
Posted by:  Remy Lebeau (TeamB) (gambit47.no.spam@no.spam.yahoo.com)
Date: Fri, 12 Dec 2003

"Kay Kirchhoefer" <nobo…@nowhere.com> wrote in message
news:D0E83548C889E240nobo…@nowhere.com...

> What could be the problem ?

Did you read the documentation for TIdIcmpClient?  It says the following:

    "Note: For Windows NT, and Windows 2000, administrator privileges are
required to allow TIdICMPClient.Ping to work properly. The command line PING
application does not exhibit this behavior because Microsoft chose to use
undocumented calls in ICMP.DLL and its winsock implementation to get around
the issue. In short: they cheated. Indy does not use ICMP.DLL to maintain
Linux compatibility, and allow use of both Raw sockets and ICMP sockets."

In the case of NT, the following article explains how to turn off the
restriction:

    PRB: RAW Socket Access Denied to Non-Admin Windows NT 4.0 and Windows
2000 Users
  http://support.microsoft.com/default.aspx?scid=kb;en-us;195445

In the case of Win2K, there is no way to bypass that restriction, sorry.

If that does not suit your needs, then you will just have to forget about
using TIdIcmpClient and use Microsoft's undocumented Icmp.dll instead.

Gambit

Replies

None

In response to

IdIcmpClient problem with NT4 posted by Kay Kirchhoefer on Thu, 11 Dec 2003