ORIGINAL PROBLEM: I did a complete reinstall of
> DU 4.0B (the system was originally 2.0). We access the
> Alpha 3000 Model 400 using Exceed on Win95 machines. Exceed
> now fails (did work under OSF 2.0) saying
> XDM session declined
> using ps -A I do not see xdm, when run by typing xdm the process
> lives until someone tries to connect with a xwindow, then
> xdm dies. Telnet and ftp continue to work fine.Liz Stewart <liz_at_ece.neu.edu>
The answer below solved my problem, thanks to:
Liz Stewart <liz_at_ece.neu.edu>
Harvey Rarback 630-252-0427 <RARBACK_at_cars3.uchicago.edu>
EMMANUEL CHOQUET <ics_at_cica.fr>
from Exceed group on your PC launch Xconfig
click on Communication Icon
select configure xdm-query
remove xdmkey from key field
end select OK
This may help also, thanks to:
Chan Shih-Ping <matcsp_at_math.nus.sg>
If you are using dtlogin (as XDM host) or xdm itself check the Xerror
file (this is in different places depending whether you are using
dtlogin or xdm). E.g. on my system using dtlogin, the error file is
/var/dt/Xerror. This usually indicates why the XDM session was rejected.
One of the most common reasons for XDM rejections is reverse IP lookup -
the XDM host is trying to convert the requesting hosts IP address
back to a domain name. In a PC-type environment you may not have setup
your nameservers to reverse map IP addresses to domain names. Here's
a typical error message if this is the case (extracted from my Xerrors
file):
Fri Mar 21 13:43:37 1997
error (pid 541): Cannot convert Internet address 137.132.81.48 to host
name
Thank you to all who responded and helped it is really appreciated.
Brian Hinderliter
Received on Mon Mar 24 1997 - 16:58:12 NZST