Exchange 2007 - No email since adding SMTP service to SSL certificate

I recently needed to add the SMTP service to our SSL certificate for use with OCS2007.
Now none of the email is getting through the Hub Transport. All roles are on the one server (we dont have an Edge Transport Server). I rebooted the server only to find ALL services are now assigned to the SSL certificate. The self signed cert is still there with the SMPT, IIS servides applied.
The SSL cert wal already applied to the IIS sites.
Running the Exchange analyser, it initially comes up with the Hub Trnasport role installed, but then comes up saying it cant find the Hub Trnasport when checking the queues. Have I missed a step somewhere?
Without building a new Hub Transport server elsewhere, what can I do. I can remove the certificates as Exchange complains that some services will not work . (Fair enough)
Thoughts appreciated...
riskyflierAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

William YangSolution ConsultantCommented:
Did you get any 12014 error in event log?

If yes, it means the FQDN on SMTP receive connector does not match the one on the self-cert certificate.

You can try to fix it by:
1. check the FQDN on the receive connector. Make sure it is not configured to external FQDN.

2. Use the powershell command below to renew the self-cert and assign it for SMTP service.
New-ExchangeCertificate -SubjectName "CN=<server internal FQDN>" | Enable-ExchangeCertificate -Services "SMTP"
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
riskyflierAuthor Commented:
No such errors whatsoever in the event log. But I'll check the FQDN. From what I remember from yesterday it DID have the FQDN (external) configured on the receive connector.
Will let you know. Thx
0
riskyflierAuthor Commented:
Well, looking at the SAN certificate, it states invalid when running the Get-ExchangeCert command.
I think I'll follow your advise to renew the self cert...

Will let you know how it pans out.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.