Exchange Server 2010 Outlook Client Stops Responding

Greetings- This issue is with Exchange Server 2010 sp2 using Outlook 2013 clients in AD environment. Single server, single database (80GB) , 60+ users, Windows 8/8.1 workstations.
All of a sudden our users started experiencing issues yesterday. One or two at first, then more.
The issue where Outlook stops responding. This is most noticeable when you try to send and receive. The recipient will get the email before outlook clears it from pending submissions in the outbox.
1. SMTP is fully operational
2. Push clients functions normally
3. Exchange is fully updated and current
4. The mailbox databases are verified and healthy
5. Network traffic to and from the server appears normal according to wire shark
6. Setting Outlook to use no cache connection mitigates the issue partially
7. The issue is global on all deployed OS's
As this is happening on many, maybe all, workstations, my thought is that is has to do with Exchange, not the client.
Thanx
You should never, never doubt what nobody is sure about. -Willy Wonka

Does this happen all day, or at specific times? I'll add that your server appears to be light on CPU, but without knowing its CPU profile (when idle and when under a load), I can't say for sure this is your issue. One additional thing I can
ask - do you have hyperthreading enabled? This can be a bad thing in an Exchange server. See the following:
https://technet.microsoft.com/en-us/library/dd346699%28v=exchg.141%29.aspx?f=255&MSPPError=-2147217396#Hyper and the following:
http://blogs.technet.com/b/exchange/archive/2013/05/06/ask-the-perf-guy-sizing-exchange-2013-deployments.aspx Note that this second note is about Exchange 2013, but it goes into more details on some of the issues that may be adversely affecting your
Exchange 2010 servers.

Similar Messages

Problem connecting to godaddy exchange server via outlook client

I am pretty much having a very similar problem here:
https://social.technet.microsoft.com/Forums/exchange/en-US/437c5f8d-3a42-4689-90b4-13fd2749373f/go-daddy-ucc-certificate-exrca-can-only-validate-the-certificate-chain-using-the-root-certificate?forum=exchangesvr3rdpartyappslegacy
When I set up in outlook, I have noticed this in advanced connection settings:
the URL is required
mail.ex4.secureserver.net
Then check connect SSL only
Only connect to proxy servers with this principal name
msstd:mail.ex4.secureserver.net
When I use the connect principal, it works fine, but otherwise if it is not checked, it won't connect to the server.
http://www.experts-exchange.com/Software/Server_Software/Email_Servers/Exchange/Q_26423254.html
However, when I restart outlook, because I have multiple exchange accounts, they keep becoming "unchecked".
Everything worked fine about 48 hours ago, and now... all these problems.
Here is my log from the testing site:
Connectivity Test Failed
Test Details
   Testing Outlook connectivity.
    The Outlook connectivity test failed.
   Additional Details
Elapsed Time: 3897 ms.
   Test Steps
   Testing RPC over HTTP connectivity to server mail.ex4.secureserver.net
    RPC over HTTP connectivity failed.
   Additional Details
HTTP Response Headers:
Content-Type: text/html
Server: Microsoft-IIS/7.5
WWW-Authenticate: Negotiate,NTLM
X-Powered-By: ASP.NET
Date: Fri, 13 Feb 2015 01:07:27 GMT
Content-Length: 58
Elapsed Time: 3897 ms.
   Test Steps
   Attempting to resolve the host name mail.ex4.secureserver.net in DNS.
    The host name resolved successfully.
   Additional Details
IP addresses returned: 72.167.83.115
Elapsed Time: 95 ms.
   Testing TCP port 443 on host mail.ex4.secureserver.net to ensure it's listening and open.
    The port was opened successfully.
   Additional Details
Elapsed Time: 110 ms.
   Testing the SSL certificate to make sure it's valid.
    The certificate passed all validation requirements.
   Additional Details
Elapsed Time: 461 ms.
   Test Steps
   The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server mail.ex4.secureserver.net on port 443.
    The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
   Additional Details
Remote Certificate Subject: CN=mail.ex4.secureserver.net, O="Starfield Technologies, LLC.", L=Scottsdale, S=AZ, C=US, Issuer: SERIALNUMBER=10688435, CN=Starfield Secure Certification Authority, OU=http://certificates.starfieldtech.com/repository,
O="Starfield Technologies, Inc.", L=Scottsdale, S=Arizona, C=US.
Elapsed Time: 356 ms.
   Validating the certificate name.
    The certificate name was validated successfully.
   Additional Details
Host name mail.ex4.secureserver.net was found in the Certificate Subject Common name.
Elapsed Time: 0 ms.
   Certificate trust is being validated.
    The certificate is trusted and all certificates are present in the chain.
   Test Steps
   The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=mail.ex4.secureserver.net, O="Starfield Technologies, LLC.", L=Scottsdale, S=AZ, C=US.
    One or more certificate chains were constructed successfully.
   Additional Details
A total of 1 chains were built. The highest quality chain ends in root certificate OU=Starfield Class 2 Certification Authority, O="Starfield Technologies, Inc.", C=US.
Elapsed Time: 39 ms.
   Analyzing the certificate chains for compatibility problems with versions of Windows.
    Potential compatibility problems were identified with some versions of Windows.
   Additional Details
The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
Elapsed Time: 5 ms.
   Testing the certificate date to confirm the certificate is valid.
    Date validation passed. The certificate hasn't expired.
   Additional Details
