I'm not sure if this is the right place to post this but I just ran into this issue and it took me some time to find the cause. I figured I would share this info in case someone else runs into this weird problem.
First a little background information. I configured SNMP on a few of my printers as a test before I load them all into Zenoss. I enabled SNMPv1 and configured the SET and GET community strings. I also disabled the default "public" string. I then added these printers to Zenoss and began playing with them. Soon after we noticed these printers began to show as "offline" in our print server (Windows Server 2003 R2). After scratching my head for a little while thinking it had to be a driver issue I realized that this started happening right after I configured SNMP. Come to find out that this is being caused by a bug in Windows Server 2003 SP2. You can find more information here: http://support.microsoft.com/kb/946198 I didn't want to install the hotfix so I disabled SNMP on the printer port as shown in the workaround section. As soon as I did this the printers came back online. While doing that I noticed that the printer port was trying to use "public" as a community string. Since I disabled the "public" community string in the printer's SNMP configuration, that caused it not to respond and go offline. It looks like if I either enable the "public" community string on the printer or if I change the community string in the printer port this issue will go away but I'm not sure yet. I will test that and report back if it works. Anyway, I hope this information helps. -------------------- m2f -------------------- Read this topic online here: http://forums.zenoss.com/viewtopic.php?p=35422#35422 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
