Solved

OutlookAnywhere - MAPI Mail Store endpoint - attemped to ping failed

Posted on 2014-10-25
6
1,145 Views
Last Modified: 2015-05-24
Hi,

I have a DC (Server 2012 R2) setup, with RDS and EXCHANGE (with MS Exchange 2013 SP1) as virtual servers.

RDS is facing the internet (mail.domain.com @ Port 443), and is using ARR with URL Rewrite for OWA, EWS, Autodiscover, ActiveSync and ECP, rewriting all requests to EXCHANGE.

When I run tests on https://testconnectivity.microsoft.com for Outlook connectivity, it fails saying:

Attempting to ping the MAPI Mail Store endpoint with identity: 86b551b0-c6d5-4ec4-8f1b-66e01b29beeb@domain.com:6001.
       The attempt to ping the endpoint failed.
        Tell me more about this issue and how to resolve it
       
      Additional Details
       
The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.
Elapsed Time: 3310 ms.

Telnet from DC or RDS into EXCHANGE on port 6001 works fine.

However, I am concerned that there may be two things preventing this from working:

1) 86b551b0-c6d5-4ec4-8f1b-66e01b29beeb@domain.com:6001 <-- shouldn't this be trying to connect to mail.domain.com:6001 and not domain.com?

2) Even if there is nothing wrong with the above, I would assume it is using RDS's standard 443 port, and trying to ping 6001 on RDS itself, since as far as I know, URL Rewrite has no rules to forward port requests on to exchange.

Am I right in my assumptions?
0
Comment
Question by:Saleem Beg
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
6 Comments
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 40407292
This:
86b551b0-c6d5-4ec4-8f1b-66e01b29beeb@domain.com:6001

is normal on Exchange 2013. All end users have a unique end point, so that is what you will see for the mailbox. Not the real name of the server, or the SSL name.

As for the second point - you are probably not getting answers because no one has done it.
ARR is still a new technology, I haven't deployed it anywhere myself. Regular RDS and Exchange OWA will paly well, but I don't know if that applies with ARR.

if it is affecting users, then one of them will have to go to get connectivity back.
Or you will have to call Microsoft support.

Simon.
0
 

Author Comment

by:Saleem Beg
ID: 40410112
Hi Simon,

Thanks for the response.

ARR may explain the issue with Outlook Connectivity from the internet. But it should surely connect internally directly to 'exchange' as this is what I specified as it's internal name?
0
 
LVL 63

Expert Comment

by:Simon Butler (Sembee)
ID: 40411246
No.
The behaviour is the same both internally and externally. Everything connects to the unique end point.
The server name isn't used by any of the clients. They have the unique end point and then FQDN configured for Outlook Anywhere.

Simon.
0
Office 365 Training for IT Pros

Learn how to provision tenants, synchronize on-premise Active Directory, implement Single Sign-On, customize Office deployment, and protect your organization with eDiscovery and DLP policies.  Only from Platform Scholar.

 

Accepted Solution

by:
Saleem Beg earned 0 total points
ID: 40418883
I managed to fix this myself.

In ARR I had rewritten URL for ECP, OWA, etc, etc but not RCP, and hence it was pinging the RCP of ARR server and not exchange.
0
 

Author Closing Comment

by:Saleem Beg
ID: 40428003
Because it worked
0
 

Expert Comment

by:Sainaa
ID: 40794542
Hi Saleem Beg,

Can you share your rewrite rule for RPC? I'm having same issue.
0

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
This article will help to fix the below error for MS Exchange server 2010 I. Out Of office not working II. Certificate error "name on the security certificate is invalid or does not match the name of the site" III. Make Internal URLs and External…
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
There's a multitude of different network monitoring solutions out there, and you're probably wondering what makes NetCrunch so special. It's completely agentless, but does let you create an agent, if you desire. It offers powerful scalability …

729 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