<div>
No UPS. There was one at one time, so that is something i will look into.
</div>


<div>
That was it. There were two UPS boxes under the table where the server was located, and nothing was plugged into either one. When I moved the server, I disconnected everything from the back of it without paying attention to details, and did not notice that one of the connections was a serial line running to a UPS. I plugged the UPS into a wall socket and connected the serial line and the server then stayed up. My guess is that the batteries in the UPS had failed, and nobody wanted to spend any money on a server that would only be briefly and infrequently powered up on the rare occasions when it was needed.
</div>


<div>
<div class="content wysiwyg-content">
I have a Netware 3.12 that worked fine until I shut it down. It is normally not left on, but booted on occasions when the old data on it is needed, then shut down. Today was different. I shut it down by the normal proper procedure, moved it to another room in the building, and restarted it. There were no workstations running when it booted. The the last thing it does when booting is LOAD MONITOR. <br />
<br />
My workstations wouldn't connect. When I shut down the monitor, I found that the server was down, with a message on the screen like this:<br />
<br />
1/21/09 9:34:20 PM: 0.0.0 Down file server requested by user MLI station 0<br />
<br />
If I shutdown the monitor at the earliest possible moment, I can see the shutdown message spontaneously appear about 15 seconds after I close out the monitor.<br />
<br />
This happens quite regularly on every boot now. I find that if I beat MLI to the punch by downing the server myself, the shutdown command from MLI still happens, but it produces an already-down message.
</div>
</div>


I have a Netware 3.12 that worked fine until I shut it down. It is normally not left on, but booted on occasions when the old data on it is needed, then shut down. Today was different. I shut it down by the normal proper procedure, moved it to another room in the building, and restarted it. There were no workstations running when it booted. The the last thing it does when booting is LOAD MONITOR. 

My workstations wouldn't connect. When I shut down the monitor, I found that the server was down, with a message on the screen like this:

1/21/09 9:34:20 PM: 0.0.0 Down file server requested by user MLI station 0

If I shutdown the monitor at the earliest possible moment, I can see the shutdown message spontaneously appear about 15 seconds after I close out the monitor.

This happens quite regularly on every boot now. I find that if I beat MLI to the punch by downing the server myself, the shutdown command from MLI still happens, but it produces an already-down message.

Netware 3.12 server spontaneously downing itself - how do I keep it up?

NetWare is a computer network operating system developed by Novell, Inc. It initially used cooperative multitasking to run various services on a personal computer, using the Internetwork Packet Exchange (IPX) network protocol. It is hardware-independent, running on any suitable Intel-based PC compatible system, and a wide range of network cards. Products inclue NetWare Directory Services (NDS), a global directory service similar to Microsoft's Active Directory; GroupWise, an email system; ZENworks, an application configuration suite; and BorderManager, a security product. Open Enterprise Server, the current iteration, runs on a SUSE Linux Enterprise Server.