| On the VMS machine, I changed the VMS password and opened ADMIN and
changed the password there as well.
On the Windows 95/eXcursion 2.1 PC I opened the eXcusion control panel,
selected the accounts tab, selected the machine, entered a new password
clicked OK and exited. The new password would not take, and of course the
old password would not let me back into the VMS machine.
Not until I deleted all of the applications associated with machine with
the new password, and re-installed those one-by-one was I able to access
the VMS machine again.
Is there a `trick' to updating passwords on the server and the PC w/o
tempting fate?
Bruce
|
|
Here's a bit of inside information that may help you understand
excursion's current (and a bit deficient) method of handling passwords.
Note that in the excursion control panel, there are two kinds of
apps you can define. One kind is "predefined x apps" and the other
is "custom x apps".
Try defining a predefined x app. After the system icon appears, click
the right mouse button on it and look at its properties, and go to the
shortcut tab and examine the resultant system command. For example,
suppose you set up the predefined "terminal" application. The
line shown in the properties box will look something like this:
D:\s\recent\x86\launch.exe -Xapp -alias 'osman osfwnt'
$create/term/detach
Notice how the line includes "-alias" and then my username osman and
then my unix system node name which is osfwnt.
Compare this with the resultant line if you define a custom x app
instead of a predefined one. Here's what mine looks like:
D:\s\recent\x86\launch.exe -Xapp -t TCPIP -m rexec osfwnt -l osman -pwd
!MTQi$$cPlM $ create/term/det
Notice how there's no -alias this time, and how there's -pwd followed
by an encoded password.
This is the crucial difference ! Since the password is stored right in
the command string for the custom case, that means if I change my
password over on unix system osfwnt, and I change the password in my
excursion control panel (in the accounts tab) under account "osman
osfwnt" the custom app will no longer start since the old password is
still stored on the command line in the shortcut.
But the predefined x app will magically continue to work, since its
command line points to the account "osman osfwnt" indirectly, and hence
it will see the password change.
In the future, we hope to change excursion so that the custom apps
define their command line the same way the predefined x apps do. But
for now, if you change your password on the host system, you'll need
to redefine your custom x apps, but not your predefined x apps. So
it's better to use the predefined ones if possible. And of course for
either type you need to change the account password in the excursion
control panel.
I hope giving some of this inside information helps you manage things
better at your end.
/Eric
|