No firewall inbetween them, or not that I know off.........the funny thing is I think it has somethign to do with the display...is that possible but then again I have both machiens run the exact same settings resolution and so on....
Man this thing is drivign me up the wall and I knwo it is goign to be somethign stupid or small!!!!

Do you have access to the server? Does it have a monitor? Does it have the X windows system running? Is it using a session manager?

It seems to me that the problem is the Centos's xfree86 configuration or video driver. I think that the best approach is to divide the problem up and get the x server working on the CentOS box on its own before logging on to a remote session.

Back up the /etc/inittab and /etc/X11/XF86config files before proceding. I bet that the /etc/inittab will be the same as before when you are finished, but the XF86Config file will be different.

OK skipper, I have managed to reproduce the latest problem here.

If I insert a typo into the 'x:5:respawn:....' line in /etc/inittab or remove execute privileges from prefdm, it gives the same "respawning too fast" stuff you had. This is because init is compelled to respawn a doomed process.

I believe your original problem was a better one, so I would suggest you return the line in /etc/inittab to what you started with, and check to see if a Window manager is specified in /etc/sysconfig/desktop.
Mine has a single directive:
DESKTOP="GNOME"

This is a global, and will be superseded (I think) by a '.xsession ' file in the user's home directory, so check for a specified desktop there if .xsession exists.

RHELL, it sounds that you are on something here but now I have to behonest and say that I will go and spend time on what you said btu here need to try and translate your reply to english or actually afrikaans so that I can understand what and where I need to check and change.......

I do appreciate your time and will mentioned to managemnet your help because this could help a lot if I can get this working just before increase time!!!

Okay, I re-did my ks.cfg file for automated installation and this time I selected the GNOME package to be installed instead of the KDE and by just editing the inittab file it works liek a charm......well not 100% but at least I can now get the application login screen and login, the problem I have now is the fact that there is no borders to the application and it doesn't seem to be accepting any commands, for e.g. if I click on an accoutn to open a timesheet it just sit there and look at me if I am crazy.....
Any ideas why I will be able to open the application but not able to use any of the actions and why the borders will be missing?

Glad the desktop works, KDE would also be fine, it just wasn't specified before, so you got the crudest default window manager instead(called TWM). For future reference, you could have changed /etc/sysconfig/desktop without the re-install, and you can install packages(such as other window managers) using 'rpm'.
I don't speak Afrikaans, but 'mein hund haben wermen' if that helps.

That said, do other X applications run properly?

Ignorance question, I can not make up my mind if that is either soemthign in German or Swedish?
Well what the entry in the inittab file does, I think, is it does nto use anything installed on the box, it merely runs an application from the server and displays the graphics on the workstation......
Other than that I have no idea, I am planning on writting my RHCE exam at the end of the year so stay tuned as I learn more and more Linux, any tips will be apprecaited?
Thanks for your effort's on helping me!
Where you from?

It's supposed to be German, but I wouldn't bank on it.
The nature of X is a bit backward, a server(display manager) in the X context controls a display, the clients are things that want access to the display.
Inittab attaches X attributes to a runlevel, in my case they are all local, in yours they are split. Either way they start automatically on runlevel 5.
I'm in Northern California.