The certificate is valid. NotBefore = 11/29/2012 8:39:18 PM, NotAfter = 11/29/2015 8:39:18 PM
Elapsed Time: 0 ms.
   Checking the IIS configuration for client certificate authentication.
    Client certificate authentication wasn't detected.
   Additional Details
Accept/Require Client Certificates isn't configured.
Elapsed Time: 232 ms.
   Testing HTTP Authentication Methods for URL https://mail.ex4.secureserver.net/rpc/rpcproxy.dll?mail.ex4.secureserver.net:6002.
    The HTTP authentication methods are correct.
   Additional Details
The Microsoft Connectivity Analyzer found all expected authentication methods and no disallowed methods. Methods found: Negotiate, NTLM
HTTP Response Headers:
Content-Type: text/html
Server: Microsoft-IIS/7.5
WWW-Authenticate: Negotiate,NTLM
X-Powered-By: ASP.NET
Date: Fri, 13 Feb 2015 01:07:27 GMT
Content-Length: 58
Elapsed Time: 146 ms.
   Attempting to ping RPC proxy mail.ex4.secureserver.net.
    RPC Proxy was pinged successfully.
   Additional Details
Elapsed Time: 224 ms.
   Attempting to ping the MAPI Mail Store endpoint with identity: mail.ex4.secureserver.net: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: 2626 ms.

Here is another test from the autodiscover:
    The Microsoft Connectivity Analyzer is attempting to test Autodiscover for [email protected].
    Autodiscover was tested successfully.
   Additional Details
Elapsed Time: 1745 ms.
   Test Steps
   Attempting each method of contacting the Autodiscover service.
    The Autodiscover service was tested successfully.
   Additional Details
Elapsed Time: 1745 ms.
   Test Steps
   Attempting to test potential Autodiscover URL https://MYDOMAIN.com:443/Autodiscover/Autodiscover.xml
    Testing of the Autodiscover URL was successful.
   Additional Details
Elapsed Time: 1745 ms.
   Test Steps
   Attempting to resolve the host name MYDOMAIN.com in DNS.
    The host name resolved successfully.
   Additional Details
IP addresses returned: xx.168.xx.74
Elapsed Time: 59 ms.
   Testing TCP port 443 on host MYDOMAIN.com to ensure it's listening and open.
    The port was opened successfully.
   Additional Details
Elapsed Time: 60 ms.
   Testing the SSL certificate to make sure it's valid.
    The certificate passed all validation requirements.
   Additional Details
Elapsed Time: 197 ms.
   Test Steps
   The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server MYDOMAIN.com on port 443.
    The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
   Additional Details
Remote Certificate Subject: CN=MYDOMAIN.com, OU=Domain Control Validated, Issuer: CN=Starfield Secure Certificate Authority - G2, OU=http://certs.starfieldtech.com/repository/, O="Starfield Technologies, Inc.", L=Scottsdale, S=Arizona, C=US.
Elapsed Time: 132 ms.
   Validating the certificate name.
    The certificate name was validated successfully.
   Additional Details
Host name MYDOMAIN.com was found in the Certificate Subject Common name.
Elapsed Time: 0 ms.
   Certificate trust is being validated.
    The certificate is trusted and all certificates are present in the chain.
   Test Steps
   The Microsoft Connectivity Analyzer is attempting to build certificate chains for certificate CN=MYDOMAIN.com, OU=Domain Control Validated.
    One or more certificate chains were constructed successfully.
   Additional Details
A total of 2 chains were built. The highest quality chain ends in root certificate OU=Starfield Class 2 Certification Authority, O="Starfield Technologies, Inc.", C=US.
Elapsed Time: 27 ms.
   Analyzing the certificate chains for compatibility problems with versions of Windows.
    Potential compatibility problems were identified with some versions of Windows.
   Additional Details
The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
Elapsed Time: 4 ms.
   Testing the certificate date to confirm the certificate is valid.
    Date validation passed. The certificate hasn't expired.
   Additional Details
The certificate is valid. NotBefore = 7/2/2014 2:30:01 AM, NotAfter = 7/2/2015 2:30:01 AM
Elapsed Time: 0 ms.
   Checking the IIS configuration for client certificate authentication.
    Client certificate authentication wasn't detected.
   Additional Details
Accept/Require Client Certificates isn't configured.
Elapsed Time: 673 ms.
   Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
    The Microsoft Connectivity Analyzer successfully retrieved Autodiscover settings by sending an Autodiscover POST.
   Additional Details
Elapsed Time: 754 ms.
   Test Steps
   The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://MYDOMAIN.com:443/Autodiscover/Autodiscover.xml for user [email protected].
    The Autodiscover XML response was successfully retrieved.
   Additional Details
