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.
yes Normis i can ping 126.96.36.199
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.
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.
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:
ping - local problem.jpg
The following shows command line ping (to the same device) working:
cmd ping - works.jpg
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.
You do not have the required permissions to view the files attached to this post.
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.
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),
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