Discovery problems

I have just installed the Dude to play with (I haven’t any mikrotik units - yet!) but I am having trouble getting discovery to find all the units on the network.

I have a variety of units most of which talk snmp and http, some are Http on port 8080, some are telnet / ping only…

Dude only finds a few of the units and then discovers things on unallocated IP addresses!! I have tried a ‘fast’ ping only discovery, also a ‘reliable’ service poll discovery both of which don’t find all of the devices. I have a ‘ping’ utility on the same PC which is reliably pinging all the devices so I know they are reachable at least at the ping level. All the device types are ticked & I can’t see any reason why it isn’t working…

The PC is behind a firewall (in DMZ) from the network but I use ping/web/telnet from the PC to the network without any problems. I have also temporarily set the PC up with a direct connection to the network which may have improved matters slightly but it still didn’t find all the units.

Is the timeout for discovery pings/service connections (not polling) configurable?
Also I set up a port8080 service to connect on TCP port 8080 with ‘connect only’ checked but that seems to find port8080 even on devices that don’t support it…

A minor issue is that Dude doesn’t pick up the port information from my 3com switch in the bridge fdb table…

Any suggestions? Is it possible to enable some debug logging?

Thanks
David

PS Free (libre) the Dude…!

Hmm even more strange… I installed dude on my main machine (which is connected to the network over a VPN & ADSL connection so has quite high round trip latency) and it discovered the network without any issues so it must be something on the network management machine. What are the dependencies for Dude? Does it use Java or .NET framework or winPcap or anything like that?

David