Link to home
Start Free TrialLog in
Avatar of jjwolven
jjwolvenFlag for United States of America

asked on

Cannot connect with Outlook Anywhere

I am trying to get Outlook Anywhere to connect so that we can use laptops at the company for email inside and outside of the domain.  I have already purchased an SSL cert and have OWA working properly.  We are running Exchange 2007 with Outlook 2007 clients, external domain radiant.us.com.

I tried setting up OA with Microsoft's guide, entering the external host name as the same as used in OWA minus the "/owa" at the end (mail.radiant.us.com) as well as entering the same thing as the proxy on outlook.  It seems to connect, asking for a password but never registering it correctly.  One thing I noticed is that when it asked for the password it referenced the server.local domain in the Connecting to (exch.radiant.local).  I tried changing this in the Outlook setup to "https://mail.radiant.us.com" but that did nto work eaither.

What do i need to do to get this working properly?
Avatar of Sembee
Sembee
Flag of United Kingdom of Great Britain and Northern Ireland image

You need to ensure that you are putting the right information in the right boxes.

The primary recommendation I make with this feature is to test it internally first. Setup Outlook in the usual way, confirm it connects then ADD the additional information. If you are using Outlook 2007 then you need to ensure that autodiscover is working correctly, issuing the correct URLs.

The other common mistake is a version mismatch. Set the server to use basic authentication in EMC but set it to use NTLM in Outlook (or vice versa, with NTLM set as integrated on the server).

However if you have autodiscover and the URLs set correctly then Outlook should configure itself. Have you tested autodiscover to see what it is trying to set?

Simon.
Avatar of jjwolven

ASKER

autodiscover?  I saw a mention of it in one of the articles but the context made it look unimportant.

How do you set that up?
Autodiscover is not unimportant. It is one of the core features of Exchange 2007. If Autodiscover isn't working correctly then your server will have problems, particularly with Outlook 2007 clients.

http://exchange-genie.blogspot.com/2007/07/autodiscover-ad-attribute.html

Simon.
I decided to try the method using DNS because not all of the people that will be using the email will be joined to the domain.  

The document given says to create an A record for a url...A records are only for IPs.  I feel a bit stupid, but is there something I need to setup before the A record for it to look for the correct URL?
ASKER CERTIFIED SOLUTION
Avatar of Sembee
Sembee
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hmmm...this article states that when creating the SRV records I need to add it to the external DNS zone.
Does this mean that I have to create a new zone for radiant.us.com?  
Is there anything other than this SRV record that needs to be in there?
Sorry, clicked to fast.
This external zone need to be Primary, Secondary, or Sub?
The DNS records need to be made in DNS servers that point to the Internet - so that could be your ISP, domain name registrar etc.

Simon.
We currently have the domain through Network Solutions.  We have an MX record on the DNS  there for mail.radiant.us.com that points to the public IP of the Exchange server on site.  We also have a DNS onsite (same box as the exchange server).

Do I need to add the record to network solutions or to the onsite DNS?
Network Solutions. The DNS you have one site isn't internet facing so will not help.

Simon.
Still getting a certificate error, but receiving.  I will open a new question for that part.