Make sure you are using the local name of the server in your outlook
setup.

For example, if your mail server is named "exchange" on your internal
network, but is called "mail" on your external mx record, you must your
"exchange" in the server name when setting up the outlook profile.  Also
you need to make sure the name you enter in the OA settings in Outllook
matches the certificate.

As for buying a cert, I could not get OA to work until I purchased a
cert.  I used GoDaddy.  I want to say it was $30.

However, I have not set it up in EX2007.

Also check this blurb:

"Exchange 2007 apparently depends on a number of subject alternative
names. If you don't have your subject alternative names on your
certificate in the correct order, and they don't match the correct
common name on the same certificate, you can look forward to hours of
troubleshooting Outlook Anywhere Access from Outlook 2007 clients. Oh,
give us back the sheer simplicity of Exchange 2003 and RPC/HTTP."

Cut from this article:
http://articles.techrepublic.com.com/5100-1035_11-6184591.html



Bob Fronk
[EMAIL PROTECTED]


> -----Original Message-----
> From: Oliver Marshall [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, April 30, 2008 1:48 PM
> To: NT System Admin Issues
> Subject: Outlook 'anywhere' (aka nowhere) and Exchange 2007
> 
> Hi chaps,
> 
> I'm having a 'mare getting Outlook Anywhere working on an Exchange
2007
> sp1 box running on 64bit 2003 and Outlook 2007 clients.
> 
> I've installed RPC over HTTP on the server, I've enabled Outlook
> Anywhere in Exchange 2007, I've set up a self signed cert for the
> external name, and opened up port 443.
> 
> When I set the the outlook clients up it just reports 'disconnected'.
On
> the outlook end I've set it up the same way I would when using SBS or
> Exchange 2003. Everything *looks* ok on the server end. There's
nothing
> apparent in either set of event logs.
> 
> I guess I have two questions. Firstly, are there any logs somewhere I
> can check to see whats failing? Also, does 'outlook anywhere'
*require*
> a cert to be used from a valid cert authority or should I be able to
> just install the self cert on each of the client machines for it to
work
> ?
> 
> Olly
> 
> ~ Upgrade to Next Generation Antispam/Antivirus with Ninja!    ~
> ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~

~ Upgrade to Next Generation Antispam/Antivirus with Ninja!    ~
~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm>  ~

Reply via email to