i am setting up The Dude from scratch, and am installing on a server.
as a basic setup, i just want it to ping our routers & switches.
when i add a device in, it’s initially green and everything looks OK, but then after a couple of minutes it goes Red.
If i use the Ping tool on Dude, i cannot get a response from the device.
If a use the Traceroute tool on Dude, i DO get a response (quick response, no timeout)
If i ping from a command line on the Server i also get a quick response from the device, with no timeouts.
Finally, as a test, i’ve installed Dude on my laptop (connecting through the same subnet & routers) and Dude has no problem pinging the device(s) from my laptop.
I’ve tried several devices in different locations, with the same result.
The firewall is switched off on the server as everything is dealt with at the router, so it’s not blocking ICMP traffic.
Also, when it’s initially setup it pings OK for a couple of minutes, then goes red.
I also think it’s something to do with the server, but i can’t think what.
The only thing that springs to mind is the server has 2 network cards, one of which is disabled, but i can’t see any settings in Dude to use one network card over another (if this exists?).
The Dude is added to the exceptions that can pass the firewall. Still I cannot pring from The Dude, while I can ping from a DOS box. After setup I could ping for a while then everything became red while the webtool and telnettool still work. It has something to do with the server. But I don’t know what.
For anyone still struggling with this problem, I have been able to solve it for our specific environment:
It seems that The Dude does not fetch routes at all from the static routing table, and for The Dude to ping a device it needs a route in the dynamic table, eg:
If you’re on a 192.168.1.0 network and you wish to ping device 196.47.193.163 through gateway 192.168.1.1, even if you have the route set up in the static routing table you’ll still need to add it to the dynamic routing table by using the following command -
This problem seems to only occur in cases where you run the dude server from a machine that has Routing and Remote Access set up, with routes to specific devices that do not go through your default route gateway (0.0.0.0), because with the dude pinging from any other device it would successfully resolve over the default route, through the device’s default gateway. tl;dr - gateway machines have specific routes that need to be utilized. Adding to static in Routing and Remote Access isn’t enough.
I have the same problem, with one server, all other pings going perfectly. Can you tell me please, where can i put the following: route add 196.47.193.163 mask 255.255.255.255 192.168.1.1 (with my ip adresses, of course).
