The real problem with the VMWare image is that when loaded into VMWare, there is NO eth0 at all. Not even listed in the /networks-scripts/ folder. ifconfig -a, only "lo" shows. ifconfig eth0, shows there isnt even an eth0 in the system "unknown device". I searched, read and searched again for a solution, however, evry one I tried, and there were a load of them, did not work. Re-download the image, reinstalled VMWare, many times,and always, the same problem. I do not think it was VMWare. But rather the image. Although I do not kow why on mine it would not pick up eth0. I can however, ifconfig eth1 and it works to let me winSCP to the server and mess around. But, I can fire up the server, but, client could not see it. Also, rebooting centOS removed eth1 from the list. It still there, just not active. Nothing I tried would make it stay. So, after messing around with that for several hours, I went back to VMbox, slid the server files over to that, changed the IPs where needed, did not have to mess with eth0 or any thing network at all. it all started, 'cept the gdelivery problem, but could be gauth also however that is the first one to load and syslog shows it loads fine, keys accepted.
Am not new to ubuntu, but am REAL new to centos. I think i stick with ubuntu. Not new to setting up servers, diagnosing problems with them. Been doing it for many a year now. But, I will admit, this one has me stumped.
