@MG11
If we read through all the comments in the post that you found, you will agree that the issue is caused by network settings on the OS.
The Veritas TN that I quoted from on 04-25-2011 can be found here: https://www.veritas.com/support/en_US/article.000009888
Solution
This problem was resolved on multiple client hosts by stopping and restarting the inetd process via the Service Management Facility. On two of the client hosts, the entire host needed to be rebooted to resolve the problem.
The precise root cause was not available, but it is likely that at the time inetd was last started, there was an unusual and incompatible combination of TCP and/or kernel tunables in place. One or more of the setting must have been changed to a compatible value before the problem was noticed because all settings appeared normal during debugging. However, the restarted instance of inetd clearly picked up a better environment than the prior instance.
There is nothing from NBU that we can do to fix this.
If the customer does not want to reboot, they need to log a call with Oracle to troubleshoot.
Herewith a good explanation of Status 24: https://vox.veritas.com/t5/NetBackup/Error-23/m-p/738836#M201891
