What you’re seeing
- Some users see a security alert saying the certificate name doesn't match the site, or that it isn't trusted.
- Outlook keeps asking for a password even when the right one is entered.
- Certain computers or phones won't connect, while colleagues in the same office have no trouble.
- It began the day the mail server's certificate was replaced.
Common causes
Every environment is different, but these are the causes our engineers find most often:
- The new certificate is missing one of the names Outlook connects to, such as the autodiscover name or an internal server name.
- The intermediate certificate from the issuing authority was not installed, so devices that do not already have it cached cannot build a trusted chain.
- One node behind a load balancer or reverse proxy still serves the old certificate, so only users routed to it are affected.
- Older operating systems or mobile devices do not trust the root authority behind the new certificate.
- Outlook profiles on some machines cached the old certificate exception or credentials and keep retrying them.
Why it matters
Partial failures are frustrating and expensive to support. Help-desk time goes into one-by-one troubleshooting, and staff who can't connect fall behind or start using webmail on personal devices. Repeated password prompts also condition people to type their credentials into any box that appears, which is exactly the habit phishing attacks exploit. If the cause is a missing intermediate certificate or name, it can also break mobile sync and calendar sharing for people outside your organization.
How AskTechGurus fixes it
Skip the trial and error. A certified engineer works on your actual system, finds the root cause, and fixes it properly.
Tell us what’s happening
Submit a ticket in about two minutes. Paste the error, describe what changed, and pick your tier. No charge to submit.
A certified engineer diagnoses it
A vetted, US-based systems engineer claims your ticket, usually within minutes during business hours, and investigates over a secure remote session you can watch and end at any time.
Fixed and verified with you
The engineer resolves the root cause and confirms with you that it’s working. You don’t just get a workaround, and you get a plain-English summary of what was wrong.
Pay only when it’s resolved
Fixed price from $99, invoiced only after you approve the fix. If it isn’t resolved, you don’t pay.
Frequently asked questions
Why is it only some people?
Different devices check certificates in slightly different ways and may connect by different names or through different servers. The users affected usually share something, such as a device type, location or connection path, and finding that pattern points to the cause.
Do we have to buy another certificate?
Not always. Many cases are solved with the certificate you already have. If a name is genuinely missing, a reissue may be needed, and we explain that before anything is changed.