Autodiscover Account Settings
XML response:
<?xml version="1.0"?>
<Autodiscover xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.microsoft.com/exchange/autodiscover/responseschema/2006">
<Response xmlns="http://schemas.microsoft.com/exchange/autodiscover/outlook/responseschema/2006a">
<User>
<DisplayName>[email protected]</DisplayName>
</User>
<Account>
<AccountType>email</AccountType>
<Action>settings</Action>
<Protocol>
<Type>IMAP</Type>
<Server>MYDOMAIN.com</Server>
<Port>993</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<SSL>on</SSL>
<DomainRequired>off</DomainRequired>
<SPA>off</SPA>
<AuthRequired>on</AuthRequired>
<LoginName>[email protected]</LoginName>
</Protocol>
<Protocol>
<Type>SMTP</Type>
<Server>MYDOMAIN.com</Server>
<Port>465</Port>
<DirectoryPort>0</DirectoryPort>
<ReferralPort>0</ReferralPort>
<SSL>on</SSL>
<DomainRequired>off</DomainRequired>
<SPA>off</SPA>
<AuthRequired>on</AuthRequired>
<LoginName>[email protected]</LoginName>
</Protocol>
</Account>
</Response>
</Autodiscover>
HTTP Response Headers:
Keep-Alive: timeout=15, max=256
Connection: Keep-Alive
Content-Length: 1227
Content-Type: application/xml; charset="UTF-8"
Date: Fri, 13 Feb 2015 01:14:56 GMT
Server: Apache/2.2.27 (Unix) mod_ssl/2.2.27 OpenSSL/1.0.1e-fips DAV/2 mod_bwlimited/1.4 mod_fcgid/2.3.9
Elapsed Time: 754 ms.

Exchange server 2010 DAG configuration

Dear Boss,
I would like to configure Exchange server 2010 with DAG . I have test lab . i would like to tell my test LAB setup .
One domain controller win-2008 X 64 Ent
Two Exchange server 2010 ( Role - Client Access, Mailbox) Each Server Two Network Cards with Different Classes
IP 192.168.44.50 , 51
IP 10.0.0.10 , 20
One Exchange server 2010 ( Role - Hub Transport )
IP 192.168.44.53
Pls tell me how can i create DAG
Note:- i would like to test below steps
1. Exchange server1 may be down or network link down how server 2 to work automatically without any disturbance
2. Exchange server2 may be down or network link down down how server 1 to work automatically without any disturbance
3. Hub transport server maybe down how it can be work ?
Regards
Subash

Hi Suriya,
To create a DAG, simply use the below commands from Exchange Management Shell:
New-DatabaseAvailabilityGroup -Name "DAGNAME" -WitnessServer HUBSERVERNAME
Add-DatabaseAvailabilityGroupServer –Identity DAGNAME -MailboxServer ExchangeServer1
Add-DatabaseAvailabilityGroupServer –Identity DAGNAME -MailboxServer ExchangeServer2
New-MailboxDatabase -Name DB1 -Server
ExchangeServer1
Add-MailboxDatabaseCopy -Identity DB1 -MailboxServer
ExchangeServer2
You can run your tests now, by restarting any of the servers, and you should be able to see the DB1 will automatically failover & failback between the nodes with out any intervention.
for the HUB transport you must have another server to achieve high availability, so you can install the HUB role on a different server or add it to one of your existing servers.
Mohammad Saeed | MCSE 2003 | MCTS: Lync, OCS, Exchange

Migration from Exchange server 2010 to Exchange server 2013

Hi All,
We have migrate Exchange Server 2010 to Exchange Server 2013. When I turned off my Exchange Server 2010, Outlook is not able to connect through Exchange 2013. It's prompting for user name and password again and again and nothing would happen
after provide user name and password. So, we are not able to uninstall exchange 2010 from old server.

Run these commands and post the update.
Get-WebservicesVirtualDirectory -Server E2K13SERVER |Fl internalURL,ExternalURL
Get-OWAVirtualDirectory -Server E2K13SERVER | Fl internalUrl,ExternalURL
Get-ClientAccessServer E2K13SERVER | Fl AutodiscoverServiceInternalUri
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange Server 2010 SP3 - Rollup 8 - Issue - Problems with client connections - MS Outlook 2013

Exchange Server 2010 SP3 - Rollup 8 - Issue - Problems with client connections - MS Outlook 2013
Detected Problems:
- Access denied for attached mailbox (department mailbox)
- Access denied for delete or move messages on own mailbox
- Can't send new messages with error (Error: [0x80004005-00000000-00000000])
Solution:
- Rollback to Exchange 2010 SP3 - Rollup 7
- You can rollback to Exchange 2010 SP3 - RollUp 7 in 30 min
Algunos de los destinatarios no recibieron su mensaje.
Asunto: Hola
Enviado el: 11/12/2014 8:35
No se puede localizar a los destinatarios siguientes:
'[email protected]' en 11/12/2014 8:35
Este mensaje no se pudo enviar. Inténtelo de nuevo más tarde, o póngase en contacto con el administrador de red.
Error: [0x80004005-00000000-00000000].

See the following forum thread:
https://social.technet.microsoft.com/Forums/en-US/1be9b816-b0ab-40ea-a43a-446239f8eae3/outlook-client-issues-following-exchange-2010-rollup-8

Exchange Server 2010 - Problem configuring my server 2008 so my clients can use Outlook to send/receive e-mails

Hi,
I am new to the servers and domains stuff. Therefore i have setup succesfully a Server 2008 R2 server with AD, DHCP, DNS roles installed. I configured the roles as i wanted and then i installed Exchange Server 2010 so the clients can use Outlook to send
receive mails in and out of the domain.
I can send/receive mails inside the domain (disalfa.com) but i cannot send/receive mails outside the domain. I configured the Exchange properly, i am sure of that. I am 99,9% i did something wrong with the DNS (A records, MX records, etc.).
Also is there something i must do from the control panel of the site i purchased the domain name and the mails?
Can someone guide me so i can manage to work this out?
Server 2008 - 192.168.1.250
Registered Domain - disalfa.com
Thank you in advance

