Red Hat Enterprise - Desktop

All of my sites run D3/PICK-Linux on some version of Red Hat over the
years. Primarly, i have never really been interested in the GRAPHICAL
DESKTOP of RedHat, as the server simply hosts the D3 database and my
application.
apart from some of the obvious tools such as SAMBA / CUPS etc, i use
WEBMIN to do most Linux Admin tasks, far simpler. However, the newer
versions of RedHat force this desktop onto you.


Anyway, i have installed 3 servers over the past 2 months, all
running
RedHat Enterprise 5.0. I have installed "ALL" applications and even
run the Software Updater to bring them up to spec. On all of them i
run the GNOME desktop as default, which from the outset seems to be
pretty standard and ok for what i need.


However, on all of these servers, at some point during a controlled
shutdown and reboot, whether that is because of software updates or
configuration changes (nothing drastic), the desktop seems to fall
over, and i am unsure as to why this happens.


When the server logs on, i get multiple ERROR WINDOWS pop up saying
such things as


"an error occured whilst loading or saving configuration information
for Nautilus" The error status window inside, then will say things
like "Failed to contact configuration server, some possible causes
are
that you need to enable TCP/IP networking for ORBIT or you have stale
NFS locks etc,,"


I will have other error windows stating that sessions have not opened
correctly (gnome-seesion, gnome-session-daemon and so forth), all
puporting to issues possibly with ORBIT or NFS locks etc. I have
never
touched ORBIT (dont even know what that is), so it sppears that it
gets itself into some sort of error during a reboot.


Can anyone shed any light on this, or have some users seen this
before.


I have not touched the "environment" of the server at all, in all
these servers apart from install Linux, install all software updates,
install D3 databae, and in between possibly reboot the machine a few
times.


The only way i seem to work around it, is to then boot the server up
and then choose the KDE DESKTOP interface, which is actually not
fixing the problem. It just means the GNOME desktop is no longer
functional.


John