Is it possible to fix the jetdirect bug in this release?

Better documentation

We are having the same problem and we have the most current version of The Dude installed. No matter what age the Ketdirect is, after The Dude polls it with the HP Jetdirect polling, the Jetdirect would lock up. I now have to disable that poll on over 100 printers now. How fun for me.

I checked part one of you reply and it looks like it's configured properly. As far as SNMP, I don't think that is the problem. The IP addess and the computer name are reporting back properly, they just report back as Some Device instead of a Windows computer.

I have a problem where all of our Windows workstations are being detect as "Some Device". Is there something I have overlooked in the scan configurations or is it something on the Windows firewall that is preventing The Dude from detecting that it is a Windows computer?

Great! The discovery worked! Does anyone know if there is a way to create a notification when there is a new item discovered?

Very helpful, that was it exactly. Thanks!

I was wondering if there was a way to automatically discover a new network device within a VLAN or a subnet. For example, on VLAN in the range 192.168.100.x, if a new device connected and was assigned an IP adddress via DHCP, is it possible to configure Dude to pick up that new device and display it...

I read through this thread about using a WOL application. I was successfully able to do this without a batch file using the mc-wol app. I just put the app on C: and used this command: c:\mc-wol [Device.MacAddressesColumn] It works great. The problem is, I have to create that for every single device ...