Conference bulova::decw_jan-89_to_nov-90

    The default 'trusted host' list contains just "LOCAL 0 SYSTEM" (or
    something similar.  What you want to do is create a file,
    SYS$MANAGER:DECW$SERVER_ACCESS_ALLOWED.DAT, on your workstation with an
    entry such as "DECNET LEVEL OSMAN".
    
    James

	So when should we modify the ACCESS_ALLOWED file, and when should
	we modify the TRUSTED_ACCESS file ?

	How are they different ?
[
/Eric

  If I remember correctly the ACCESS_TRUSTED file allows those connections
to modify the host list, whereas the ACCESS_ALLOWED file does not.

  I has been my experience that pretty much all the connections should be
in the ACCESS_ALLOWED file only.  In fact you really don't need to have the
ACCESS_TRUSTED file unless a client needs to modify/maintain the host list
for other connections.

					-=> Jim <=-

    o.k. I've finally been able to start a login box on the server screen
    of my choice from the client of my choice BUT...
    
    I must have special privileges on the client, because apparantly
    DECW$STARTLOGIN requires privileges.
    
    But I've heard a rumor that it's possible to do without special
    privileges. Something about sending the name of the WS device (the one
    you created with SET DISPLAY/CREATE) to the job controller's mailbox.
    
    My real goal here is to speed up our slow VS2000's in our lab by
    presenting the login box from our big fast machine, on the VS2000 which
    would just be the server.
    
    But I don't have special privileges on the big machine (just username
    and password is what I have).
    
    So, how can I get the mailbox name of the job controller ?  What
    exactly is the message I should send it to tell it the WS device name?
    Will this really succeed in working ?
    
    Thanks.
    
    /Eric

    The job controller mailbox is MBA1.  This string is the value of
    the symbol SYS$C_JOBCTLMB.  However, it is world no access; otherwise
    there would be a massive security hole.  For the record, the message
    is a word containing MSG$_TRMUNSOLIC, followed by the device name.
    There is some possibility that it is in ASCIC -- I don't remember for
    sure, and I can't get to the listings right now to check.

    
    So the question remains:
    
    	Is there a way to fire up a login box from a client to a server
    	without having special privileges on the client ?
    
    	I'd like to log in on the client and type something that causes
    	the login box to appear on the server.
    
    	By the way, I DO have privs on the server.
    
    	Thanks.
    
    /Eric

    this might be one way of avoiding the problem (it still probably
    involves the system manager to set a couple things up):
    
    shouldn't the startup of the remote session manager be part of the
    server's booting process?  in that case, couldn't you have decwindows
    start up (without a session manager) on the vs2000, then create a batch
    job in a queue which is accessible to the vs2000, but which runs on the
    big vax, which will run the loginout process with the display set as
    discussed in the previous replies?
    
    i am hoping to do something similar here (same configuration, same reason)
    after we have upgraded to vms 5.3, and ultrix 4.0.
    
    			--dd

>    	Is there a way to fire up a login box from a client to a server
>    	without having special privileges on the client ?

No there is not.  You could install DECW$STARTLOGIN with privs and then put an
ACL on it to control access to those who need it.

It's a bit incongruous.  A new product which I feel I better not name
here (we're not quite out yet) lets us say "create LAT X session...", which
causes the decnet node of your choice to send you a login box to your screen.

You don't need to be privileged to get this service.  So it seems over
restrictive that you need to be privileged to do it from a "regular"
workstation.

Thanks.

/Eric