HP-UX Desktop Troubleshooting Guide

The ipnodes entry may be as follows:
ipnodes: dns [NOTFOUND=continue] files
ipnodes: files [NOTFOUND=return] dns.
NOTE: Gr8 reference call:
http://gr8.mvlabs.corp.hp.com/gr8/stable/callEdit.pl?call=4000142281
For a similar problem related to DNS, please refer the above link.
Check the entries in the /etc/resolv.conf file. Ensure that the following entries
are correct if you are using DNS:
domain <domain name>
nameserver <DNS IP address>
5.1.6 Check problems with the dtgreet screen
If you are not able to view the dtgreet screen, establish a telnet connection with the
HP Server and check the dtlogin parent process by running the # ps ef | grep
dtlogin command.
If the dtlogin parent process is not running, start the dtlogin process by running
the # /sbin/init.d/dtlogin.rc start command on the command prompt and
re-check the status.
If the dtlogin process is started, it may have been possible that the auto-start option
of dtlogin was disabled (the auto-start option will start the dtlogin process every
time the system is rebooted). To enable the option, run the following commands in the
same sequence:
1. # /usr/dt/bin/dtconfig e
2. # /sbin/init.d/dtlogin.rc stop
3. # /sbin/init.d/dtlogin.rc start
5.1.7 Check problems with the dthello screen
The dthello screen is a blue color screen containing the copyright information of
CDE. The dthello screen is displayed after you have successfully logged in from the
dtgreet screen. If you are not able to view the dthello screen, the problem may be
related to rpcbind, which is a daemon process.
To check whether the rpcbind daemon process is running or not, execute the # ps
ef | grep rpcbind command.
The following command will be displayed on the screen:
root 899 1 0 Sep 5 ? 0:00 /usr/sbin/rpcbind
22 Troubleshooting on the HP-Server