Hi ,
I recommend you refer to the following article to configure your external mail flow:
Configure Internet Mail Flow Directly Through a Hub Transport Server
Prerequisites
Register MX resource records for all accepted domains in a public domain name system (DNS) server. Consult the documentation of your DNS provider for information about how to register MX records for your domain. Detailed procedures about how to complete
this step are outside the scope of this topic.
Configure network gateways to allow SMTP traffic to and from the Hub Transport server. Consult the documentation for your network routers and firewalls for information about how to route SMTP traffic to and from the Hub Transport server. Detailed procedures
about how to complete this step are outside the scope of this topic.
Best regards,
Niko Cheng
TechNet Community Support

Need help with Outlook 2013 connecting to Exchange server(2010)

Hi
I need help with Outlook 2013 and with my exchange server(2010) email account
After setting up account initially emails come in and than after an hour or two stop. My OWA is working fine with no issues. I have even created a forward rule in OWA to my GMAIL account whch works fine
However Outlook 2013 is not syncing messages, have difficulty in sending emails sometimes as it takes too long. In fact the connection also is intermittent. Even if the task bar shows connected to exchange, it seems that is not the case since new emails
and any emails I compose dont work. I have trouble shot the issue with my ISP and email service provide, but they havent resolved the issue I have also done a TraceRoute and that shows no drops or problems to he exchange server.
Can someone please help me resolve this matter so I can continue to use Outlook 2013( running Windows 8.1) in both my computers which have the identical problem
Look forward to a solution soon
Thanks

Hi Angela
Thanks for your message
To answer your questions, please note the following
a) My account is set up in Cache Mode( not online mode)
b) I am the only other user on the account
c) When the connection to the exchange server is broken, I see upon clicking connection tab that there is no information in the box, and when I press reconnect it starts showing "connecting"
d) When the connection to the server is there, it shows connection as "established"
e) Sorry I dont understand th meaning of CAS array in your environment? Can you pls explain
Since yday I have been using Outlook 2010 on desktop and Outlook 2013 on my laptop using Exchange 2013 account. So far all emails are syncing, and I can send emails from both computers. However, I am concerned that the connection can break-off anytime,
as it has done that in the past on both outlook versions. The max time it has worked without any problem is 48 hrs and than after that the same issue of not connection, not syncing and unable to send emails happens
My ISP has checked and there is no network connectivity issues. My email service provider has trouble shot the issue many times, but to no positive results. I have also changed the profile a few times, but the intermittent connectivity problem hasn't
been resolved.
Can you identify the possible causes and more importantly a working permanent solution please
Thanks
Mahesh

Free Busy takes over 30 seconds to retrieve on Outlook 2010 using Exchange Server 2010

We have a small 100 user domain running Exchange server 2010 and outlook 2010 clients. The issue is that Retrieving Free/Busy takes over 30 seconds.
So someone is trying to schedule a meeting has to wait Minutes see the Free/busy time for many users.. I have checked and all the users in question have published at least one month free busy time.
It seems it would be much faster. Anyone have this same experience and know of a way to speed it up?
thanks in Advance
David

Hi David,
Does the issue happen in OWA? In Exchange 2010, the free/busy information is retreved by using Availability service (EWS url). Generally, if a user wants to view free/busy information when create a meeting, the http Availability service request
would send to CAS server.
Please check whether the usage in Exchange server is high when the slow free/busy information occurs. This reflect time would also be related to the network in your environment.
Regards,
Winnie Liang
TechNet Community Support

Outlook 2010 Exchange Server 2010 to Exchange Server 2013 Features

Hi All
We have recently upgraded from Exchange Server 2003 to Exchange Server 2010. We are using the Outlook 2010 (32 bit) email client. When mailboxes were moved on to the new server various features inside the system were activated. For email Internal Out of
Office Messages, External Out of Office Messages, notifications in the email recipient bar when creating emails if the user was out of office.
What new features would be available with Outlook 2010 (32 bit) and Exchange 2013. And are they dependent on the Office Service Pack?
Kind Regards
Please note that I have previously posted this in another forum but was advised to post here in this forum.

Hi,
I find your post on Office forum:
http://social.technet.microsoft.com/Forums/en-US/fc538968-212c-411c-8ce8-0ef1d7acfcca/outlook-2010-exchange-server-2010-to-exchange-server-2013-features?forum=outlook
The Steve's answer is comprehensive, great links on Exchange 2013 new features and removed features.
About "And are they dependent on the Office Service Pack?", I will give the answer.
Based on my knowledge, when new SP releases, it include enhancements in security and compliance, architecture and administration, and user experiences.
For example, Exchange 2013 SP1, it connects to Outlook 2013 SP1 via MAPI over HTTP.
If you want to know more about the Exchange new features, please see Exchange Team Blog.
Find blog about SP1 for your reference:
http://blogs.technet.com/b/exchange/archive/2014/02/25/exchange-server-2013-service-pack-1-available.aspx
Thanks
Mavis
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Exchange Server 2010 - Receive Connector for Client Computers

I have one customer with a SBS 2011 with Exchange Server 2010 - a pretty standard setup except for some customisation with Receive Connectors in order to cater for an application which is installed on a number of computers that requires to use an SMTP Server
to send notifications. In order to accomplish this (allow to be sent using Exchange Server) we added the IP Address of client computer (which we also set as a DHCP reservation) to a pre-configured Receive Connector (Anonymous setup for Printer/Scanner).
This worked fine, but we now find that there are other applications that require the same function to use SMTP to send.
How should/could this be better configured so an application can send if they authenticate?

