Pinging in Dude client fails as Windows 'restricted user'

RouterOS The Dude
1

I’ve got The Dude server running on a Win2000 Server, everything’s fine. Small issue with the Dude as client though:

When I run the dude client on a Windows XP PC under a restricted user (non-admin), then something peculiar happens: ping fails from the dude client, but pinging simultaneously from a command prompt works fine. See attached screenshot. (When I ask the ping tool in the dude client to let the server do the pinging, that obviously works fine: there’s no problem with the Dude server.)

When I give the local windows user admin privilieges, this issue goes away. (But I do not want to run the user as admin…)

Note there’s no firewall on this machine, that can’t be it.

Everything else in the Dude client seems to work fine under the restricted user, only the ping tool fails.

I’ve read posts with similar issues under Vista, and then people were pointed towards the UAC feature. Since I have this issue under XP, there must be something else underlying all this.

Anybody seen this on their setups?
Ping fails from Dude client.jpg

2

I’ve noticed this in the Dude manual (http://wiki.mikrotik.com/wiki/Dude_usage_notes#Getting_Started):

Note for Linux users: you should start the Dude from the root user (or delegate some permissions to your regular user), or else the Dude will not be able to ping hosts.

I’m not using Linux, but still, it all seems very related. Is there any permission (what could it be?) that I could give the restricted Windows user so pings from the local Dude client do work?