[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

1976.0. "Remote login session problem" by PVX::VANSICLEN (Garrett in The Mill. 223-6310) Thu Dec 28 1989 12:06

    I am trying to run my entire session remotely (V1.0).  What I am
    currently trying top do is -
    
	* In SYS$STARTUP:DECW$STARTAPPS.COM on the workstation, I have
    	  commented out RUN SYS$SYSTEM:DECW$STARTLOGIN, so that only the 
    	  X-server runs, no login process.
    
    	* Then on the host I do a SET DISPLAY/CREATE/NODE=workstation then
    	  run DECW$STARTLOGIN.  A connection is made to the workstation, but 
    	  login window never comes up.
    
    Any ideas as to what I am doing wrong?  DECnet database, GBLPAGES are
    fine.
    
    garrett
T.RTitleUserPersonal
Name
DateLines
1976.1Not supportedDECWIN::FISHERBurns Fisher 381-1466, ZKO3-4/W23Thu Dec 28 1989 12:299
You probably have not enabled the remote node on your server.  Add a file
called DECW$SERVER_ACCESS_TRUSTED.DAT to sys$manager, and make it first and
only line be

DECNET remotenode SYSTEM

That should do the trick.  (Not supported, you understand...)

Burns
1976.2/perm too?AZTECH::LASTOVICATime to cross the wild meridianThu Dec 28 1989 13:252
I also find that I have to SET DIS/CRE/PERM/NODE=foo before I run
DECW$STARTLOGIN for it to work (notice the /PERM).
1976.3"server_access_trusted" v.s. "server_access_allowed" "server_access_allowed"PVX::VANSICLENGarrett in The Mill. 223-6310Thu Dec 28 1989 14:557
I didn't find I had to add the /PERMANENT - yet.  DECW$STARTLOGIN starts it's 
own process and the login session seems to hang around just fine.

What is the difference between "server_access_trusted" and 
"server_access_allowed"?  I was told there is a difference.

garrettt
1976.4Allowed vs. Trusted34339::BRYSONThu Dec 28 1989 16:2620
The allowed list are the transport/node/user combinations allowed to establish a
connection with this server.

The trusted list are the transport/node/user combinations which may modify the
allowed list.

It is important to have the node/user name in the TRUSTED list because 
DECW$LOGINOUT.EXE will change the allowed list of the server once the user
logs in.  Without these files, the only user which may establish a connection
to server is the SYSTEM account on the local node.  You will need to create the
trusted file on the system where the server is running an place an entry in
the file that looks as follows:

* NODE USERNAME

Where NODE is the node where DECW$STARTLOGIN.EXE is executed and
USERNAME is the username of the process which executed DECW$STARTLOGIN.EXE.

David
1976.5Blocks local usage11SRUS::PUDERKarl Puder, VAX APL Project LeaderWed Feb 21 1990 15:5213
My experiments with this have demonstrated that having such a file removes the
implicit "* 0 SYSTEM" (or maybe it is "LOCAL 0 SYSTEM") that the server has
built-in.  So if you want to be able to prod the workstation and dynamically
switch between local login and remote login, you need to add an explicit

LOCAL 0 SYSTEM

to the file, as well as

DECNET remotenode SYSTEM


	:Karl.