Discussion Locked

Netware server stuck on screensaver

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I have a Netware 5 server that has the screensaver with password protection activated. Right now, the screensaver is moving around, the server is functioning fine. There are no abends in the abend.log. There are c0001001 errors in the error log, but the fixes for this need to be done from the server, which I can't get into. When I press any key on the keyboard I just get a beep. It does not come up with a login screen. When I press the ALT button, it does display the grey bar at the top with the screen discription, but this is the only button that will do anything except beep. I have Groupwise, ARCServe and several other programs with open databases, so I don't want to just shut off the server. Does anyone have any suggestions?

6 replies

by budthegrey

Download and install the AdRem free remote console program (http://www.adremsoftware.com /freecon/index.php.

You can install it from a workstation, and it works quite well. I'm not sure it will get you past the locked screen saver, but it's worth a shot. If nothing else, the utility is free and will be useful later.

by gr8dane

Thanks for the advice. I am already running Freecon and it behaves in the same manner that the keyboard does. It just beeps when I tap keys. I have also tried to login using the portal, but it just locks up. You're correct that the utility is useful. I use it because it has better security than Novell's Remote Console.

by weluvm$?

OK, a 'get out of jail free' card?

Why not submit a mini arcserve backup (just 1 file will do) and as a post command issue the 'restart server' command. At least this should bring the server down and up gracefully...

by gr8dane

I like the idea. I thought for sure this would be my answer. Unfortunately, when I went into Arcserve, I cannot do anything with this particular server. After checking my logs, it appears that Arcserve isn't running properly. It looks like I'm just gonna have to down this sucker, unless anyone else has an idea?

by gr8dane

Well, I think I came across my answer. This all happened soon after I had rebooted the server and ran a DSRepair. I believe the DSRepair may have still been running when the screensaver kicked in. See TID10052417 for the explanation from Novell if you're interested. They say the only thing I can do is a hard shutdown. Thanks for your ideas and learn from my mistakes. Thanks again.

This discussion is closed to new replies.