Communicator & Mailbox access

Can anyone tell me whether Communicator 2007 can access a users mailbox information when the only available connection is RPC over HTTPS (i.e. Outlook Anywhere)?

Every time I log in to Communicator 2007, the connection it makes to the users mailbox appears to be over standard MAPI, but this was intended to be something that was to be phased out in our organisation, due to firewall rules and that fact that Outlook Anywhere is only over port 443, where as standard RPC can be any of the high ports.

I've just read the articles below which would seem to suggest that MAPI is the way the connection is made, but I need to confirm. Links to articles are:

http://communicationsserverteam.com/archive/2009/04/08/400.aspx
http://communicatorteam.com/archive/2008/01/29/54.aspx

Thanks
tbennett35Asked:
Who is Participating?
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.

HayesJupeCommented:
if outlook is available via RPC/HTTP, then communicator can access calendar information over RPC/HTTP.
0

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
tbennett35Author Commented:
So if a mail profile is configured to force HTTPS over RPC (i.e. both boxes checked in the Outlook Anywhere properties), but a standard mapi connection is also available, does it use mapi independently and make its own connection (because it can), or will it just default to whatever the mail profile dictates?

The reason I'm asking (and I might as well throw it out there) is because I'm trying to troubleshoot an issue with mail/communicator services via ISA, where only the OCS address book goes via ISA, not instant messenger traffic. When I log into the OCS client, I get a prompt for the mail box (which references the actual mailbox server name), then one for autodiscover (autodiscover.domainname.net), then another autodiscover.domainname.net prompt if I do a mail configuration test (ctrl-right click Outlook icon in system tray). This is for non  domain joined clients, where the ISA listener uses a forms based auth listener with sso configured for two domains (the domainname.net and the internal active directory name space, which would cover off sso on the mailbox name prompt).

Have just raised a call with Microsoft on this in parallell, but as I've already raised this issue, might as well follow up with the fll info.

Thnaks
0
HayesJupeCommented:
well thats by design, the OCS addy book should go via a reverse proxy, where as external IM traffic must go via an access edge (if its going to be supported - though it will work through a proxy)
thats a good question on the non-domain joined machines.... ive never tried it with that scenario...
as far as the autodiscover - have you published address book auto-discover information externally ?
0
Do You Have a Trusted Wireless Environment?

A Trusted Wireless Environment is a framework for building a complete Wi-Fi network that is fast, easy to manage, and secure.

tbennett35Author Commented:
Yes, autodiscover is configured ok, however it prompts for authentication. What its doing, however, is prompting twice for the same namespace, even though I have sso on the listener configured, once when I login to Outlook (however it only does this with communicator installed, not without) and once when i do anything else that requires autodiscover. once i've authenticated via the second autodiscover prompt, i dont get prompted again (which is as I would expect it to be after the first promptif my understanding of ISA is accurate).
0
HayesJupeCommented:
i had that for a while too, and it turned out that my autodiscover was configured incorrectly (which i then fixed) and then i had a seperate issue with the address book auth on the front-end which would also prompt.
You are correct with your comment above, but i spose i just want to be sure, that you're sure, that the prompt is definately for calendar information...
0
tbennett35Author Commented:
I ws wondeing whether it was autodiscover or not.

Have just ran test-outlookwebservices to test and these are the results:

[PS] C:\>Test-OutlookWebServices | fl


Id      : 1003
Type    : Information
Message : About to test AutoDiscover with the e-mail address tm-server-06@domainname.net.

Id      : 1006
Type    : Information
Message : The Autodiscover service was contacted at https://autodiscover.domainname.net/autodiscover/autodiscover.xml.

Id      : 1013
Type    : Error
Message : When contacting https://isa.domainname.net/EWS/Exchange.asmx received the error The request failed with an empty response.

Id      : 1016
Type    : Error
Message : [EXCH]-Error when contacting the AS service at https://isa.domainname.net/EWS/Exchange.asmx. The elapsed time was 249 milliseconds.

Id      : 1015
Type    : Success
Message : [EXCH]-Successfully contacted the OAB service at https://isa.domainname.net/EWS/Exchange.asmx. The elapsed time was 0 milliseconds.

Id      : 1014
Type    : Success
Message : [EXCH]-Successfully contacted the UM service at https://isa.domainname.net/unifiedmessaging/service.asmx. The elapsed time was 31 milliseconds.

Id      : 1013
Type    : Error
Message : When contacting https://isa.domainname.net/EWS/Exchange.asmx received the error The request failed with an empty response.

Id      : 1016
Type    : Error
Message : [EXPR]-Error when contacting the AS service at https://isa.domainname.net/EWS/Exchange.asmx. The elapsed time was 0 milliseconds.

Id      : 1015
Type    : Success
Message : [EXPR]-Successfully contacted the OAB service at https://isa.domainname.net/EWS/Exchange.asmx. The elapsed time was 0 milliseconds.

Id      : 1014
Type    : Success
Message : [EXPR]-Successfully contacted the UM service at https://isa.domainname.net/unifiedmessaging/service.asmx. The elapsed time was 15 milliseconds.

Id      : 1017
Type    : Success
Message : [EXPR]-Successfully contacted the RPC/HTTP service at https://isa.domainname.net/Rpc. The elapsed time was 0 milliseconds.

Id      : 1006
Type    : Success
Message : The Autodiscover service was tested successfully.

Id      : 1021
Type    : Information
Message : The following web services generated errors.
              As in EXCH
              As in EXPR
          Please use the prior output to diagnose and correct the errors.


Looks pretty successful. All the internal and external urls for both exchange and OCS address book are set the same for each service (i.e. autodiscover internal and external are the same, OCS address book internal and external are the same but different to autodiscover etc)
0
tbennett35Author Commented:
Itried this with MAPI rules in ISA turned off. it still works.
0
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
Microsoft Server OS

From novice to tech pro — start learning today.