3. Troubleshooting

If X cannot come up and is broken:

If X is broken and the connection fails, most of the time it has this error messages:

       _ FontTransSocketUNIXConnect: Can't connect: errno = 111
       failed to set dafault font path 'unix:-1'
       Fatal server error:
       could not open default font 'fixed'

This is likely due to xfs not finding the correct port for the Font Server (again, if you are running RH 6.2). To resolve this, check steps 1 and 7 above. Make sure the configuration are pointing to (port) 7100 and make sure you have the following fonts installed (if not re-install the XFree86 font packages):

         FontPath  "/usr/lib/X11/fonts/75dpi/"
         FontPath  "/usr/lib/X11/fonts/misc/"
         FontPath  "/usr/lib/X11/fonts/CID"
         FontPath  "/usr/lib/X11/fonts/Speedo"
         FontPath  "/usr/lib/X11/fonts/100dpi"

Use the command startx (on local) to restart the X server (or use telinit 5 to switch the run-level).

If Exceed has no respond:
In this case, most likely your xdm (or gdm, depending upon which is used in /etc/inittab) is not starting correctly. Issue the command: ps -ef | grep gdm (or ps -ef | grep xdm if xdm is used).
If the process is not running, check the steps on the setup above (make sure there are no typo's and that the correct path is given). Restart X using the command telinit 5.