Outlook connection over HTTP issue

Dear Experts

I have an issue with accessing emails from outside our domain

My business runs Windows 2008 SBS active directory domain

Example of domain name – exampledomain01.local

We also have Exchange 2007 with an email format of

Example – joe.blogg@exampledomaino1.local

Note: when the domain was set up by an external company (before my time) the domain name was set up incorrectly

It was set up as exampledomain01.local instead of exampledomaino1.local

Exchange can route emails to both domains

The issue: When working from home (not connected to domain) Outlook (set up with ‘Outlook anywhere’ – HTTP connection) connects to the wrong domain – exampledomain01.local and although this works we don’t have a certificate installed for that domain so Outlook gives a certificate error, which you can click OK to but it causes confusion.

Is there a way to force Outlook to connect to the correct domain – exampledomaino1 via ‘Outlook anywhere’ HTTP connection?

I’m not hot on exchange so any advice or suggested trouble shooting steps would be gratefully received

Many Thanks
Who is Participating?

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

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.

ChrisSenior Technical ArchitectCommented:
which bit was setup incorrectly?

What is the domain name on the certificate
What URL in on Outlook anywhere
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
I appreciate you trying to keep annominity in your question by not including the exact problem with the domain.

As a Zone Advisor on this site I do have access to your IP address and did review your actual certificate issued by GoDaddy.

I do see that the .local domain is not consistent with the rest.

What you need to do is have your certificate REKEYED to match the actual domain name that was used (with the "o" instead of the ZERO).  This is fairly easy to do at the GoDaddy site.

See http://help.godaddy.com/article/4976 for more information, or just call GoDaddy help for assistance (they are fairly good about this issue as I've dealt with it a few times)

Use the Add a Trusted Certificate Wizard to supply the new CSR, and once rekeyed go back to the Wizard to install correctly.  You may need to run the Fix My Network Wizard after reinstalling the cert to get things put in the right place.



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
ChrisSenior Technical ArchitectCommented:
that's saved some time.
GoDaddy are usually pretty good so you should be able to get it sorted easyily
ChrisSenior Technical ArchitectCommented:
don't worry about that, saves a lot of guess work while trying to keep the details anonymous :)
i2oitadminAuthor Commented:
Thanks guys, I'll look into it and get back to you ASAP
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

From novice to tech pro — start learning today.