Let me begin by saying hello and being new to TheDude; what an OUTSTANDING product, and the price is even better! Way to go guys!! VERY COOL!
TheDude 3.0beta3 running on Win2kProSP4
This is a very basic configuration, monitors services and SNMP on servers/printers and other devices, no WiFi, simple email alerts, etc.
Question1:
Why would TheDude repeatedly add a 192.168.40.0/21 network when I only tell it to scan 192.168.40.0/24? The network is setup with servers and important devices on 192.168.40.0 with user workstations and DHCP running on 192.168.45.0 with a mask of 255.255.248.0 for both 40 & 45. What gives and how can I tell TheDude to quit adding this /21 subnet? This is very frustrating and causes my workstation to slow to a crawl in the morning before I can clear it all out.
Question2:
There are several phantoms or ghost devices that show up in 192.168.40.0 network to which there are no DHCP addresses in this range and NO ONE is assigning these addresses manually. They appear in the network map and are grey with no services. Port scans, IP address scans come up with no devices which match those listed in the TheDude, so how come TheDude says differently? The ghost devices are always 192.168.40.101-110 (never higher or lower than that range, so far). DO I need to look into the possibility that someone is on my network by giving themselves a static and running firewall to hide? I have unplugged my VPN server as a precaution. How does TheDude figure these things out if that is the case?
Question3:
If I change the server from "always run" to "run as a service" all my devices turn red. I change it back, viola they all turn green again. Somehow it’s not able to function as a service? This install was done after exporting previous beta1 configuration, uninstalling and then installed beta3 and then an import of the xml. I did give the service account admin rights, which did not fix the problem; my account is a member of the enterprise administrators group. I would like to eventually get this onto a server and let my workstation be a workstation again. It worked as a service before, why not now?
Thanks in advance!
Shawn
1. Dude adds network clouds for networks it thinks are real. You say that you
have DHCP running on 192.168.45.0/255.255.248.0 and that IS 192.168.40.0/21.
You can prevend The Dude adding network clouds at all by uncheking 'Add
Networks' in discovery settings.
2. Dude discovers devices not only by pings and other services, but also by
looking in other device arp tables. If it finds such a device it adds and
scans for services. Depending on discovery settings 'Add Serviceless' and
weather any services were found it either leaves this device on map or
removes it.
3. Will be fixed in next release.
have DHCP running on 192.168.45.0/255.255.248.0 and that IS 192.168.40.0/21.
You can prevend The Dude adding network clouds at all by uncheking 'Add
Networks' in discovery settings.
2. Dude discovers devices not only by pings and other services, but also by
looking in other device arp tables. If it finds such a device it adds and
scans for services. Depending on discovery settings 'Add Serviceless' and
weather any services were found it either leaves this device on map or
removes it.
3. Will be fixed in next release.