I moved my dude from one box to another since I am decommissioning the old one. I finally found some time to play with this over weekend. The old box was Windows 2003 and the new box is Windows 7.
my devices and what not were there but PING stopped working comes up with some error. BUT, from a CMD prompt, I can PING the same devices from the same box. I removed the dude and reinstalled letting it clear the config and did the same thing. PING fails to work from the application. if I run a discover again pings dont but it does find other services running.
Has anyone seen this? ANy thoughts on what to try?
no but i’ve never needed this before and if it was an admin problem (user that logged in is administator anyway) the other discovers shouldn’t work either?
Within Windows (and Linux, under certain circumstances), pings are special and require escalated privileges. You must run The Dude (either the application or the service, if it’s running in service mode) as an Administrator. If you aren’t running as a service in Windows Vista (Server 2008) and newer, this means you must actually “Run as Administrator” so that you get a UAC Escalation prompt, and choose yes. If you are running as a service, merely having the service run as a user with Administrator permissions is sufficient.
Server 2003 didn’t have UAC, and thus the Administrator escalation was not required for sending pings (merely running within a user that has Administrator permissions was sufficient in Server 2003).
I have it running as a service or supposedly but how do I make it admin? I ran it as a task as admin last night and it did ping.
will it always autostart as admin priv if as a service? I dont want or need user intervention.