I work at a large corporation where we use many legacy systems. To note some of the systems: HP-UX 10.20, Windows 2000, VMEBus systems, systems designed 30+ years ago that do not communicate via TCP/IP protocols, and more.
Throughout the work week we are constantly plagued with these legacy systems losing communication with one another. Usually rebooting a system to try to restore communication is the last approach. It has become a common belief that rebooting a system is just a “fix-all” for ignorant co-workers. I was wondering, if there is ever validity to rebooting a system (legacy or not) to restore a failed line of communication?
I realize renewing IP addresses in windows should effectively restore network communication; but is there the possibility of a deeper problem in the underlying operating system that could become corrupt and need a reboot? A failed socket that times out, doesn’t close, or maybe doesn’t try to reconnect?
It seems to me rebooting would be a viable resolution when having such a complex network of mismatch systems. But (at least at my workplace) when a system is rebooted, and everything magically starts working again it’s always a “coincidence”; never a solution. Thoughts?