[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

3451.0. "X Toolkit error accessing remote application!" by HARDY::EARLE () Wed Oct 10 1990 11:33

 
    I'm having a problem accessing a DECwindows application located on a
    remote cluster from my workstation.

    I have defined the DECW$DISPLAY logical to my workstation (DUKEOF::) and 
    I have defined in the DECwindows Session Manager "Customize Security" 
    window the following:

            Node: Remote cluster name(s)
        Username: Earle          
       Transport: DECNET

This is what happens when I try to run the application:

$ @ipse$examples:ipse
Xlib:  connection to "DUKEOF::0.0" refused by server
Xlib:  Client is not authorized to access server
X Toolkit Error: Can't Open display
%DWT-F-DWTABORT, xtoolkit fatal error
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC

                                                           0012EEBF  0012EEBF
                                                           0012EEF3  0012EEF3
                                                           0012ECD3  0012ECD3
                                                           0012EDA3  0012EDA3
                                                           00118905  00118905
IPSE_MAIN       main                            24920      0000005F  0000E30F
$


What am I missing?

Thanks,
Ed

T.R	Title	User	Personal Name	Date	Lines
3451.1	Customize where you're pointed to	TOOLEY::B_WACKER		`Wed Oct 10 1990 12:23`	4
	You need to customize security in the session manager on the REMOTE node pointed to by your set display to allow you in. Bruce
3451.2	I did that, what next?	HARDY::EARLE		`Wed Oct 10 1990 13:01`	11
	Hi Bruce, I may not have made myself clear, but the Session Manager that I had accessed to "Customize Security" was the remote node DUKEOF:: Using a terminal window I SET HOST to the remote cluster and there is where I defined DECW$DISPLAY as DUKEOF:: and where I ran the DECwindows application. I think that's what you are suggesting. Ed
3451.3	Too much security info?	LOWELL::KLEIN		`Wed Oct 10 1990 13:17`	11
	You may have bumped into the character limit to the security list. All text in all the security entries, TOTAL, must be less than (I think) 255 characters. Try getting rid of all the security entries and add "* * *". See if it works then. BTW, I always do DEFINE DECW$DISPLAY node::0, rather than just node:: I don't know if this makes a difference, too. -steve-
3451.4	nodes in network database?	R2ME2::OBRYAN	Instant Gratification takes too long	`Wed Oct 10 1990 13:52`	8
	re:.0 > Node: Remote cluster name(s) > Username: Earle Are the client machine node names registered in your display machine's NCP database ? (If your cluster has outgoing alias, the cluster name will need to be in the database.)
3451.5	Cluster alias isn't check for DECwindows.	IO::MCCARTNEY	James T. McCartney III - DTN 381-2244 ZK02-2/N24	`Wed Oct 10 1990 13:59`	8
	I remember another discussion in this notes conference stating that cluster alias is not checked when starting decwindows connections. You have to register in the security pulldonw each node of the cluster from which connections will be started. James
3451.6	It woiked, it woiked!!	HARDY::EARLE		`Thu Oct 11 1990 09:28`	5
	Getting rid of all security entries, replacing them with "* * *" did the trick. Thanks a million. You're a life saver or at least a time saver. Ed
3451.7	Please don't leave your workstation completely unprotected!	DECWIN::FISHER	I like my species the way it is" "A narrow view...	`Thu Oct 11 1990 15:32`	9
	Wait a second...that does not prove anything...it just says there is no security whatsoever now. It is a good test, but don't leave it that way. I bet that your client node is a cluster and that you had specified the cluster alias in the security list. Am I right? You have to specify each individual node that the connection might come from. If not that, then I bet the client name was not in the server's decnet database. Burns
3451.8		HKOVC::TERENCE	From Middlesex, UWO	`Fri Oct 12 1990 03:24`	5
	Also, make sure that you didn't add :: after the node name. -Terry
3451.9	Come on now	LOWELL::KLEIN		`Fri Oct 12 1990 11:42`	12
	> -< Please don't leave your workstation completely unprotected! >- > >Wait a second...that does not prove anything...it just says there is no security >whatsoever now. It is a good test, but don't leave it that way. I still think they hit the character limit for security entries. It will do no good to chide people for unprotecting their workstations if it is the only workaround for this bug in the Session Manager. The real question is: Has the bug been fixed yet??? -steve-
3451.10		LESLIE::LESLIE	Andy Leslie, CSSE/VMS	`Fri Oct 12 1990 19:11`	8
	No, using * * * is a VERY BAD IDEA. It allows ANYONE, ANYTIME, ANYWHERE to do things on YOUR screen. If there are bugs, QAR 'em. If there is a workaround, use it until its fixed. /andy/
3451.11	Yes and No	HARDY::EARLE		`Tue Oct 16 1990 09:14`	7
	In response to NOTE.7, yes you're right on the fact that there is no security now. But, I did include the name of each individual node that the connection might come from. It seems to me that the client names not being in the server's decnet database is more than likely the problem. I'll check it out and confirm.
3451.12	DECnet database list was the problem	HARDY::EARLE		`Tue Oct 16 1990 10:38`	11
	That's what it was. My workstation DEcnet database did not contain the client node names. After adding them to the database and the workstation "Authorized Users" list, I'm able to run the application remotely with no problem. By the way, I did remove the "* * *" entry. Thanks again for all the help. Ed