Hi
For this you need to create a seperate receive connector to be used for Relay in your organizations.
Follow the below steps
1) Create a dedicated Relay Receive Connector
2) Add only the Ip addresses of the applications which needs to relay on Exchange servers
3) You can use either anonymous or authenticated relay according to your relay config
You can follow the below link as well
http://exchangequery.com/2013/12/02/steps-to-configure-anonymous-and-authenticated-relay-in-exchange-2013/
Remember to mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you Check out my latest blog posts on http://exchangequery.com Thanks Sathish
(MVP)

Receive email delay one hour using Mac Mail client (Mountain Lion) connect Exchange Server 2010

Hi all,
My boss use iPhone, iPad, MacBook Air (Mac Mail client), MacPro (Mac Mail client) connect Exchange Serve 2010 to receive emails. All clients are okay except MacBook Air, the Mac Mail client cannot receive the latest emails from Exchange Server, but it can receive (sync) the emails after one hour. The other clients can receive the latest email after Exchange Server receive new emails immediately.
In this period, the MacBook Air can receive the other IMAP, POP3 and webmail from ISP normally. I tried to set 5 mins to check emails or manual check email from Exchange Server. However, the latest email still delay one hour.......... .
I dumped a screenshot for Mac Mail setting for Exchange Server and a Log file.
could anyone help me to solve this issue?
Thanks

I am not sure what the user has the check for new messages set for but mail does arrive as short as 2 minutes. It does however arrive on his iphone immediately first.

Send As, Send on Behalf and Full Access for Exchange server 2010/2013

[This FAQ contains 2 parts]
Testing and watching the behavior of Send As, Send On Behalf and Full Access permission.
Common issue and Troubleshooting on the three permission.
[Testing and Watching]
Based on following blog, I decide to test on my lab:
Full Mailbox Access Rights + Send On Behalf = Send As ?
http://blogs.technet.com/b/ehlro/archive/2012/04/06/full-mailbox-access-rights-send-on-behalf-send-as.aspx
Description on my lab and test:
Exchange 2010 + Outlook 2010
Exchange 2013 + Outlook 2013
Senders: A01, A02, … , A07, A08
Recipient: A09
A01 grand permission to other senders.
Two methods:
a. Use A0x’s credential configure A01’s profile, then send From both A01 and A0x via Outlook. Watching result in A09’s Inbox and Sent Items which has message copy left.
b. Use A0x’s credential configure A0x’s profile, then send From both A01 and A0x via Outlook. Watching result in A09’s Inbox and Sent Items which has message copy left.
Result as following forms:
1. Exchange 2010 + Outlook 2010 / Exchange 2013 + Outlook 2013
Using A0x’s credential configure A01’s mailbox, then send From both A01 and A0x
To A09.
2. Exchange 2010 + Outlook 2010 / Exchange 2013 + Outlook 2013
Using A0x’s credential configure A0x’s mailbox, then send From both A01 and A0x
To A09.
[Common Issue]
1. [Issue]
Exchange 2010 + Outlook 2010. A01 grand A03 Send As permission. However A03 can’t send as A01 to A09 and get NDR:
You can’t send a message on behalf of this user unless you have permission to do so. Please make sure you’re sending on behalf of the correct sender, or request the necessary permission. If the problem continues, please contact your helpdesk.
Details as following pic:
[Troubleshooting]
1) Based on the NDR, it seems a permission issue. Check Send As permission, however the Send As permission configured correctly. Pic as below:
2) ince the Send As permission configured correctly, it seems the permission hasn’t been replicated. Try to restart Microsoft Exchange Information Store service. It works.
Note: The Send As permission isn’t granted until after replication has occurred. Replication times depend on your Exchange and network configuration. To grant the permission immediately, stop and then restart the Microsoft Exchange Information
Store service.
2. [Issue]
Exchange 2013 + Outlook 2013. A01 grand A03 Send As permission. However A03 can’t send as A01 to A09 and get NDR:
Your message did not reach some or all of the intended recipients.
Subject: xxx
Sent: xx/xx/2014 8:20 AM
The following recipient(s) cannot be reached: A09
This message could not be sent. Try sending the message again later, or contact your network administrator. Error is [0x80070005-00000000-00000000].
Details as below:
[Troubleshooting]
1) Also check the Send As permission configuration first.
2) Then try to use A03 send as A01 to A09 via OWA. If OWA works well, it seems and issue on the Outlook client side.
3) This behavior may occur if the OAB in Outlook isn’t updated. Try to download OAB manually.
4) If doesn’t work, please close Outlook and try to delete all the OAB folder on your computer. The path of OAB folder in Win7, Win8 as below:
\Users\<UserName>\AppData\Local\Microsoft\Outlook\Offline Address Books
5) Restart Outlook.
Note: Be aware that you cannot send e-mail messages on behalf of a mailbox if the mailbox is hidden from address list. When sending a message, Exchange requires that e-mail address is resolved in the
From field.
3. [Issue]
Exchange 2010. A01 grant A0x “Send As” or “Send on Behalf” permission. A0x send as/ send on behalf of A01. The message is only copied to the Sent Items folder in A0x’s mailbox (same as the result of my test). Also cannot configure Exchange 2010 so that the
message is copied to the Sent Items folder of both A01 and A0x.
[Troubleshooting]
This issue occurs because Exchange server 2010 was designed to copy message to the Sent Items folder of the sender only. This issue can be solved by installing Exchange 2010 SP2 UR4. More details in the following KB:
Messages that are sent by using the "Send As" and "Send on behalf" permissions are copied only to the Sent Items folder of the sender in an Exchange Server 2010 environment
http://support.microsoft.com/kb/2632409/en-us
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Nice guide Mavis, I recently explored the same topic. Few things you might want to add is the type of connectivity (Cached vs Online will produce different results) and to expand further on the methods of adding the other mailbox in Outlook (additional mailbox
vs additional account defaults to different methods). Check the screenshot:
And please post this somewhere more visible, like blog/wiki page.

