i have installed Dude 4.0
i discoverd my network and it founds the devices then i added the link bethwen them, but when i ping any of devices in the network it gets failed. why this happens?!
what i have to do?
please help me.
thanking you,
Ehsan.

can you ping those devices from the windows command line?

start -> run -> cmd - > ping 1.1.1.1 (the address)

yes Normis i can ping 1.1.1.1
i have one more question,
can i add some service in the service list to monitor in my server?
i didnt have the SNMP on my devices may be the problam was becuse of that, now i am adding it.
thnaks for your attantion.

of course, double click the device in the Dude and go to the services tab

Dear Normis,
thanks for your response.
i think you miss understoud my question,
i don't want to monitor the services which is on the list, i want to monitor some specific service on my server.
i have some services on my server and its very important for me to be sure the services are working properly.
thanks for your helps.

Yes, you can add custom probes and then use them to make new services:
http://wiki.mikrotik.com/wiki/Manual:The_Dude/Probes

Lot of information in the Dude manual:
http://wiki.mikrotik.com/wiki/Manual:The_Dude

Am also experiencing the same problem and am using Dude 3.6 in windows 7, Ping wont work as one of my services keeps on giving an error reading - Local problem. Does anyone have a way around this?

You must run the dude from an account with admin privileges... is that your trouble?

its running from an admin account with all privileges and thats the only account on the machine.

same here. I cant ping anything from the Dude.
Its beta2.

I am experiencing the same problem with 4.0beta2.
Every "ping" is failing, with the cryptic message "local problem". However, command line ping works fine.

I installed the 4.0beta2 on a system that has not had The Dude - running Windows Server 2008R2.
I imported the settings from 3.6 on a different system (though I don't think that is relevant).

The following shows The Dude error: The following shows command line ping (to the same device) working: Just to be clear:
- the account has admin privileges.
- the problem occurs even with the Windows Firewall turned off.
- a protocol trace shows that no ICMP messages are emanating from the server, *except* when command line ping is used.

I cannot find any explanation for the error "local problem" and thus I have no idea how to fix the problem.

--colin

I too am experiencing this issue on two different workstations, one with Windows 7 and one with Windows XP SP3

I tried an additional experiment (in case my problem was something to do with security in Windows Server 2008 R2). I installed 4.0beta2 on a Windows 7 SP1 machine - and I got the same behavior, notably that the ping service fails with "local error".

As a consequence of this behavior, it also means that network discovery is not able to discover anything.

Try disabling UAC? if you have "local error"...

same problem here with win7
please may sm1 work on this i have tried everything i cant just ping from dude

Did something change in your systems? Maybe windows update? It worked fine before for everyone. Local error means Dude couldn't run ping command due to a program error, or some other unknown factor.

In my case, I'm trying 4.0beta2 on two different systems (Windows Server 2008 R2 and Windows 7) that have not been used to run The Dude before.

I can confirm that turning off UAC on Windows 7 (SP1) running 4.0beta2 gets rid of the "local error" problem, and now The Dude is able to discover devices on the network.

While this was a good check to determine the probable cause of the problem, like "using a sledgehammer to crack a nut" this does not represent a viable workaround. To have production servers, capable of managing a network with lower security increases the potential risk that malware could be introduced (and rapidly spread) through the network via this "Trojan horse".

Now we understand what the problem is, does this represent:
- a bug in The Dude that needs to be fixed, and/or
- the need for additional instructions to explain how to make The Dude work (without disabling security)?

I may have answered my own question. There is an alternative to disabling UAC completely.

If I locate the executable (c:\Program Files (x86)\Dude\dude.exe),
right mouse
select Properties
click on the Compatibility tab
then check the "Run this program as an administrator"
once I restart The Dude (client and server - perhaps after a reboot?) it is able to Ping devices without getting "Local Error" any more

HI cstrutt
It doesnt work i still cant ping this is just a bug this guyz have to fix

Francistito >>> It doesnt work i still cant ping

Have you set your firewall rules to all The Dude to be able to send and receive packets without being blocked?

You might try, for example, adding a new firewall rule to allow The Dude's executable (c:\Program Files (x86)\Dude\dude.exe) to "allow the connection".

Windows 7 firewall standard blocks ICMP ping inbound and outbound. By default you cannot ping from and cannot ping to a Windows 7 machine.

I had to disable UAC and allow ping (ICMP echo-reply) inbound and outbound till the Dude worked well.

Network and Sharing Center > Windows Firewall > Advanced Settings

Under Inbound Rules: "File and Printer Sharing (Echo Request - ICMPv4-In)"
and under outbound Rules: "File and Printer Sharing (Echo Request - ICMPv4-Out)"

Enable for all Network Profiles that you use with the Dude (Private/Public/Domain)

Success


Andreas

try to change the ping probe

my dude(4.0beta3) ping openvpn clients timeout,but ping others real node work fine.

i try to change ping probe's Packet Size from 32 to 64,and it can ping openvpn clients.

i don't known why ,but it work.

I have this problem a year too

PLZ help me

Look at the cstrutt's comment, it realy work !

c:\Program Files (x86)\Dude\dude.exe),
right mouse
select Properties
click on the Compatibility tab
then check the "Run this program as an administrator"
Kill service, start again and vuala

Thanks to cstrutt's comment, the second day started arround this

Thanks a lot

In my case, reset the switch, in my network structure is complex and run the switch was hanging
sorry for my bad English

Hi!
I solved this problem running the Dude in Windows Vista (SP2) compatibility mode.

so disabling UAC on my windows 2012 R2 VM fixed the ping issue...

I was seeing the same thing where I could ping from cmd prompt, but not from "the dude"

after disabling UAC "the dude" can ping everything now.

I disabled UAC.

But now my Dude has lost all settings. No maps/devices/user etc.

Where do I need to find and put these to restore it?

Yup its working thanks a lot. You need open dude in administrator mode.

Same problem with pings on dudue 3.6

In my case admin privilages dosent work on Win7
but it works on Win10


my Win7 got already UAC OFF ... so I just turn it ON and woila
and after restart PC ... ping working


dont forget I still got admin privilages TURN ON for dude.exe on Win7 and then turn on/off UAC