There is a bug in CBOS 2.4.1 that causes EXEC and ENABLE passwords set with the set password command to be stored in lower case even if you type in upper case characters. Passwords are not affected during a CBOS upgrade. It only affects passwords set by command.

If you are on CBOS 2.4.1 and had had to re-type your EXEC and/or ENABLE passwords for some reason, your passwords won't be correct if you used upper case characters. The password if there, it just gets stored in lower case.

For those of you who want to restore passwords that were upper or mixed case, there is a workaround (albeit a long one).

Open nscfg.cfg with an ACSII text editor. Find the lines that read:

NSOS Root Password =

NSOS Enable Password =

Using an ASCII Character Chart, determine what the stored password should be.

The password is stored with the characters shifted backwards by two. For example, if the password you want is 1MyPasswd, you would edit the Password in the .cfg file to read /KwN_qqub.

Save the changes to the .cfg file.

Enable TFTP on the 675:

set tftp enable

Connect to the 675 with a TFTP client. Make sure to put the client into ascii (netascii) mode.

Do a "put nscfg.cfg".

The nscfg.cfg file will be uploaded to the 675. If you are connected to the 675 on the serial port, you'll see a confirmation message and be asked to reboot. You MUST reboot for the save configuration to take effect.

Be sure to either disable TFTP on your 675 or at least set it so that it can't be accessed from the internet.

set tftp disable

or

set tftp remote 10.0.0.2