@sweise I can confirm your observation. Since our Windows servers on foreign IP subnets also have different MS domain or workgroug names, this might also make a difference, however.
This error is filling my dashboard with so many phony device issues that this is really preventing us from putting zenoss into production. Too bad that this issue does not seem to get attention of any of the zenoss developers. Has anyone seen if this is solved in 2.1 Beta? I am not very tempted to spoil my almost stable 2.0.6 version with beta code. Martin geotek.de (http://geotek.de/en) ------------------------ unset -------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=11148#11148 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
