[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

314.0. "Can't Run Applications Across the Network" by TLE::AURENZ (Scot, DTN 381-0616, zko2-3/n30) Mon Feb 27 1989 14:28

    
    	I am having problems running DECwindows applications
        across the network. 
    
        On the cluster, I issue the command
    
        $ set display/create/node=maori
    
        and on MAORI, my workstation, I CUSTOMIZE SECURITY and 
        enter my account on all the cluster nodes, i.e.
        
        HANCOK::AURENZ
        ELUDOM::AURENZ
    
    	and so on.
    
        However, I STILL get "Client not authorized" messages when I
        try to run applications on the cluster (e.g., notes/disp=decwindows,  
        lsedit/disp=decwindows)
    
    	My TASK and FAL objects are present, but "secured" as recommended
        by recent VORTEX security procedures.
        
        Am I missing something? Why doesn't this work?
    
        						Scot
T.RTitleUserPersonal
Name		DateLines
314.1cluster alias?PSW::WINALSKIPaul S. WinalskiMon Feb 27 1989 14:576
HANCOK, ELUDOM, etc. are part of the TLE cluster, which uses TLE as an outgoing
cluster alias.  Try adding TLE::AURENZ to the list of authorized sources and
see if that makes a difference.

--PSW
314.2No changeTLE::AURENZScot, DTN 381-0616, zko2-3/n30Mon Feb 27 1989 15:3811
    
    Thanks, Paul, 
    
    I tried this, but it still does the same thing. 
    
    Anything else come to mind?
    
    Perhaps something in my NCP database? Proxies? 
    
    					Scot
314.3do thisSTAR::BRANDENBERGIntelligence - just a good party trick?Mon Feb 27 1989 16:0112
    
    Did you "apply" the security entries you added?
    
    Does your workstation actually know who the cluster nodes are (i.e. are
    they in maori's node database)?
    
    If it still doesn't fly, run the xgethost program (available in the
    unsupported software directories {see note titled "xliddy"}) on the
    local node to display the "real" security information in the server.
    
    						monty
314.4Bingo!TLE::AURENZScot, DTN 381-0616, zko2-3/n30Mon Feb 27 1989 17:0312
> Does your workstation actually know who the cluster nodes are (i.e. are
>they in maori's node database)?

	Aha! This was the problem. I only had "TLE" in my network
	database. I added the individual nodes, and now it works.

	(In fact, I am typing in this note with DECwindows NOTES!)

	Thanks!
							Scot