I had the exact same problem as the OP. I installed VMware appliance, and setup on one segment of our network 10.17.x.x for testing purposes. Everything was working fine and I could access the web interface remotely fine. I moved the server to it's rightful place on the network 10.16.x.x and I am no longer able to connect. https:// does not work and when Zenoss starts up, you can see that when it tries to determine the network settings for eth0: it tries to ping the default gateway for 10.17.x.x network. Why would the settings not update correctly? Is there a way to hardcode the IP address into Zenoss via the console??
-------------------- m2f -------------------- Read this topic online here: http://community.zenoss.com/forums/viewtopic.php?p=17880#17880 -------------------- m2f -------------------- _______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
