failing dtlogin

[jim bidebo]

running hp-ux 10.20

when i login to the mashine via X it says:
unable to intialize or connect to the Desktop messaging system. Check your $HOME/.dt/errorlog for more information.

Press OK and your session will exit.

the $HOME/.dt/errorlog looks like this:
Tue Nov 13 11:13:28 2001
Workspace Manager: I/O error on display:: workstation10.ournet.se

the problem only occures on one mashine..
any ideas?

[jim bidebo]

i tried to remove the dns entries in /etc/resolv.conf (long shot)..
and i got a litle more complete error message in .dt/errorlog :

Tue Nov 13 11:17:45 2001
dtsession: The ToolTalk session server (ttsession) could not be started. This
indicates that either ToolTalk is not installed or that it is not
installed correctly on this machine. Please see your System
Administrator.

Tue Nov 13 11:18:04 2001
dtsession: Screen lock when the screen saver is turned on is not available on th
is server. Your screen will not be locked when the screen saver is turned on.

Tue Nov 13 11:18:07 2001
Workspace Manager: I/O error on display:: 10.205.133.69:0.0

[Alex Glennie]

This sounds like a hostname resolution problem .... can you try adding the ip and hostname in /etc/hosts and ammend /etc/nsswitch.conf to try files first, then use DNS .... result ?

[Steven Sim Kok Leong]

Hi,

Run dr_dt - the diagnostics tool for dt.

Full path: /usr/contrib/bin/X11/dr_dt

More often than not, it helps to pinpoint the fault. I have found it a most useful diagnostic tool for dt sessions.

Hope this helps. Regards.

Steven Sim Kok Leong
Brainbench MVP for Unix Admin
http://www.brainbench.com

[Rob Galloway_1 · Accepted solution]

Sounds like a problem I had with an incorrect IP address for the host in /etc/hosts. Have you checked this?

[Craig Rants]

Jim,
Is rpc.ttdbserver running?

Check your inetd.conf to make sure that it is not commented out.
rpc xti tcp swait root /usr/dt/bin/rpc.ttdbserver 100083 1 /usr/dt/bin/rpc.ttdbserver


That should take care of it for you.
Good Luck,
C

[jim bidebo]

hmm.. it was in /etc/host wrong ip for the host.. must have been so for several monts.. just wounder why noone have reported the problem earlier...

solved now..
thanks