I can not ping with Indy on Windows NT or Windows 2000.  What do I do about this?

Previous  Top  Next

In Windows NT and Windows 2000, Indy's TIdICMPClient requires administrative privileges to use raw sockets.  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 single-user operating systems such as Windows 95, 98, and ME, any user can ping with Indy.