Hello,
I have a larger internal network (26 Class C’s covering 10 buildings).
And I have tried to use dude 2.x and the beta 3.x and it seems ever since we have started using TheDude every network that we scan seems to lockup all the jetdirects that we find.
Power cycling the HPJetdirects only keeps them alive until the next scan.. Anyone else having this happen?
we have a few jetdirects and network enabled HP printers and they work fine. there was a problem in earlier versions, but later betas should not cause problems like this.
All the firmwares are up to date, this happens with 2.x and 3.x. We are running with Dell and Cisco switches as well as 2 or 3 vlans at each building.
Aside from the fact that this was fixed in older versions, how can I keep it from happening in the current versions.
Because it is happening and it is very disruptive.
In general you should keep monitored services on those printers as low as you
can. Remove all services except ping (and maybe ones that do snmp queries),
and it should be stable.
Makes you wonder the quality of the HP JetDirect network stack if they are brought down so easily from the network by something as benign as a little probing… it’s not like The Dude is DoS-ing the critters…
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. 
From the devices view you can sort by type and select multiple devices… Not that it makes it much easier because it doesn’t work, you can select a range and disable services on many devices at once but it only disables services on one device.
There is obviously a bug or the feature is not supported. In which case you should not be able to select multiple devices. I have tried doing other range things and some work and some don’t so I think it is supposed to work…