Ping "Local Problem" On 4.3 beta

About a month or two ago I had to reinstall the windows beta since I had a VM issue. I tried to restore what I had but ended up having a hybrid since I had to recreate objects. The VM is running on W10 instead of W7. (and it was running W10 prior to the rebuild)

In any event a lot of my devices return the error “Local Problem” for Ping yet I can ping said devices from the VM or anywhere.

So what is this error and how can we fix it? a majority of my map is red or orange and it shouldn’t be.

Thanks leon

Has anyone else seen this or know how to resolve it?

THanks leon

Is anyone from Mikrotik support reading these posts please?

Thanks leon

Bug is now reported to DEV for fixing.

will a 4.4 come out then as I am not migrating to the new dude at this time since there is no windows server

leon

You cannot expect that the 4.4 will be released. Only the 6 version is now under development.

can someone explain why I am getting these ping failures when I can ping from the box dude is running on?

ALso, you need to rethink the windows server component please

thanks leon

This is user forum and by “you” you are referring to other users. I would like to see dude windows server continued, but I will probably move to CHR or x86 when the v.6 dude server will be at least as reliable as the 4b3 is now and there will not be windows server available.

Make sure to lower UAC and make sure the dude is running as administrator. When installing the dude make sure you are using an administrator account since it is probably setup to run as a service. There is an old thread somewhere about this problem although not win10. This could be a new problem.

was originally on a w7-32 VM which I migrated to W10-32.

The account installed is admin but I will double check. everything works except for pings

Thanks Leon

just checked and its not running as a service but ALL TIME
I did crank back the UAC as well and pings still failing from dude.

anything else you can think of?

thanks leon

I just double checked and I set the Dude OBJECT to RUN AS ADMINISTRATOR and that did it.

I vaguely remember what you mentioned.

many thanks.

leon