Screensaver fails to unload after applying Support Pack 6 for Netware 6.5

  • 3480310
  • 06-Feb-2007
  • 26-Apr-2012


Novell NetWare 6.5 Support Pack 6
Admin user that is attempting to unlock the console has a default NMAS login sequence other than the NDS login sequence.


ERROR: "The console could not be unlocked. The username or password is invalid" even when both username and password are correct.

With the introduction of NetWare 6.5 SP6 the screensaver utility has been made Universal Password aware, thus making it NMAS aware. If the user that is used to unlock the console has a default sequence defined other than "NDS", then the screensaver will not unlock the screen and will report the generic error:
This behavior is the same regardless of whether the option to enable Universal Password is turned on or not.


The issue has been reported to engineering.
In the meantime you can change the default sequence for every server operator that needs to unlock the screensaver. It's possible to specify either "No login sequence" or the "NDS" login sequence. Notice that this only means that when this user wants to login with a Novell client with another sequence, he needs to specify it in the NMAS tab.


Reported to Engineering

Additional Information

If the user you are trying to authenticate with is configured to use Universal Password, you could be affected by a different issue, the one described in KB 3924024. In this case, you can enter the command:
load scrsaver enable universal
to instruct scrsaver.nlm to use the Universal Password instead of the traditional NDS password.