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 ...

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...

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 ...

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 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 al...

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...