Discussion Locked

RConsol p-word manually typed on reboot?

0 helpful
17 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
When our servers go down and reboot themselves after a power outtage, we have had to drive to the individual buildings to type in the rConsole password so that the boot will finish. Is there a way to edit our ncf files so that there will be a password required when remotely using rconsole but without having to manually type in the password at the console during a reboot? TIA!

17 replies

by Scott Lowe

In your autoexec.ncf file, where you load REMOTE.NLM, type the desired password as an option. For example, if you want a password of "pwd" for rconsole, your LOAD REMOTE line would read:

LOAD REMOTE pwd

Enjoy!

Scott

by bruceh

under autoexec.ncf
type the following:
rspx
remote password
rem: use the password that you want in place of password and don't forget to save when exiting.

by markp

While the other two suggestions sometimes work with 5.x there is a more durable 'fix'assuming you are running IP. Either via Rconsole (once you HAVE driven building to building) or at the console type load inetcfg. At the resulting menu select Manage Configuration then Configure Remote Console Access. Set your password here and upon reboot it will 'stick'.

by jimbb

One more thing: if there are two remote statements in your autoexec (ie: once via inetcfg, once via the command itself in autoexec), netware will ask for a password the second time you try to load remote.nlm

by javier

Be sure that you place the Rconsole command before the rspx.

RCONSOLE PASSWORD
RSPX

If you reverse them it will still ask you for a password.

by tparrett

INETCFG is the best solution. INETCFG>Manage Configuration>Configure Remote Console Access. I prefer this method because it doesn't write the rconsole password in the autoexe.ncf file; therefore, providing a "little" more security.

by rogerndgreen

Although all the other answers are correct, it still leaves the password in "plain text". The inetcfg route is marginally more secure than the autoexec route, but even better is to encrypt the remote password, like this:

At the console, type

LOAD REMOTE
REMOTE ENCRYPT

This will then give back the prompt on how to load remote and ask you if you want to add it to the LDREMOTE.NCF file. For exampe:

To use this password use the command:
Load REMOTE -E BDC8DBBD8328222182

Would you like this command written to SYS:SYSTEM\LDREMOTE.NCF? (y/n)

At this point you can do any of the following:
1) Add the line LOAD REMOTE -E BDC8DBBD8328222182 into the AUTOEXEC.NCF
2) Add the line LDREMOTE in the AUTOEXEC.NCF

The remote password is now encrypted.

For Autoexec, also read inetcfg.

Hope this helps

Roger

This discussion is closed to new replies.