Remote X Login on Tru64 5.1B

[Alexey Borchev]

I've got Exeed X Server on my PC, and trying to start X session onto Tru64 box.
I's operating OK with Tru64 4.0f & 5.1A
It does not work on 5.1B - neither PK2 nor PK3.
It does not show login prompt - just waits 2-3 sec and return to Host selection screen.
Both hosts are alive, perfectly OK with Telnet.

I am absolute newbie with X, no X configuring was done neither on Tru64 side (all 4 Alphas), nor on my PC.

Where to look at?

[Dave Bechtold]

Hello,

First, check to make sure "dtlogin" daemon is running on the V5.1B system. This is the process that responds to XDMCP queries. A "ps -ef | grep dtlogin" should show the command " /usr/dt/bin/dtlogin -daemon". If not then /sbin/init.d/xlogin has not ran or failed for some reason. If this never worked and it's a new install, make sure OSFCDEDT540 subset is installed. This subset provides the support for CDE/dtlogin. the below example shows it installed as desired.

# setld -i | grep OSFCDEDT
OSFCDEDT540 installed CDE Desktop Environment (Windowing Environment)


Second, I'd look in the file /var/dt/Xerrors, the dtlogin and Xserver errors file. This may show why a connection from the Exceed PC is failing.
I'd also make sure I could ping the Exceed PC by IP name and address from the V5.1B host and vice-versa from the PC to the V5.1B host to make sure the network connectivity is OK.

Let us know if you need more help.

Dave Bechtold

[Ralf Puchner]

There is nothing to do on Tru64 side if it was installed out-of-the-box.

Depending on your X11 Server (X11 Server is always the side you are sitting in front of), e.g. Exceed you must lower the security.

Specially Exceed need additional setup to work properly. Ask the vendor what must be configured because it is application specific.

[Ezra V. Isacco Di Biase_1]

Hello Alexei,

Maybe the /.dt directory is corrupted. Try to remove it and restart the X session.
It worked for me.

Bye

[Alexey Borchev]

Dave, I've found the error:
# tail -n 5 /var/dt/Xerrors
Mon Feb 16 16:45:09 2004
error (pid 2271): Cannot convert Internet address 134.65.188.188 to host name

This is the fact of life - I do not use DNS on my Alphas (No need so far), and my PC is not included into /etc/hosts.

But on my 5.1A Alpha I am seeing exactly the same error, and it's working for me!!!

I'll try to include my IP into /etc/hosts, but it would be temporary solution because my PC uses DHCP.

[Alexey Borchev]

Ok , I've included my PC in /etc/hosts

I've got no success, but another message in
/var/dt/Xerrors:

Warning: Missing charsets in String to FontSet conversion

I've installed Russian language in addition to English during Tru64 5.1B installation.
(I did not installed Russian on my older 5.1A & 4.0f hosts)

My next assumption - and now it's trying start X with Russian charset.

When I am logging in as root from server console, X & CDE starting perfectly OK. But several windows are using Russian language.

I searched .profile and .dtprofile for any Russian - nothing.

How does X defines language?

[Dave Bechtold · Accepted solution]

The dtlogin window, Login Box, I believe uses LOCALE environment variable. The default is "C" locale. Maybe check your 'root' login with 'printenv' and see if LOCALE is defined for something other than "C".

- Is the Login Box text in Russian on the local graphics head that works?

If it is, then I'm expecting that LOCALE environment variable is defined to be Russian and when CDE is attempting to display the login box it's trying to locate Russian fonts on the PC under Exceed. The Exceed PC doesn't have the fonts so dtlogin errors out.

Hope that helps.

Dave Bechtold

[Alexey Borchev]

Yes, the 'printenv' showed the language is Russian.

I've changed default language from Russian to English:
Sysman - Software - Config. International sftware - Manage Locales.

And that closed the question - now I can log in through X.