Hi All,
I have recently set up a SBS 2008 running Exchange 2007 with the intention of getting Outlook Anywhere to work, something which I have very quickly found out is easier said than done...
Setup: Single server domain, SBS 2008, Exchange 2007, IIS7, Clients - Outlook 2007 SP2, Windows XP SP3, not joined to the domain, Firewall - ports 443, 80 and 25 open
Installed SBS 2008 clean install, installed Exchange, enabled Outlook Anywhere with basic authentication and hostname remote.domain.co.uk, installed self signed certificate*, checked and set permissions for virtual directories in IIS, pointed remote.domain.co.uk and autodiscover.domain.co.uk to the external static IP address
*I have read that self signed certificates will not work, or at least the default self signed will not work, I have requested a SAN certificate using Exchange PowerShell and issued with my server so that it contains; hostname, hostname.local; domain.co.uk, remote.domain.co.uk, autodiscover.domain.co.uk,
assigned in IIS and installed to the clients trusted root CA folder*
I do think the problem may lie with the certificate, however until I know it will solve the issue I am unable to spend the £250 required for a SAN certificate. I also believe there may be another problem as OWA accepts the certificate without a problem when browsing to
https://remote.domain.co.uk/owaHere is how far I can get:
OWA works without a problem, as long as the certificate is installed on the client (cert error if not)
Autodiscover passes a test (the one which ignores SSL authentication) on testexchangeconnectivity.c
om
When setting up a profile on an external client and entering the email address and password, it brings back the internal name of the server but says 'you must be connected/online to complete this operation'
When setting up a profile on an internal client (not joined to the domain, just in the same switch) it comes back with the correct information, connects and shows emails, but when send/receive is pressed it crashes on receiving when trying to download either the OAB or public folders.
Here is what I have tried from various forums (including this one):
Disabling IPv6
Editing hosts file to hash out #;;1 and add hostname, hostname.local to internal IP
Browsing directly to
https://remote.domain.co.uk/rpc (this prompts for a un/pw and shows a blank page when entered correctly, whichI believe is what it should do)
Switching between NTLM and Basic authentication in Outlook Anywhere
Inserting registry entries to manually assign ports 6001-6004 (which may be redundant but it was worth a shot)
rpcping from client computer (passes tests on ports 6001-6004)
Using a free trial certificate for remote.domain.co.uk from Comodo (unable to find trial SAN certificate)
Manually setting the clients to use
https://remote.domain.co.uk rather than using autodiscover
Removing and reinstalling RPC over HTTP
Disabling and re-enabling Outlook Anywhere
Breaking a keyboard (not much good to the server but relieved a little stress)
I apologise if this seems a little scrambled, I have spent the last few days on this same problem so it is possible I have missed a few steps out..! Any suggestions would be greatly appreciated
