Solved

Outlook clients using Outlook Anywhere cannot connect.

Posted on 2008-10-23
3
425 Views
Last Modified: 2012-06-27
I've been unable to get Outlook Anywhere to work for any remote clients using Outlook 2007.  I have an Exchange 2007 server on my relatively small domain and it is connected with 1 nic to my network with an internal IP and the 2nd nic is connected with a static address to our ISP (probably unsafe but was having trouble getting this to work otherwise).

Everything internal works fine (however we get a certificate error whenever outlook is launched because our certificate is for *.domain.com and the server is exchange.localdomain.local).  This is an issue I will address at another time since it at least works.  Remotely our OWA works great and is running over SSL with the proper cert.  

I went through exchange_genie's howto at:
http://exchange-genie.blogspot.com/2008/02/configuring-outlook-anywhere-for.html

and verified all the changes.  RPC over HTTP is setup, it is listed in IIS 7, RPCProxy.dll is allowed, I used EMC to enable Outlook Anywhere, with Basic Authentication and verified all the Valid Ports in the registry.  

Outlook itself from outside the company is setup using exchangeserver.localdomain.local and the connection tab has outlook anywhere's option checked off using SSL only and Basic Authentication.  

My mind is a bit mushed up now so if anyone can think of some alternative ideas to check - that would be great!
0
Comment
Question by:jaelae
  • 2
3 Comments
 
LVL 3

Expert Comment

by:Scripting_Guy
Comment Utility
If your Outlook outside the company is setup to use exchangeserver.localdomain.local, then this is where you might start looking. This DNS-Name is (if at all) only valid if you're using your DC as DNS-Server. Use the same DNS-Name / IP Adress you use for accessing OWA from outside your company.

Also note that if you're using a self signed Certificate, you will need to manually deploy it to every Client using Outlook Anywhere.
0
 

Author Comment

by:jaelae
Comment Utility
The certificate is a wildcard one issued by godaddy and appears to work great over OWA.  It seems to be a configuration issue in Exchange - rather than on the client.  I'm using GFI MailEssentials for antispam - and Microsoft Forefront Exchange Security for antivirus.  Aside from this it is just using the internal firewall which I have even disabled to verify nothing is being blocked.
0
 

Accepted Solution

by:
jaelae earned 0 total points
Comment Utility
I have since reloaded a new Exchange Server from scratch and this is no longer an issue.
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

We are happy to announce a brand new addition to our line of acclaimed email signature management products – CodeTwo Email Signatures for Office 365.
This article explains in simple steps how to renew expiring Exchange Server Internal Transport Certificate.
In this video we show how to create a Distribution Group in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >>…
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Ac…

743 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

18 Experts available now in Live!

Get 1:1 Help Now