NLB detected duplicate cluster subnets - Exchange Server 2010 SP3 CU5

Hi All,
I will explain the environment first, there are:
-Two HUB/CAS servers (WNLB)
--HUBCAS01
--HUBCAS02
-Two Mailbox servers (Failover Clustering)
--MAILBOX01
--MAILBOX02
*All servers are updated to Exchange Server 2010 SP3 CU5.
The issue is that from recently outlook users are disconnecting from the outlook and cannot be joined to the exchange server unless if I drainstop or stop HUBCAS01. Furthermore, if I start HUBCAS01 from WNLB it will work fine for sometimes yet it will randomly
disconnects outlook users from exchange again (For ex: next day morning).
So far when I search deeper in Event log, there is an warning event log:
Event ID 18: NLB cluster [192.168.*.*]: NLB detected duplicate cluster subnets. This may be due to network partitioning, which prevents NLB heartbeats of one or more hosts from reaching the other cluster hosts. Although NLB operations have resumed properly,
please investigate the cause of the network partitioning.
Now I hope you will provide this link to resolve this issue - http://technet.microsoft.com/en-us/library/cc726421(v=ws.10).aspx
But I don't think that this will resolve this issue, as i have tried this for 3 times, yet no luck. Please help me to resolve this issue permanently. Thanks in advance.

Hi,
The issue is mainly related to the HUBCAS01 server. To deep investigate the issue, you need to take RPCTrace from the Outlook client and see the details. Even more, it’s better
to take a Network trace to check the details of the network.
Thanks,
Simon Wu
TechNet Community Support

Exchange Server 2010: Undeliverable Message

