XP PRO-"No permission to open RAW network socket".

My 3 PC home network seems to be working but 'StressTest' software for
the INTEL D945GNT motherboard keeps failing the "network" test.
'StressTest' is failing to ping 127.0.0.1. The error message is
"WARNING: Network, No permission to open RAW network socket". While the
'StressTest' is failing PINGING LocalHost, I also run PING localHost in
a CMD window and this PING does get the echo expected.

My system runs WIN XP PRO SP2. I looked, but cannot find, "how to
adjust permissions" to allow "StressTest to open RAW Netowrk socket".
Running the StressTest in RUN_AS mode did not allow PING to work.

I am told that I must run StressTest in an account with Administrator
priviledges. I really need assistance with this and particularly with
being sure "administor USERS have correct priviledges". None of my
USERS, shown with "adminstrator" require a password. Do I need to create
a seperate administrator USER with a password?

Many thnaks for suggestions. Dave_s

On Tue, 23 May 2006 09:04:55 -0700, Dave_s <(E-Mail Removed)> wrote:

>My 3 PC home network seems to be working but 'StressTest' software for
>the INTEL D945GNT motherboard keeps failing the "network" test.
>'StressTest' is failing to ping 127.0.0.1. The error message is
>"WARNING: Network, No permission to open RAW network socket". While the
>'StressTest' is failing PINGING LocalHost, I also run PING localHost in
>a CMD window and this PING does get the echo expected.
>
>My system runs WIN XP PRO SP2. I looked, but cannot find, "how to
>adjust permissions" to allow "StressTest to open RAW Netowrk socket".
>Running the StressTest in RUN_AS mode did not allow PING to work.
>
>I am told that I must run StressTest in an account with Administrator
>priviledges. I really need assistance with this and particularly with
>being sure "administor USERS have correct priviledges". None of my
>USERS, shown with "adminstrator" require a password. Do I need to create
>a seperate administrator USER with a password?
>
>Many thnaks for suggestions. Dave_s

Consider the time it took to post that question you could have already
answered it ;-)

If the application works when run from the actual Administrator account, then
create a user account with a real live password and give it Administrator
privileges. Then log in and run your "Stress Test" from that account.

What's the worst that can happen?

Dave_s <(E-Mail Removed)> writes:

>My 3 PC home network seems to be working but 'StressTest' software for
>the INTEL D945GNT motherboard keeps failing the "network" test.
>'StressTest' is failing to ping 127.0.0.1. The error message is
>"WARNING: Network, No permission to open RAW network socket". While the
>'StressTest' is failing PINGING LocalHost, I also run PING localHost in
>a CMD window and this PING does get the echo expected.

>My system runs WIN XP PRO SP2. I looked, but cannot find, "how to
>adjust permissions" to allow "StressTest to open RAW Netowrk socket".
>Running the StressTest in RUN_AS mode did not allow PING to work.

XP SP2 imposed new restrictions on raw sockets:

* TCP data cannot be sent over raw sockets
* UDP datagrams with an invalid source address cannot be sent
over raw sockets. A datagram is invalid if the asserted source
IP address does not exist on a network interface.

Depending on how your stress test software was written, this may
explain the problem.

As a side note, this change broke NMAP, even though its use as a security
tool was recommended by Microsoft on its web site. Microsoft's statement
to Fyodor (the author of NMAP) was that "raw sockets are used only
by hackers."

Joe Morris

Joe Morris wrote:
> Dave_s <(E-Mail Removed)> writes:
>
>
>>My 3 PC home network seems to be working but 'StressTest' software for
>>the INTEL D945GNT motherboard keeps failing the "network" test.
>>'StressTest' is failing to ping 127.0.0.1. The error message is
>>"WARNING: Network, No permission to open RAW network socket". While the
>>'StressTest' is failing PINGING LocalHost, I also run PING localHost in
>>a CMD window and this PING does get the echo expected.
>
>
>>My system runs WIN XP PRO SP2. I looked, but cannot find, "how to
>>adjust permissions" to allow "StressTest to open RAW Netowrk socket".
>>Running the StressTest in RUN_AS mode did not allow PING to work.
>
>
> XP SP2 imposed new restrictions on raw sockets:
>
> * TCP data cannot be sent over raw sockets
> * UDP datagrams with an invalid source address cannot be sent
> over raw sockets. A datagram is invalid if the asserted source
> IP address does not exist on a network interface.
>
> Depending on how your stress test software was written, this may
> explain the problem.
>
> As a side note, this change broke NMAP, even though its use as a security
> tool was recommended by Microsoft on its web site. Microsoft's statement
> to Fyodor (the author of NMAP) was that "raw sockets are used only
> by hackers."

PassMark Company who sells Burn-in Test Software and is the
developer of StressTest for INTEL D945 GNT motherboards is using RAW
SOCKETS in the StressTest.
>
> Joe Morris

I have two PC's both running StressTest, both running XP PRO SP2.
StressTest fails 'network test' on the Desktop PC and runs error free
on the Thinkpad Laptop.

The laptop is a loaner set up by my son who is not available to help.
I set up the Desktop.

It appears that the StressTest software CAN RUN 'network test' ERROR
FREE on a XP PC if given correct priviledges.
However, I cannot find the XP PRO setting on the Desktop to give the
needed RAW SOCKET priviledges. I can really use some hints with this
problem.

Thank you, Dave_S