External emails not received after shutdown of Exchange 2010 in coexistence with Exchange 2013

I have exchange 2013 and exchange 2010 in coexistence mode. All mailboxes have been moved to Exchange 2013 and firewall/spamfilters already pointed to Exchange 2013 CAS server. I can receive/send from and to external addresses, however when I shutted down
the Exchange 2010 all incoming external mails were not received. What could be the cause?

Start by re-checking how the device that takes the traffic from the external MX IP to internal is configured.
Sniff the traffic to ensure that it is hitting 2013 directly.
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne 
Twitter:   LinkedIn:
  Facebook:
  XING:
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.

Similar Messages

  • Internal outlook client connectivity in exchange 2010 when coexist with exchange 2013

    Hi all ,
    on my side i would like to clarify few queries.
    Say for instance i am coexisting exchange 2010 with exchange 2013 .Unfortunately if all of my exchange 2013 servers goes down .
    Q1 .On that time will the internal outlook users having their mailboxes on exchange 2010 can be able to connect mailboxes without any issues ? In case if they face any issues what kind of issues will they be? Because why i am asking is we should have pointed
    the autodiscover service to exchange 2013 during coexistence.
    When an user closes and reopens the outlook after whole exchange 2013 environment failure ,outlook will first query the autodiscover service for the profile changes to get it updated on users outlook profile.In such case autodiscover service will not be
    reachable and i wanted to know will that affects the internal client connectivity for outlook users having their mailboxes on exchange 2010.
    Q2. Apart from outlook internal users connectivity ,what kind of exchange services(i.e owa,active sync,pop,external OA and imap) will get affected when whole exchange 2013 environment goes down during coexistence ?
    I have read the below mentioned statement on this awesome blog but still i wanted to clarify with you all on my scenario.
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx<o:p></o:p>
    Internal Outlook Connectivity
    For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will still connect to the Exchange 2010 RPC Client Access array endpoint.
    For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2007, they will still connect directly to the Exchange 2007 Mailbox server instance hosting the mailbox.
    Please share me your suggestions and that would help me a lot .
    Regards
    S.Nithyanandham

    Hi Winnie Liang ,
    Thanks a lot for your reply.
    Scenario  1 : for internal outlook connectivity 
    We have below settings for exchange 2010 autodiscover.
    mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2010 cas serves
    We are going to have below settings for exchange 2013 autodiscover.
    mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2013 cas serves
    During coexistence mail.domain.com will be pointed to exchange 2013 cas servers . I mean to say if we try to resolve the mail.domain.com it will get resolved in to the exchange 2013 cas servers.
    So on such case if anything happened wrong to the new environment or else if entire environment goes down .Do we face any issues while outlook users connect to existing mailboxes in exchange 2010 ?
    Because why i am asking is ,on the below mentioned article i have read all the autodiscover request will go via exchange 2013 cas servers during coexistence.That means all the existing mailboxes in exchange 2010 will also have to query exchange 2013 cas
    servers for autodiscover request.During the whole exchange 2013 environemnt failure whenever the user tries to close and open outlook .Outlook will first queries the autodiscover service for any changes happened on that particular mailbox and it will try to
    get it updated on user profile.
    http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
    Would it be possible to make the exchange 2010 mailbox users to query only the scp points which belongs to the exchange 2010 cas servers for autodiscover request ?
    Scenario 2: For exchange services
    mail.domain.com - will be the namespace for all the exchange 2010 services (i.e owa,activesync,external outlook anywhere,pop,imap)
    mail.domain.com - will be the namespace for all the exchange 2013 services (i.e owa,activesync,external outlook anywhere,pop,imap)
    What about the above services will it get affected during whole exchange 2013 environment failure ?
    Note : We are not facing this issue , i hope everything goes well in my environment while doing coexistence i am just asking this question on my own interest?
    Regards
    S.Nithyanandham
    Thanks S.Nithyanandham

  • Exchange 2010 co-existence with Exchange 2007 issue NDR size Four Times then we send

    Hi All,
    I am facing some strange issues of NDR size four times then we send like if I send 1 MB message to internal OR external recipient then we receive 4 MB NDR.
    Even we send one black mail with subject Test mail of 4 kb then we receive 16 kb NDR is it due to architecture change or something else.
    Everything was fine with Exchange 2007 but facing this issues after we change the mail flow to Ex2010.
    Any help really appreciated
    Regards
    Anand S
    Thanks & Regards Anand Sunka MCSA+CCNA+MCTS

    Hi Anand,
    From your description, the NDR size is four times than original message size. I would like to verify the following thing for troubleshooting:
    How many people has this issue, only one or all the people?
    If only one user has this issue, I recommend you move the user's mailbox to another mailbox database and check the result.
    If all the people have this issue, please enable Pipeline tracing and see if there is any hint. If the issue persists, please install the latest Service Pack and Rollup and check the result.
    Here is an article for your reference.
    Enable Pipeline Tracing
    http://technet.microsoft.com/en-us/library/bb125018(v=exchg.141).aspx
    Hope it helps.
    Best regards,
    Amy Wang
    TechNet Community Support

  • Exchange 2010 CAS array with Exchange 2013 Mailbox Servers

    Here is our current scenario,
    Exchange 2007
    2 - Hub Transport Servers
    2 - CAS servers (cluster NLB)
    2 - Mailbox servers (clustered)
    Exchange 2010
    2 - Huib Transport Servers
    3 - CAS servers (array NLB)
    2 - Mailbox servers (1 DAG)
    We have not migrated any users to the Exchange 2010 environment yet. We're thinking that at this point we would rather go from 2007 to 2013. Does the 2013 mailbox server work with a 2010 CAS array?

    Hi,
    As far as I know, CAS array doesn' t exist in Exchange 2013. And OWA and other requests can be proxyed and redirected from Exchange 2013 to Exchange 2010.
    For more information, you can refer to the following article:
    http://blogs.technet.com/b/exchange/archive/2013/01/25/exchange-2013-client-access-server-role.aspx
    Thanks,
    Angela Shi
    TechNet Community Support

  • Error msg: "Config message not received after 45 seconds"

    I have developed a simple stateless session bean. After being called once, the following is output to the log:
    Thu Jan 04 18:15:46 CST 2001:<I> <RJVM> Signaling peer 3978882810638278829C198.171.129.36 gone: weblogic.rjvm.PeerGoneException:
    - with nested exception:
    [java.net.SocketException: Connection reset by peer]
    Exactly 45 seconds later the following is output and I can no longer access a JDBC connection from my pool:
    Thu Jan 04 18:16:31 CST 2001:<I> <CliCon-#|myserver|0.978653734170> Connection to client for ClientContext - id: '#|myserver|0.978653734170', bound: 'true', dead: 'false' has been unexpectedly lost be
    cause weblogic.rjvm.PeerGoneException: Config message not received after 45 seconds.
    Initiating hard disconnect.
    Can anyone shed some light on this for me?
    Thanks in advance!

    Hi,
    this is the explanation why this occours:
    If there is a t3 Client connects to the server, every ( weblogic.system.configTimeoutCheckVal
    ) time, ConfigTimeoutChecker will run to check the t3 client is disconnected or
    not. The problem is, if the client has already disconnected, the ConfigTimeoutChecker
    still runs every time to check the disconnected t3Client again and again.
    This should be solved with SP11.
    Christian Plenagl
    Developer Relations Engineer
    BEA Support
    "kelvin" <[email protected]> wrote:
    >
    I am using WLS 5.1 sp8 128SSL, I got this error. I results that the java
    object
    in the JMS channel is sometimes missing. I increased the weblogic server
    thread
    from 15 to 30. But still can't help. I also ugrade the client server
    to use the
    same sp8. But can't help. Some one mentions the sp9 can solve this problem.
    It
    is true? anyone have it for unix ? where can I download it? I can't
    find it in
    weblogic web site.
    Kelvin

  • I cannot send emails, only receive, after upgrade to Yosemite today, Apple should resolve this issue. Any help more than welcome. Thanks

    I cannot send emails, only receive, after upgrade to Yosemite today, Apple should resolve this issue. Any help more than welcome. Thanks

    BTW. I have seen posts suggesting age of Mac has an affect. Mine is MacBook Pro (Retina, Mid 2012)
    The mail I am having problems send is Exchange and google mail. The google client I re-installed and this had no affect.

  • I cannot send emails, only receive, after upgrade to Yosemite today, Apple should resolve this issue. Any help more than welcome. Thanks in response to Pita Fito I have contacted three more people that made the upgrade and they have the same problem

    I cannot send emails, only receive, after upgrade to Yosemite today, Apple should resolve this issue. Any help more than welcome. Thanks
    in response to Pita Fito
    I have contacted three more people that made the upgrade and they have the same problem. My advise is not to upgrade until Apple solves the serious issue, I would hate to have to re-install Outlook...

    I can send e-mails just fine with apple mail on yosemite...
    Might not be a generic problem but rather a personal problem..
    You should try find a fix rather than waiting on apple.
    Hopefully somebody can help you out.
    More than happy to help with your settings/preference pain... And compare mine with yours...
    If you send some screenshots... I can send you my equivalent... So maybe you can figure it out.
    Is it a gmail or icloud email acount? Can be of more help if it is.

  • Email not updating after IOS 8.1.2

    Email not updating after installation of IOS 8.1.2.  On ipad, ipad2, and iphone. How to roll it back to the prior version?

    HHaving the same issue here,im don't think you can roll back.
    did it start after crashing while trying to send an email with multiple attachments?

  • Change domain of the email not received email from apple

    update my ipad 2 and  then ask activate, im loss my id and password change domain of the email not received email from apple I can not activate my ipad please help, my little girl put false  information fuel the only thing certain email

    If you're using the tell a friend tag ({tag_tellafriend}) you can modify the subject of the email that is sent out by Site Manager > System E-mails > Tell-a-Friend.
    If you're not using this, please let us know how eaxactly you're achieving this functionality.

  • Apple ID verification email not received - anybody have latest / newer fix?

    Apple ID verification email not received - anybody have latest / newer fix?

    Check the following:
    1. Spam folder
    2. Junk folder
    3. Rescue email

  • ISA 2006 publish Exchange 2010 Outlook Anywhere with KCD/NTLM and IPSEC - Problem

    Hi
    I have setup ISA 2006 to publish Exchange 2010 Outlook Anywhere with Kerberos Constrained Delegation and IPSEC.
    The clients have an IPSEC policy pushed to them via GPO.  The clients are windows 7 laptops and the ISA server is server 2003, so the IPSEC connection is IKE not AuthIP.
    However, it seems that the connection will work for a while, then all of a sudden stop working with zero trace of why.  I cant get the Oakley log to work and I cant see any traffic on the ISA.
    I am wondering if I need to publish the CRL's externally?  Currently we don't, and the Outlook Anywhere uses private certificates (as the whole point of IPSEC is to validate the internal certificate, there is no point in using
    public certificates).
    I have tried using the StrongCRLCheck=0 registry key in the IPsec Policy Agent on the windows 7 machine but it doesn't seem to make a difference.
    Any advice would be appreciated.
    Steven

    Hi,
    Firstly, have you received any related error messages in ISA server or on the clients' side? Besides, as you mentioned IPsec, did you have a VPN connection?
    In addition,
    While ISA 2006 only includes a Client Access Web Publishing Wizard for both Exchange 2003 and Exchange 2007. Which Exchange version you have chosen when publishing Exchange 2010?
    Please also make sure that you have selected the
    External interface for the web listener to listen on.
    Besides, the link below would be helpful to you:
    OWA publishing using Kerberos Constrained Delegation
    method for authentication delegation
    Best regards,
    Susie

  • Exchange 2010 - 2003 coexistence "unable to relay"

    Hi
    I have a customer with a Exchange 2010 / 2003 coexistence. 
    The Exchange 2010 has 3 CAS/HT servers. 
    When sending mails from 2003 to the outside world, one of the CAS/HT is giving me "unable to relay".
    Right now I have removed it from the routing group connector, but do you have any ideas where to look?
    BR
    Steen

    Hello,
    If there is only AD site, the receive connector is not needed.
    If there are multiple AD sites, when you send message to other AD sites, the receive conenctor is needed. If you send message from exchange 2003 to exchange 2010 or exchange 2010 to exchange 2003, the routing group connector is needed.
    Cara Chen
    TechNet Community Support

  • Exchange 2010 OWA usage in Exchange 2013

    Hi,
    I have Exchange 2010 with Sp3 Currently running in environment, Now we have plan to Migrate it to Exchange 2013.... Total number of mailbox is around 26000.
    Before Migration we want below things to keep in mind...
    1. We want to Use existing exchange 2010 OWA url ( mail.abc.com ), How to accompolish this as it will take couple of months to migrate all mailbox ?
    2. Can i use my Existing Exchange certificate to get the above goal done ?
    3. What will be the steps and pre-requsite to achieve the Goal ?
    An Early reply would be appreciated !! 
    Amit

    Hi Amit 
    First Change SCP of Exchange 2010 CAS VIP to Exchange 2013 CAS VIP.
    Configure external  DNS records accordingly.DNS entries should be pointed to Exchange 2013 CAS from Exchange 2010 CAS.
    Ensure that you are having a seperate name for CAS array from external ews url
    Outlook Anywhere should be enabled and Url should be external URL which points to Exchange 2013.
    Authentication for OUtlook Anywhere should be - NTLM
    for OWA exchange 2010 - FBA and windows 
    Point your new CAS server to the firewall or TMG . Now from exchange 2013 all request will be proxied to 2010 users 
    You cannot use the same certificate . YOu need to add seperate entries as the host name for new servers will vary
    Apply a new certificate with all the required site names included in Exchange 2013 CAS.
    Whats more you can refer my blog as well 
    http://exchangequery.com/2014/05/02/things-to-consider-before-configuring-autodiscover-in-exchange-20102013-coexistence-scenarios/
    Cheers :)
    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

  • Coexistence with Exchange 2007 and 2013

    Hi everyone ,
    i migrated this week to exchange 2013 in coexistence with exchange 2007 ,,,, is it normal that i cannot create anymore a mailbox on the exchange 2007 server even with the console (ecp) in 2013 ?? 
    thanks

    Provided an answer on your other thread
    https://social.technet.microsoft.com/Forums/en-US/393a2406-5202-4d21-9583-2e4beed574be/create-mailbox-on-2007?forum=exchangesvrgeneral
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

  • ISA 2006 publish Exchange 2010 Outlook Anywhere with Kerberos Constrained Delegation

    Hi,
    I have two Exchange 2010 Sp1 CAS with Windows Network Loadbalancing. I set up an alternate Serviceaccount and mapped the http,ExchangeMDB,PRF and ExchangeAB SPNs.
    Then i published the Exchange Services via ISA 2006. OWA is working using Internet -> via NTLM -> ISA(webmail.domain.com) -> via KCD -> CAS-Array(ex2010.domain.com)
    I tried the same with Outlook Anywhere (RPC over HTTP) without success.
    Authentication to the ISA via NTLM works fine, but i think the isa server cannot delegate the Credentials successfully to the CAS-Server.
    The ISA Log looks like:
    Allowed Connection ISA 24.11.2011 15:50:40
    Log type: Web Proxy (Reverse)
    Status: 403 Forbidden
    Rule: Exchange 2010 RPC
    Source: Internal (172.16.251.33)
    Destination: (172.18.10.182:443)
    Request: RPC_OUT_DATA
    http://webmail.domain.com/rpc/rpcproxy.dll?ex2010.domain.com:6001
    Filter information: Req ID: 108b89d8; Compression: client=No, server=No, compress rate=0% decompress rate=0%
    Protocol: https
    So i always get a 403 Forbidden from the CAS.
    I the IIS logfile from the cas server i see this entry:
    2011-11-24 15:51:37 172.18.10.182 RPC_OUT_DATA /rpc/rpcproxy.dll ex2010.domain.com:6001 443 - <ISA IP> MSRPC 401 1 2148074254 203
    I use the same Listener for OWA and Outlook Anywhere. Authentication Methods are Basic and Integrated. I forward the request to a webfarm which exists of the two physical CAS. Internal Site Name is set to the NLB name ex2010.domain.com, SPN is set to http/ex2010.domain.com
    Thanks for your support

    Hi, i ran into the same Problem.
    the steps above solved mine too (Creating a custom AppPool which runs under LocalSystem).
    I wonder why they included only the Script: convertoabtovdir.ps1
    http://social.technet.microsoft.com/Forums/en-US/Forefrontedgegeneral/thread/dc24ccd3-378a-47cc-bbbf-48236f8fe5b0
    Ist this a supported configuration (changing AppPool of RPC)?

Maybe you are looking for