Admin Server 4 fails to start up with new Internet Protocol (IP) address

Question

By default, the Netscape Admin Server 4.x uses the Internet Protocol (IP)
address that was entered in its configuration at the time the server was
installed. However, if a system administrator decides to change the IP address,
the server will fail to start.<BR>
<P>
The following is an example of the error message:<BR>
<P>
# ./start-admin
Info: Cache expiration set to 600 seconds
Netscape-Administrator/4.0 B99.035.2034
startup failure: could not bind to port 4050, IP address 208.12.45.56 (Invalid
Argument)
The error log will show:<BR>
[29/Oct/1999:11:32:58] info: successful server startup
[29/Oct/1999:11:32:58] info: Netscape-Administrator/4.0 B99.035.2034
[29/Oct/1999:11:32:58] failure: startup failure: could not bind to port 4050,
IP address 208.12.45.56 (Cannot assign requested address)
<P>
In addition, if the system administrator manually clears the IP address for the Admin
Server in Console (by clicking the Configuration tab, clicking the Network tab,
selecting Process Settings, and then selecting IP Address), the server will
also fail to start. The following are examples of the error message and error
log entries.
<BR>
# ./start-admin
Info: Cache expiration set to 600 seconds
Netscape-Administrator/4.0 B99.165.2023
startup failure: could not bind to port 4100, IP address
(Directory open error)
The error log will show:<BR>
[03/Dec/1999:09:32:43] info: successful server startup
[03/Dec/1999:09:32:43] info: Netscape-Administrator/4.0 B99.165.2023
[03/Dec/1999:09:32:43] failure: startup failure: could not bind to port 4100,
IP address (Error 0)
<P>
These problems affect both Admin Server 4.0 and 4.1.
<P>
(See attachment)

Answer 1

Hi Laurent,
although I was given the advice earlier that I should simply take the machine back to the shop, or call the help centre, I ended up just praying that it would be OK.  A couple of days after I posted the message I think there was an update to download and install, just a regular one from Apple from the Software Update option for the operating system or it may have been one for Final Cut Pro X, and once it installed I never had the problem again, so my prayers were answered.
It was pretty scary at the time because I thought it must be some hardware malfunction, but because it was resolved through an update it suggested it was a software issue.  Hopefully it is the same with you.
I'm now running 10.7.2 and have had no recurrence of the problem in many months, thankfully.
It might have nothing to do with it, but the only other two things that may have somehow caused errors in the system startup (and I doubt these will be "unrelated" to people who know how computers work better than I do, but I feel I should mention them just in case), but I also updated Final Cut Pro X from a glitchy version to version 10.0.2 around the same time, and I also had an application installed which didn't function correctly in OS10.7 called PowerController (a simple app that can start up the computer at a set time and play music from iTunes as an alarm clock) and it was in the group of apps that were set to start at the starting up of the computer.
Anyway, I hope your problem is resolved as easily.  Pray about it too!