Cannot start session manager using Exceed

[Qing Zhu]

Hello,
I'm having a problem starting a remote session on a HP Alpha running tru64 Unix v4.0g.
My current configuration is: networked PCs running Exceed 7.0 for NT and XDMCP broadcast.
Problem description:
I have several Alpha workstatiions running tru64 unix v4.0g. When running "XDMCP broadcast" these systems
offer themselves as willing to manage the window session and present a logon screen when selected. However after
the username and password are entered, I receive the following messsage: "cannot start session manager from remote client - access denied".
I'm almost sure that the problem reside in the Alpha side, the session manager won't start from remote unless some configurations was set up properly.
I'm wondering if anybody encountered a similar problem before and how you tackle this please email to qing.zhu@bctransco.com

Many thanks,
Qing zhu

[Ravi_8]

Hi

have added 'ptys' at the end of /etc/securettys file

[Michael Schulte zur Sur]

Hi,

you will have to add the client ip address like:
10.0.0.1:0
pchost:0
to /etc/securettys

either in numeric form or in alphanumeric form.

Michael

[Ralf Puchner]

As written in another posting here with the same question:

you must configure exceed properly to work without a problem. There are some security settings which must be changed within the exceed setup menu. As I remember it was a edit field containing an xdmcp key which must be empty.

Other X Server software works out of the box without this change (e.g. excursion etc.)

Be sure the ip nameresolution works and if you will login as root you need an entry within /etc/securettys

[Qing Zhu]

Thank you all for the quick responses.

Actually I already had ptys and hostname:0 in
/etc/securettys, and my XDMCP key field is also empty in Exceed configuration. I'm running KDE desktop on the same machine on root account and have no problem at all when login as root on Exceed.

In addition, I can start any other X applications except that session manager, which calls /usr/X11/xdm/dxsession. It might
be some configuration files related to this "dxsession" that need to be changed.

[Ralf Puchner · Accepted solution]

in case of xdm use:

$HOME/DXsession
*security: false

[Pieter 't Hart]

first check status of X-access
xhost
if disabled change with
xhost + # -> free for anyone
or xhost + # X-access for this host

Pieter

[Qing Zhu]

Thanks Ralf, problem solved.