Xref: utzoo comp.windows.x:27414 comp.os.vms:30782
Path: utzoo!attcan!uunet!munnari.oz.au!metro!usage.csd.unsw.oz.au!decus!taylort
From: taylort@decus.com.au
Newsgroups: comp.windows.x,comp.os.vms
Subject: Re: How to get DECW$STARTLOGIN to work with arbitrary X server
Message-ID: <4723.26ff6b7f@decus.com.au>
Date: 25 Sep 90 04:36:47 GMT
References: <3451@prowest.propress.com>
Organization: DECUS, South Pacific Chapter
Lines: 55

In article <3451@prowest.propress.com>, pan@prowest.propress.com (Philip A. Naecker) writes:
> I'm trying to get an X-terminal up using the DECw session manager.  I believe
> that for what I am doing, I can reproduce this problem on several different
> manufacturer's Xterminals, ...
>
(stuff deleted ...)
> 
> 4.  At that point, since we have a login banner up, one would think we could
> certainly log in and everything would be peachy, right?  Wrong.  Instead, after
> we log in the following occurs:
> 
> 	1.  The login banner and dialog box disappears.
> 	2.  The cursor changes to a watch.
> 	3.  The server appears to hang.
> 	4.  The _WSAn: process errors out and re-creates itself, apparently
> 	    ad nauseum.
>	etc. etc. ...

I cannot guarantee that I have the solution to your problem,
but I do know for a fact that this symptom occurs on an NCD17c.
(There, I've mentioned a name and it didn't hurt a bit.)

The problem is that the DEC session manager changes the
host access list on the server (X terminal) to match the one 
in your saved configuration file. However, it does so only part 
way through the startup. As a result, further attempts to open 
connections fail because you probably do not have your own host
listed as a valid node.

To get around the problem, log in on a VAXstation and use the
customise security menu to add an appropriate host/username
combination, i.e. the one which you will be logging in to.
Then run DECW$STARTLOGIN as usual. When you log in, the
access list will already have you as a valid user for the
purpose of connections.

If you want multiple users to use the X terminal, you may have
to specify a wildcard username. This of course leaves you wide
open for other users from the same host to play tricks on you
by running applications on your screen. It also has implications
for security.

(more stuff deleted ...)
> 
> 3.  I have been told by DEC's customer support that there *is* no correct
> procedure - it is unsupported.  This strikes me as very odd.  I don't see why
> any particular server configuration should work any differently for, say, the
> DECW$CLOCK client than for the DECW$STARTLOGIN client or the DECW$SM client.
> 

This is true in essence. There is a new XDMCP protocol for this
type of remote login function which NCD contributed to the X Consortium.
However, it is not yet widely used and certainly not available under VMS.

	Trevor