🚀 go-pugleaf

In article <1dc5cdINNkdl@fnnews.fnal.gov> shah@fnalb.fnal.gov writes:
>In article <1d9meiINNfh@sacomm.schulz.unisa.edu.au>, cowleym@sacomm.schulz.unisa.edu.au () writes:
>|> 
>|> Trying to run any X-windows application from a window on our Ultrix machine, 
>|> on my VMS VAXstation, over DECNET, as myself (not the superuser) I always 
>|> get the message:  

>|> Xlib:  connection to "saccs1::0.0" refused by server
>|> Xlib:  Client is not authorized to access server
>|> X Toolkit Error: Can't Open display
>|> 
>|> I am running Motif on a VAXstation 3100.
>
>On you VMS system type following command:
>
>$ set display/create/node='nodename'/trans=decnet
>
>and then start Xapplication on remote system.
>
>Hope this helps :-)

Unfortunately I don't think it will! The VMS command:

SET DISPLAY/CREATE/NODE=nodename

sets the DECW$DISPLAY logical on the machine which is going to run
the client so that the client can find out which machine to display to.
The information from the previous poster doesn't make sense therefore.

It sounds to me like one of two things:

(1) Is the VAX you are trying to display to running VMS or EWS (ie
    only running a server and a scaled down version of the VAXeln O/S)?
    If so certain default files have to be set up correctly for you to
    display remotely - it's all badly ;-) explained in the manual!

(2) When you log into your Ultrix machine you don't by any chance log
    into another VAX along the way do you? I've found I can't display
    remotely if I do this - well written DEC software....

One thing that is always useful is to go into session manager security
and put these 3 entries in:

Node Username Transport
---- -------- ---------
*    *        *
*    *        DECNET
*    *        TCPIP

This (for yet another unknown reason) is the most likely way to connect
to a VAX (just putting * * * doesn't always work....)

Hope this helps,

Mark Parsons.