Dear All,
We are using exchange server 2010 to send a email to a client, however, we got this message back. How can i solve this problem?
Thanks for your attention and help!
次の受信者またはグループへの配信に失敗しました:
[email protected] 受信者の電子メールプロバイダーによって拒否されたため、メッセージを配信できませんでした。
メッセージは次の組織に拒否されました。BL2FFO11FD039.mail.protection.outlook.com。
管理者向けの診断情報:
生成サーバー: xxxx.com
[email protected] BL2FFO11FD039.mail.protection.outlook.com #<BL2FFO11FD039.mail.protection.outlook.com #5.7.0 smtp;550 5.7.0 Relay Access Denied> #SMTP#
元のメッセージヘッダー:
Received: from na01-by2-obe.outbound.protection.outlook.com (207.46.163.241)
by exch.xxxx.com (192.168.10.32) with Microsoft SMTP Server (TLS)
id 14.3.210.2; Sun, 19 Oct 2014 22:36:47 -0700
Received: from BN1AFFO11FD049.protection.gbl (10.58.52.31) by
BN1AFFO11HUB044.protection.gbl (10.58.52.155) with Microsoft SMTP Server
(TLS) id 15.0.1049.20; Mon, 20 Oct 2014 05:36:44 +0000
Received: from mgcserv4.magsaysay.com.ph (203.167.92.249) by
BN1AFFO11FD049.mail.protection.outlook.com (10.58.53.64) with Microsoft SMTP
Server id 15.0.1049.20 via Frontend Transport; Mon, 20 Oct 2014 05:36:43
+0000
Received: from Crystal ([203.167.92.232]) by
mgcserv4.magsaysay.com.ph (Lotus Domino Release 8.5.3) with ESMTP id
2014102013364607-10992 ; Mon, 20 Oct 2014 13:36:46 +0800
X-TM-IMSS-Message-ID: <[email protected]>
Received: from na01-bl2-obe.outbound.protection.outlook.com ([65.55.169.54])
by magsaysay.com.ph ([203.167.92.232]) with ESMTP (TREND IMSS SMTP Service
7.0; TLS: TLSv1/SSLv3,256bits,AES256-SHA) id 26975997000186d5 ; Mon, 20 Oct
2014 13:40:58 +0800
Received: from BL2FFO11FD041.protection.gbl (10.173.160.33) by
BL2FFO11HUB022.protection.gbl (10.173.161.46) with Microsoft SMTP Server
(TLS) id 15.0.1049.20; Mon, 20 Oct 2014 05:36:36 +0000
Received: from mail.xxxx.com (216.81.51.170) by
BL2FFO11FD041.mail.protection.outlook.com (10.173.161.137) with Microsoft
SMTP Server (TLS) id 15.0.1039.16 via Frontend Transport; Mon, 20 Oct 2014
05:36:36 +0000
Received: from na01-by2-obe.outbound.protection.outlook.com (207.46.163.236)
by exch.xxxx.com (192.168.10.32) with Microsoft SMTP Server (TLS)
id 14.3.210.2; Sun, 19 Oct 2014 22:36:28 -0700
Received: from BY2FFO11FD056.protection.gbl (10.1.14.33) by
BY2FFO11HUB055.protection.gbl (10.1.14.244) with Microsoft SMTP Server (TLS)
id 15.0.1039.16; Mon, 20 Oct 2014 05:36:15 +0000
Received: from mailgate.zzz.com (14.16.28.51) by
BY2FFO11FD056.mail.protection.outlook.com (10.1.15.193) with Microsoft SMTP
Server id 15.0.1049.20 via Frontend Transport; Mon, 20 Oct 2014 05:36:13
+0000
X-AuditID: c0a81e07-b7f5e6d000000b4e-4d-54449f4b6588
Received: from UNER2.zzz.com (unr2.zzz.com
[192.168.30.13]) by mailgate.zzz.com (Symantec Messaging Gateway) with
SMTP id CA.40.02894.B4F94445; Mon, 20 Oct 2014 13:36:11 +0800 (HKT)
Received: from UN2.zzz.com ([::1]) by UNR2.zzz.com
([::1]) with mapi id 14.01.0438.000; Mon, 20 Oct 2014 13:36:11 +0800
From: Yukihiro <[email protected]>
To: Simonu <[email protected]>, Charles
<[email protected]>
CC: Miln <[email protected]>, FSA
<[email protected]>
Subject: Re: unia s maual / MV Kett Iand
Thread-Topic: unaa sh ml / MVlettsland
Thread-Index: Ac/sEV9D2LsdkU5fRkW0Rd1v4PsvSQAFlzIA
Date: Mon, 20 Oct 2014 05:36:10 +0000
Message-ID: <D06AC01C.21F27%[email protected]>
References: <[email protected]>
In-Reply-To: <[email protected]>
Accept-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.2.140509
x-originating-ip: [192.168.30.123]
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprJIsWRmVeSWpSXmKPExsVyYIUcr673fJcQg8bHChbzDrexW/R3vGG2
OPK31GLjrinMDiwePbO6WAIYo7hsUlJzMstSi/TtErgy/my9w1Zw2LJi74lOxgbGd+ZdjJwc
EgImEq27r7NA2GISF+6tZ+ti5OIQErjIKHF27jdmCGcCo8SpVw3MIFVsAtoS21rusILYIgKR
En8nzgKzmQXiJL7sPAc2SVjAWOLni0tsEDUmEvNOdzNC2EYSp55dZgKxWQRUJa5unwBm8wro
SVzdtgNsvpBAhETH9lawOZxA808+PwxmMwJd9/3UGiaIXeISlyYvYoO4WkBiyZ7zzBC2qMTL
x//A7hEFmtnc9YYRIq4kcfbZAaA5HEC9wRJ3mzgg1gpKnJz5hGUCo9gsJFNnIVTNQlIFEdaU
WL9LH6JaUWJK90N2CFtDonXOXCjbWuJq40IWZDULGDlWMQrlJmbmGOqV5mXqJhZnJuol5+du
YoREJ/sOxg9NlocYBTgYlXh4pzi5hAixJpYVV+YeYpTgYFYS4f2XARTiTUmsrEotyo8vKs1J
LT7EyMTBKdXAKPV7/zEX5dgtO6cd8N8764+UCO+vDPaVj5LWF051+GIx3/pf/dHiA0Gn+Lia
by2Se/tyVqhMYGzs1CpNAcut2bfuLIhUOqbbIDv7buL74s/XWGIu27vcYoi+dJ9BSzA9WNnH
h1NVbn+SgEDAhsL6Cyvs48Ja+1InV76xt515//fJOSLapX/uKbEUZyQaajEXFScCAFed/I2s
AgAA
Return-Path: [email protected]
X-EOPAttributedMessage: 2
X-Forefront-Antispam-Report-Untrusted: CIP:14.1.28.51;CTRY:HK;IPV:NLI;EFV:NLI;SFV:NSPM;SFS:(428002)(189002)(66654002)(199003)(252514010)(76176999)(21056001)(71186001)(31966008)(106466001)(81156004)(77096002)(95666004)(54356999)(105586002)(4396001)(50986999)(15975445006)(86362001)(83506001)(107046002)(84326002)(19617315012)(36756003)(85852003)(53416004)(92726001)(15974865002)(19580395003)(19580405001)(44976005)(101416001)(16236675004)(92566001)(87836001)(85306004)(99396003)(2656002)(46102003)(120916001)(15202345003)(20776003)(30436002)(512874002);DIR:INB;SFP:;SCL:1;SRVR:BY2FFO11HUB055;H:mailgate.zzzz.com;FPR:;MLV:sfv;PTR:014168051.static.ctinets.com;MX:1;A:0;LANG:en;
X-Exchange-Antispam-Report-Test: UriScan:;UriScan:;UriScan:;
Received-SPF: None (protection.outlook.com: zzz.com does not designate
permitted sender hosts)
Authentication-Results: spf=none (sender IP is 203.167.92.249)
[email protected];
X-Auto-Response-Suppress: DR, OOF, AutoReply
X-Matching-Connectors: 130582569966280204;(42405700-fa69-4020-a9c4-08d0e394d333);()
X-Forefront-Antispam-Report-Untrusted: CIP:216.81.51.170;CTRY:CA;IPV:NLI;EFV:NLI;SFV:NSPM;SFS:(10009020)(428002)(199003)(66654002)(252514010)(189002)(81156004)(106466001)(76176999)(54356999)(36756003)(77096002)(101416001)(53416004)(50986999)(105586002)(95666004)(31966008)(46102003)(20776003)(30436002)(19580395003)(4396001)(44976005)(19580405001)(16236675004)(6806004)(21056001)(71186001)(15974865002)(15202345003)(99396003)(84326002)(120916001)(15975445006)(83506001)(92726001)(92566001)(85852003)(86362001)(2656002)(87936001)(85306004)(107046002)(512874002)(19617315012);DIR:OUT;SFP:1101;SCL:1;SRVR:BL2FFO11HUB022;H:mail.xxx.com;FPR:;MLV:sfv;PTR:216.81.51.170.epikip.net;A:0;MX:1;LANG:en;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:BL2FFO11HUB022;UriScan:;
X-Forefront-PRVS: 03706074BC
X-MIMETrack: Itemize by SMTP Server on mgcserv4/mgc(Release 8.5.3|September 15, 2011) at
10/20/2014 01:36:46 PM,
Serialize by Router on mgcserv4/mgc(Release 8.5.3|September 15, 2011) at 10/20/2014
01:36:47 PM,
Serialize complete at 10/20/2014 01:36:47 PM
X-TNEFEvaluated: 1
Content-Type: multipart/alternative;
boundary="_000_D06AC01C21F27hzzzcom_"
Content-Language: ja-JP
X-Forefront-Antispam-Report: CIP:203.167.92.249;CTRY:PH;IPV:NLI;EFV:NLI;SFV:NSPM;SFS:(428002)(252514010)(189002)(66654002)(199003)(76176999)(54356999)(86362001)(15974865002)(50986999)(85852003)(92566001)(92726001)(19617315012)(512874002)(46102003)(85306004)(97736003)(99396003)(120916001)(33186001)(53416004)(44976005)(105586002)(19580405001)(106466001)(16236675004)(77096002)(81156004)(19580395003)(95666004)(31966008)(71186001)(107046002)(21056001)(101416001)(15202345003)(84676001)(68736004)(30436002)(87836001)(2656002)(20776003)(4396001)(6806004)(84326002)(83506001)(15975445006)(36756003)(72026002);DIR:INB;SFP:;SCL:1;SRVR:BN1AFFO11HUB044;H:mgcserv4.magsaysay.com.ph;FPR:;MLV:sfv;PTR:ErrorRetry;MX:1;A:0;LANG:en;
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:BN1AFFO11HUB044;

