| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 925.1 | Do you set security? | AVIATE::SHAH | Yanks in '89 | Mon Jun 12 1989 17:04 | 7 |
|
Do you set security on your VMS machine? This can be done
under the customize menu item in the Session Manager.
-PS
|
| 925.2 | Security is set | BDWISR::HEAFEY | How's the guy in the audience? | Tue Jun 13 1989 08:35 | 7 |
| >> Do you set security on your VMS machine? This can be done
>> under the customize menu item in the Session Manager.
Yes. Sorry for not mentioning that.
Dave H.
|
| 925.3 | Another possibility | AVIATE::SHAH | Yanks in '89 | Tue Jun 13 1989 08:44 | 6 |
|
Is your VMS node set properly in the NCP database on your
Ultrix machine?
-PS
|
| 925.4 | | JAMMER::JACK | Marty Jack | Tue Jun 13 1989 09:18 | 3 |
| For an Ultrix to VMS connection, you need the UID in the username part
of the VMS-side authorization. It's often easiest to specify node::*.
|
| 925.5 | ::0 was needed | BDWISR::HEAFEY | How's the guy in the audience? | Tue Jun 13 1989 11:33 | 18 |
| Got it to work! Not sure if this is the supported way but, it worked
for me.
On the VMS node:
I put ultrixnode::* in my security database per .4.
On the ULTRIX node:
setenv DISPLAY mystation::0
/usr/bin/dxmail
The "::0" was the key.
Thanks for all your help,
Dave H.
|
| 925.6 | two security entries...uid and name | R2ME2::OBRYAN | When in doubt, let the user decide. | Wed Jun 14 1989 22:33 | 7 |
|
> For an Ultrix to VMS connection, you need the UID in the username part
> of the VMS-side authorization. It's often easiest to specify node::*.
I've found that SOME applications require both the user name AND uid need
to be defined in the security list (e.g. ultrix::user, ultrix::321).
Some security-conscious types will find node::* to be a security hole.
|
| 925.7 | Related issue but only on VMS... | TOOK::L_OUELLETTE | | Fri Jun 16 1989 14:25 | 19 |
| I have a problem that is somewhat related and was hoping to find out if anyone
has any ideas... when I run some applications (e.g. DECW$CLOCK) with
my security set to: myworkstation-node::myaccountname (using myworkstation-node
and logged in as myaccountname) everything works fine - as to be expected.
The problem is that if I, from a DECterm window, do a set host back to
myworkstation-node and log in as SYSTEM, define my security as:
myworkstation-node::SYSTEM, I get:
XIO: non-translatable vms error code: 0x2DBA002, vms message:
%decw-e-cnxabort, connection aborted
%XLIB-F-IOERROR, xlib io error
%TRACE-F-TRACEBACK, symbolic stack dump follows
Interestingly enough, if I setup my security as *::SYSTEM, everything works
just fine - and yes I do have decw$display defined as myworkstation-node::0.
Any ideas would be greatly appreciated!
|