HP-UX Desktop Troubleshooting Guide

1. dtlogin parent process may not be running on the HP server.
— Check for the existence of dtlogin parent process by executing the
following command:
# ps –ef | grep dtlogin
— If the process does not exist, start the dtlogin process by executing the
following command and re-check the status:
# /sbin/init.d/dtlogin.rc start
— If the dtlogin process is started, it may have been possible that the
auto-start option of dtlogin was disabled. (auto-start option will start
dtlogin process every time the system is rebooted). To enable the option,
execute the following command in the same sequence:
# /usr/dt/bin/dtconfig –e
# /sbin/init.d/dtlogin.rc stop
# /sbin/init.d/dtlogin.rc start
2. The dtlogin request port may be mentioned incorrectly.
The “Dtlogin.requestPort: 0” entry in Xconfig file may be
uncommented.
# #########################################################################
# To disable listening for XDMCP requests from X-terminals.
#
# Dtlogin.requestPort: 0
# #########################################################################
Once commented, start the dtlogin process by running the following
command:
# /sbin/init.d/dtlogin.rc start
Then try connecting via any X manager to check if CDE comes up or not.
NOTE: GR8 call reference:
http://gr8.mvlabs.corp.hp.com/gr8/stable/callEdit.pl?call=4000142228
For a similar problem as XDMCP connection, please refer the above link.
4.3 Troubleshooting Problems related to Network
There may be several issues related to the network that may prevent CDE to come up
on a remote system. Some of the commonly encountered problems are as follows:
4.3.1 Problems related to IP address and host name
Check the IP address and the hostname of the HP-Server in the /etc/hosts file. If
DNS is not used to resolve the hostname and IP address, there must be one entry for
each HP server along with the hostname because this entry will help in resolving the
hostname and IP address.
16 Troubleshooting on the Remote System