Hi Shiloh,
According to your description, my understanding is that you send a message to external user(@xxx.com) fail.
Before going further, I'd like to ask the following question to narrow down the issue:
1. Could you send message to any other external user except xxx.com? like google.com,outlook.com.
2. Try to disable or bypass Transport Scanning in Forefront Protection 2010 and check if any helps.
You can refer to the following article to disable or bypass FPE:
http://social.technet.microsoft.com/wiki/contents/articles/407.how-to-disable-or-bypass-transport-scanning-in-forefront-protection-2010-for-exchange-server-fpe.aspx
Best regards,
Niko Cheng
TechNet Community Support

Exchange Server 2010 Room Mailboxes Double Booking

We are have several room mailboxes setup on Exchange Server 2010 and are having an issue with rooms being double booked.
I have "Allow Conflicting Meeting Requests" unchecked on the Resource Policy Tab but if a user try's to book a room that is already reserved it gets accepted and put on the calendar.
How do I stop this from happening?
Here are the settings for the room:
AutomateProcessing                  : AutoAccept
AllowConflicts                      : False
BookingWindowInDays                 : 365
MaximumDurationInMinutes            : 1440
AllowRecurringMeetings              : True
EnforceSchedulingHorizon            : True
ScheduleOnlyDuringWorkHours         : False
ConflictPercentageAllowed           : 0
MaximumConflictInstances            : 0
ForwardRequestsToDelegates          : True
DeleteAttachments                   : True
DeleteComments                      : False
RemovePrivateProperty               : True
DeleteSubject                       : False
AddOrganizerToSubject               : True
DeleteNonCalendarItems              : True
TentativePendingApproval            : True
EnableResponseDetails               : True
OrganizerInfo                       : True
ResourceDelegates                   : {}
RequestOutOfPolicy                  : {}
AllRequestOutOfPolicy               : False
BookInPolicy                        : {}
AllBookInPolicy                     : True
RequestInPolicy                     : {}
AllRequestInPolicy                  : False
AddAdditionalResponse               : False
AdditionalResponse                  :
RemoveOldMeetingMessages            : True
AddNewRequestsTentatively           : True
ProcessExternalMeetingMessages      : False
RemoveForwardedMeetingNotifications : False
MailboxOwnerId                      : gsc.local/Users/Board Room
Identity                            : gsc.local/Users/Board Room
IsValid                             : True

The most common cause of this issue is that you have both Outlook Direct Booking and AutoAccept enabled. To fix this logon to the Mailbox using Outlook and disable direct booking see (or use a script) http://blogs.technet.com/b/exchange/archive/2013/07/15/a-significant-update-to-remove-directbooking-script-is-now-available.aspx
and http://blogs.technet.com/b/mohammad_qassim/archive/2011/05/22/meeting-rooms-double-booking-in-exchange-2007.aspx
Cheers
Glen

Exchange Server 2010 Outlook Client Stops Responding

Similar Messages

Maybe you are looking for