I was able to find some code on CodeHound that worked for me. I made some changes to consolidate the caller code but all in all, it worked great.
Message from Kamen Lilov <[EMAIL PROTECTED]>@DISCUSS.DEVELOP.COM received on 09/12/2006 02:11 PM 09/12/2006 02:11 PM Kamen Lilov <[EMAIL PROTECTED]>@DISCUSS.DEVELOP.COM Please respond to "Discussion of advanced .NET topics." <[email protected]> Sent by "Discussion of advanced .NET topics." <[email protected]> To: [email protected] cc: Subject: Re: [ADVANCED-DOTNET] [POSSIBLE SPAM]::Re: [ADVANCED-DOTNET] Ping Just a quick thought... Why don't you spawn a CMD.EXE with a ping invoked in a hidden/minimized window, redirect output, then recognize some simple patterns? I know it sounds hacky but sometimes process spawning actually works well, even not under *nix :) -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of dave wanta Sent: Tuesday, September 12, 2006 12:53 AM To: [email protected] Subject: Re: [ADVANCED-DOTNET] [POSSIBLE SPAM]::Re: [ADVANCED-DOTNET] Ping just a heads up. If this is a web app, you will need to have your IIS app run under admin privileges. In 1.x, Pinging requires the capability to create Raw sockets, and you need admin permissions, per the OS, to do this. I haven't looked at 2.0, and if/how they got around this OS requirement. Cheers! Dave [del] =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
