> Although I already have an own implementation for pinging remote
> hosts, I encountered problems which I hoped others may have already
> solved.
>
> The thing is, that all sources I found (including my own) use raw
> sockets to send ICMP echo requests. A user without administrative
> privileges does not have the permissions to create raw sockets though.
> This is why it simply does not work with user permissions. Here is an
> example from Microsoft: http://support.microsoft.com/kb/828993/en-us
>
> I thought maybe the SocketPermission class might help. But it seems
> that it is only capable of allowing TCP and UDP connections, not ICMP.
>
> Does anyone have a solution for this?
>
> Best regards,
> Christian Jacob.

"Dominick Baier [DevelopMentor]" wrote:

> Hello Christian Jacob cjacob AT nospam toptechnologies DOT de,
>
> under which operating system are you running? I am surprised that this works
> at all, as sending raw sockets on XP SP2 and W2K3 SP1 should be disabled
> by now (but maybe not for ICMP...)
>
> SocketPermission is a Code Access Security class and has nothing to do with
> OS level privileges.
>
> If you can upgrade to .NET 2.0 - there is an easy solution :)
>
> using System.Net.NetworkInformation;
>
> PingReply reply = new Ping().Send(args[0]);
> Console.WriteLine("Reply from {0} - Roundtrip Time {1} ms", reply.Address,
> reply.RoundTripTime);
>
>
> ---------------------------------------
> Dominick Baier - DevelopMentor
> http://www.leastprivilege.com
>
> > Although I already have an own implementation for pinging remote
> > hosts, I encountered problems which I hoped others may have already
> > solved.
> >
> > The thing is, that all sources I found (including my own) use raw
> > sockets to send ICMP echo requests. A user without administrative
> > privileges does not have the permissions to create raw sockets though.
> > This is why it simply does not work with user permissions. Here is an
> > example from Microsoft: http://support.microsoft.com/kb/828993/en-us
> >
> > I thought maybe the SocketPermission class might help. But it seems
> > that it is only capable of allowing TCP and UDP connections, not ICMP.
> >
> > Does anyone have a solution for this?
> >
> > Best regards,
> > Christian Jacob.
>
>
>

> Hi Dominick,
>
> yes, I am actually using Windows XP SP2. I know, that .NET 2 brings a
> solution (I was wondering all the time, why 1.1 didnt include a ping
> class, e.g.), but unfortunately, I cannot upgrade (yet) for several
> reasons.
>
> 1. The ping class is used in a component of a software which is
> distributed to customers and we cannot force them to upgrade to 2.0
>
> 2. 2.0 is still in beta. ;-)
>
> Anyway,... so you say, there is no way of pinging another computer
> safely without running into permission problems?
>
> Since we use the ICMP echo request for testing whether a host is
> "alive", is there another convenient way for getting this piece of
> information? I read about establishing a TCP connect,... is this a
> common and reliable way?
>
> Best regards,
> Christian.
> "Dominick Baier [DevelopMentor]" wrote:
>
>> Hello Christian Jacob cjacob AT nospam toptechnologies DOT de,
>>
>> under which operating system are you running? I am surprised that
>> this works at all, as sending raw sockets on XP SP2 and W2K3 SP1
>> should be disabled by now (but maybe not for ICMP...)
>>
>> SocketPermission is a Code Access Security class and has nothing to
>> do with OS level privileges.
>>
>> If you can upgrade to .NET 2.0 - there is an easy solution :)
>>
>> using System.Net.NetworkInformation;
>>
>> PingReply reply = new Ping().Send(args[0]);
>> Console.WriteLine("Reply from {0} - Roundtrip Time {1} ms",
>> reply.Address,
>> reply.RoundTripTime);
>> ---------------------------------------
>> Dominick Baier - DevelopMentor
>> http://www.leastprivilege.com
>>> Although I already have an own implementation for pinging remote
>>> hosts, I encountered problems which I hoped others may have already
>>> solved.
>>>
>>> The thing is, that all sources I found (including my own) use raw
>>> sockets to send ICMP echo requests. A user without administrative
>>> privileges does not have the permissions to create raw sockets
>>> though. This is why it simply does not work with user permissions.
>>> Here is an example from Microsoft:
>>> http://support.microsoft.com/kb/828993/en-us
>>>
>>> I thought maybe the SocketPermission class might help. But it seems
>>> that it is only capable of allowing TCP and UDP connections, not
>>> ICMP.
>>>
>>> Does anyone have a solution for this?
>>>
>>> Best regards,
>>> Christian Jacob.

"Christian Jacob" <cjacob AT nospam toptechnologies DOT de> wrote in message
news:5EDFF1A4-1F39-4AC8-A812-4E21B9DAC5A5@microsoft.com...
> Hi Dominick,
>
> yes, I am actually using Windows XP SP2. I know, that .NET 2 brings a
> solution (I was wondering all the time, why 1.1 didnt include a ping
> class,
> e.g.), but unfortunately, I cannot upgrade (yet) for several reasons.
>
> 1. The ping class is used in a component of a software which is
> distributed
> to customers and we cannot force them to upgrade to 2.0
>
> 2. 2.0 is still in beta. ;-)
>
> Anyway,... so you say, there is no way of pinging another computer safely
> without running into permission problems?
>
> Since we use the ICMP echo request for testing whether a host is "alive",
> is
> there another convenient way for getting this piece of information? I read
> about establishing a TCP connect,... is this a common and reliable way?
>
> Best regards,
> Christian.
>
>
> "Dominick Baier [DevelopMentor]" wrote:
>
>> Hello Christian Jacob cjacob AT nospam toptechnologies DOT de,
>>
>> under which operating system are you running? I am surprised that this
>> works
>> at all, as sending raw sockets on XP SP2 and W2K3 SP1 should be disabled
>> by now (but maybe not for ICMP...)
>>
>> SocketPermission is a Code Access Security class and has nothing to do
>> with
>> OS level privileges.
>>
>> If you can upgrade to .NET 2.0 - there is an easy solution :)
>>
>> using System.Net.NetworkInformation;
>>
>> PingReply reply = new Ping().Send(args[0]);
>> Console.WriteLine("Reply from {0} - Roundtrip Time {1} ms",
>> reply.Address,
>> reply.RoundTripTime);
>>
>>
>> ---------------------------------------
>> Dominick Baier - DevelopMentor
>> http://www.leastprivilege.com
>>
>> > Although I already have an own implementation for pinging remote
>> > hosts, I encountered problems which I hoped others may have already
>> > solved.
>> >
>> > The thing is, that all sources I found (including my own) use raw
>> > sockets to send ICMP echo requests. A user without administrative
>> > privileges does not have the permissions to create raw sockets though.
>> > This is why it simply does not work with user permissions. Here is an
>> > example from Microsoft: http://support.microsoft.com/kb/828993/en-us
>> >
>> > I thought maybe the SocketPermission class might help. But it seems
>> > that it is only capable of allowing TCP and UDP connections, not ICMP.
>> >
>> > Does anyone have a solution for this?
>> >
>> > Best regards,
>> > Christian Jacob.
>>
>>
>>