Greetings all.
I can no longer use the “discover” feature with my install of The Dude 3.3. Have tried exporting config…uninstalling…reinstalling…importing config…but with no happy ending.
To be clear, to test I create a new network map, click the Discover button, enter the subnet info for the map (all valid and real) and then click Discover button again…and…NOTHING.
Thx in adv.
JJM
Could be that is is working but the device type setting is removing the object as soon as it it discovered.
Just checked ALL my settings and they’re (mostly) all set to default. Will apply 3.4 today and report back the results.
I have the same issue. I just installed 3.4 on a Windows 7 64 bit machine. There were no errors on the install, but the scan just comes back with nothing.
I too have the same issue with 3.4.
I then installed 3.5 and it has the same problem.
My system is Windows 7 64 bit.
I had no troubles with same PC running XP Pro 32 bit and Dude version 3.4, the Local map would populate automatically with “discovered” devices.
Windows 7 64 bit, discovers nothing but did find something strange.
I added a device manually, scanned with ping and icon green but thirty seconds later (default probe interval) it changed state and Dude ping reported a “local problem”.
The same time I had a windows ping running in a command window and it didn’t drop a packet to my device.
Dude ping an issue?
AT LAST!
The solution to my problem was to change the Discover Mode from fast (scan by ping) to reliable (scan each service).
I left rest on defaults and it found most devices.
The problem seems to be Dude ping
Have found with Win7 that the UAC has an issue with some of the calls that the dude makes, if u disable windows UAC the ping and scan functions seem to work perfectly again.
yes, run the dude as administrator (right click on the Dude icon, choose “run as administrator”) to fix the problem.