GeoTrust QuickSSL CA root certificate is not trusted -- please help

I am using a Redhat Enterprise plain server. My domain name is www.auctionzealot.com. About a month ago I installed a server on my laptop for development and testing. The API I was interfacing with required SSL for a single authorization step, so I created a self-signed certificate for my dummy app implementation, NOT using a domain name, but using my computer's IP address of the server. After transferring everything to an EV1 dedicated server just recently and going through the GeoTrust QuickSSL to get a REAL SSL certificate, I am running into the following problem. Somehow I am suspicious that this certificate is in conflict with my old self-signed certificate? But I honestly don't know SSL enough to know what the problem is for sure! ;D

I followed the GeoTrust steps exactly and installed it without complication. The page CAN be accessed via https. However, I get the following warning from IE6 on THREE different machines, the same warning that used to show up on my local server with a self-signed SSL certification:

A Security Alert box pops up and says:

Security Alert
Information you exchange with this site cannot be viewed or changed by others. However, there is a problem with the site's security certificate.

- The security certificate was issued by a company you have not chosen to trust. View the certificate to determine whether you want to trust the certifying authority.

- The security certificate date is valid.

- The name on the security certificate is invalid or does not match the name of the site

Do you want to proceed?

YES | NO | VIEW CERTIFICATE
<3 buttons>

When I click View Certificate a new box pops up:

Certificate
General | Details | Certification Path
<3 page tabs>

Under the General tab it says:

Certificate Information
This CA Root certificate is not trusted. To enable trust, install this certificate in the Trusted Root Certification Authorities store.

Issued to: localhost.localdomain
Issued by: localhost.localdomain

Valid from 2/16/2004 to 2/15/2005 <by the way, these dates are incorrect, I paid for and went through the certificate process in late march around 3/28/04 or so>
<I believe these dates correspond to around the time that I did the self-signed certificate for testing purposes on a different machine using an IP instead of a domain name>


Under the Details tab it says:
Show: <All>
Field | Value
Version | V3
Serial number | 00
Signature algorithm | md5RSA
Issuer:
- E = root@localhost.localdomain
- CN = localhost.localdomain
- OU = SomeOrganizationalUnit
- O = SomeOrganization
- L = SomeCity
- S = SomeState
- C = --
<None of these values are what I entered during the certificate process>
Valid from | Monday, February 16, 2004 1:13:16 AM
Valid to | Tuesday, February 15, 2005 1:13:16 AM]
<again, these dates aren't correct as I paid for and went through the Geotrust QuickSSL process somewhere around March 28 (several days ago)>
Subject:
- E = root@localhost.localdomain
- CN = localhost@localdomain
- OU = SomeOrganizationalUnit
- O = SomeOrganization
- L = SomeCity
- S = SomeState
- C = --
<Again, none of these values are what I entered during the certificate process>
Public key | (a series of numbers and letters)
Subject Key Identifier | (a series of numbers and letters)
Authority Key Identifier:
KeyID=(a series of numbers and letters)
Certificate Issuer:
Directory Address:
E=root@localhost.localdomain
CN=localhost.localdomain
OU=SomeOrganizationalUnit
O=SomeOrganization
L=SomeCity
S=SomeState
C=--
Certificate SerialNumber=00
Basic Constraints:
Subject Type=CA
Path Length Constraint=None
Thumbprint alogrithm | sha1
Thumbprint | (a series of numbers and letters)

Finally, under the Certification Path tab it says:
Certification path
localhost.localdomain
Certificate status:
This CA Root certificate is not trusted because it is not in the Trusted Root Certification Authorities store.


It was probably overkill typing all of this out, but I really need to get this working soon and provide all the information that I know.

Again I suspect some sort of strange certificate conflict, but the other (self-signed) certificate was generated for another machine and an IP address, not a domain name.. Does anyone have a clue what is the matter with this?

Thanks in advance!
David

i'm having the same problem!!! y no one reply the solution????????