[XPSP2/admin] "Access denied" when running network utilities?

G

Gilles Ganault

Hello

On a up-to-date test host running XPSP2, logged on as admin, I get
"Access denied" messages when running network utilties in a DOS box
such as "netstat", "ipconfig", or "ping". Nothing shows up in the
Event Viewer.

I don't know why XP is doing this. Any idea?

Thank you.
 
J

Jim

Gilles Ganault said:
Hello

On a up-to-date test host running XPSP2, logged on as admin, I get
"Access denied" messages when running network utilties in a DOS box
such as "netstat", "ipconfig", or "ping". Nothing shows up in the
Event Viewer.

I don't know why XP is doing this. Any idea?

Thank you.
This is a permission issue. However, getting such a message when trying to
access these utilities is way out of the ordinary.
First, determine what the permissions on these utilities are. A member of
the administrators group can always perform this task.
Next, set the permissions to allow full access to members of the
administrators group. A member can always do this.

Finally, check your machine for malware. Unexplained changes to permissions
is usually a sign of such things. (Unless some pranksters live in your
house).

Jim
 
C

Claymore

Hello

On a up-to-date test host running XPSP2, logged on as admin, I get
"Access denied" messages when running network utilties in a DOS box
such as "netstat", "ipconfig", or "ping". Nothing shows up in the
Event Viewer.

I don't know why XP is doing this. Any idea?

Thank you.

Salut Gilles,

How are your IP addresses being assigned - server, router?
If it's via a router, try resetting the router.
 
G

Gilles Ganault

This is a permission issue. However, getting such a message when trying to
access these utilities is way out of the ordinary.

It's very strange. It's a clean, test host, on which I'm connected as
admin. Even running wget in a DOS box says "Access denied".
 
G

Gilles Ganault

This is a permission issue. However, getting such a message when trying to
access these utilities is way out of the ordinary.

Found what it was: It's the Comodo firewall that was causing this.
Removing it solved the issue. I'll go ask for information over there.
Thanks.
 
B

bojimbo26one

Found what it was: It's the Comodo firewall that was causing this.
Removing it solved the issue. I'll go ask for information over there.
Thanks.

Which version of Comodo are you using ? I`m using v2.0 , tried v3.0
but prefer v2.0 .
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top