Kent Peacock <[email protected]> wrote: On 05/11/09 05:07, Sean Clarke wrote: >> >> OK, found and fixed! >> >> Caught me out, but simple enough - another machine on the network had >been >> rebooted and came up with a DHCP server enabled - the IP address range >was >> in the same network mask, but non conflicting (one had ascending and the > >> other had descending allocations)... >> >> Anyway, stopped that and they all burst into life. >> >> Apparantly the other machine was restarted a while ago, however the >problem >> has only just surfaced - I guess perhaps all there leases expired withing >a >> closly knit time range (?). > >I don't quite understand how this could cause 26D, unless the Sun Rays >were connecting to the wrong server. Is that what happened?
The server that was restart (and had the 2nd DHCP server running) was an "old" Sun Ray Server (SRSS services were not running), hence I suspect the DHCP messages had Sun Ray params that pointed to itself - with no Sun Ray Server running the users all got a 26D, except the ones that were luck enough to still have the "correct" DHCP lease and Sun Ray DHCP params. Make sense? Morale of the storey - always tidy up properly, problems can surface very much later! -- -- Regards Sean Clarke --------------------------------------------- SEC Consulting Limited Phone: +44 (0)23 8040 5599 Website: http://www.sec-consulting.co.uk Email: [email protected] SEC Consulting is a Sun Partner Advantage Member: Sun, keeping 10 moves ahead. http://www.sec-consulting.co.uk/Sun/index.html _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
