AIX

where do you see this error?

does it stall for a long time?

exactly what doesn't work right now? people can't start a desktop from their PC? the desktop won't start on the console?

it hard to imagine that a restoration of the system would remain broken. when you restored, did you use the same IP address and machine/host names as the original installation (back when it DID work)?

i don't know what DT_TTSESSIONS is, but at first guess, i'd say it has to do with CDE.

This error is on the machine console, we use only telnet for remote connection.
I put login and password in CDE then the following message appears : "Starting the Common Desktop Environment". After a few time comes a windows "ToolTalk Message Server Could Not Be Started" with DT_TTSESSION_TIMEOUT.
I've checked all files (/etc/hosts,resolv.conf,netsvc.conf,and so on...)

This problem occurs a few days while I was configuring /etc/inetd.conf. The backup was on december (same IP and hostname) and was ok, now the restore has the same problem... I don't understood that!

This problem despairs me because I waste time to seek a unknown error.

Thanks

Im pretty sure it's a name resolution issue.
I've had the same with 5.2 either the /etc/resolv.conf was erronous or some change was made at /etc/hosts, didn't really remember which were the source maybe both ...

yeah... i'm tending to think the same.

do you absolutely need to run CDE on your console? if not, you may want to try and run 'dtconfig -d'. this disables the desktop.

Dumb question. After you put back the stuff in /etc/inetd.conf, did you SIGHUP inetd (or reboot)? inetd isn't going to reread the file unless you tell it to by sending it the HUP signal with a "kill -HUP ..." command.

Yeah... I've made a reboot!
I don't need absolutely the Xsessions but I just want to make CDE running like before. I'm interessting to find the cause of that problem!

So, I've controlled many times /etc/resolv.conf /etc/hosts and so on whitout the find a mistakes...
Perhaps I should install AIX again!

Well, try smit mktcpip and check every parameters there (hostname, route, dns...), if everything is fine then update by clicking ok... that seems odd but anytime we do change related to network/hostname we need to rehresh it for the change to take effect...
Thought that might help