Strange Exchange 2010 Traffic

Hi Guys,
I've a strange and mysterious Traffic dropping all the network caused by one of the HUB\CAS servers.
We have Exchange 2010 Environment 2 DAG Members and 2 HUB\CAS Servers we are using WNLB as a load-balancing Solution.
We have two physical hosts and we virtualized  the all servers mailbox and HUB\CAS 
MBX-01 --  HUB-CAS-01  on HV1
MBX-02 --  HUB-CAS-02  on HV2
When Both servers are up strange traffic begin and all telephony system "Avaia" go down.
I've disabled the replication on the MAPI network on both DAG members to ensure that the replication traffic goes throw the private network and changed the mode of NLB " Multicast and then Unicast" and nothing changed any ideas.
All servers running Exchange 2010 SP3.
Thanks 
Best Regards 
Mohamed Attia

Hi,
Based on the description, you used WNLB as a load-balancing Solution, however, it is recommended to use the HLB instead in the production environment.
From the "Network requirements" topic in the article
Planning for High Availability and Site Resilience, DAG must have a single MAPI network, which is used by a DAG member to communicate with other servers (for example, other Exchange 2013 servers or directory servers), and zero or more Replication networks,
which are networks dedicated to log shipping and seeding.
So nothing changed, even though you disabled the replication on the MAPI network on both DAG members. It is the expected behavior.
Do you connect the telephony system "Avaia" to an Unified Messaging server?
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Similar Messages

  • Strange Exchange 2010 error and dismounting

    Hi all
    I have migrate a server from Exchange 2007 to Exchange 2010 Sp3 R6 (In Windows 2008 r2).
    Everythings Works fine and i deleted the old Exchange server but now we have a problem.
    This problem occours 2 time in 20 day.
    The Outlook 2010 ask for credentials and the connetion to Exchange server i lost.
    I try to see the log files on Exchange server and i can se the MailboxDB is dismounting and try to Mount but fail.
    Soo i need manuelly to restart the services.
    On the system event viewer is this error
    The Microsoft Exchange Information Store service terminated unexpectedly.  It has done this 1 time(s).  The following corrective action will be taken in 5000 milliseconds: Restart the service.
    But this error can mean many Things so i took at look on Exchange HighAvaailAbility and can see 2 warning and 2 error befor the Outlook ask for password and lost connection.
    The warning is:
    1.
    Forcefully dismounting all the locally mounted databases on server 'GRANEXCH10.domain.dk' (Reason: TransientFailoverSuppression).
    2.
    There seems to be a database operation which is already in progress. Mount operation will be delayed until the previous operation is complete (databaseGuid='f28e179c-8cd1-4495-b569-936b58000162', error='MapiExceptionDismountInProgress: Unable to mount database.
    (hr=0x80004005, ec=2613)
    The error shows this:
    1.
    Direct mount operation failed for database (Guid=f28e179c-8cd1-4495-b569-936b58000162, Error=Microsoft.Mapi.MapiExceptionNetworkError: MapiExceptionNetworkError: Unable to mount database. (hr=0x80040115, ec=-2147221227)
    Diagnostic context:
        Lid: 16280   dwParam: 0x6D9      Msg: EEInfo: ComputerName: n/a
        Lid: 8600    dwParam: 0x6D9      Msg: EEInfo: ProcessID: 8644
        Lid: 12696   dwParam: 0x6D9      Msg: EEInfo: Generation Time: 2014-12-02 14:41:02:56
        Lid: 10648   dwParam: 0x6D9      Msg: EEInfo: Generating component: 2
        Lid: 14744   dwParam: 0x6D9      Msg: EEInfo: Status: 1753
        Lid: 9624    dwParam: 0x6D9      Msg: EEInfo: Detection location: 501
        Lid: 13720   dwParam: 0x6D9      Msg: EEInfo: Flags: 0
        Lid: 11672   dwParam: 0x6D9      Msg: EEInfo: NumberOfParameters: 4
        Lid: 8856    dwParam: 0x6D9      Msg: EEInfo: prm[0]: Unicode string: ncalrpc
        Lid: 8856    dwParam: 0x6D9      Msg: EEInfo: prm[1]: Unicode string:
        Lid: 12952   dwParam: 0x6D9      Msg: EEInfo: prm[2]: Long val: -1712963568
        Lid: 12952   dwParam: 0x6D9      Msg: EEInfo: prm[3]: Long val: 382312662
       at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, SafeExInterfaceHandle iUnknown, Exception innerException)
       at Microsoft.Mapi.ExRpcAdmin.MountDatabase(Guid guidStorageGroup, Guid guidMdb, Int32 ulFlags)
       at Microsoft.Exchange.Cluster.ActiveManagerServer.AmStoreHelper.Mount(Guid mdbGuid, MountFlags flags)
       at Microsoft.Exchange.Cluster.ActiveManagerServer.ActiveManagerCore.<>c__DisplayClassb.<MountDatabaseDirect>b__2()
       at Microsoft.Exchange.Cluster.Replay.FailoverPerformanceTrackerBase`1.RunTimedOperation(TOpCode opCode, Action operation)
       at Microsoft.Exchange.Cluster.ActiveManagerServer.ActiveManagerCore.MountDatabaseDirect(Guid mdbGuid, MountFlags storeFlags, AmMountFlags amMountFlags, AmDbActionCode actionCode)
       at Microsoft.Exchange.Cluster.ActiveManagerServer.AmRpcServer.<>c__DisplayClass19.<MountDatabaseDirect>b__18()
       at Microsoft.Exchange.Data.Storage.Cluster.HaRpcExceptionWrapperBase`2.RunRpcServerOperation(String databaseName, RpcServerOperation rpcOperation))
    2.
    Failed store mount for database 'Mailbox Database 1764181684' on GRANEXCH10.domain.dk (Duration=00:00:05.3267428, ErrorMessage=An Active Manager operation failed with a transient error. Please retry the operation. Error: MapiExceptionNetworkError: Unable
    to mount database. (hr=0x80040115, ec=-2147221227)
    Diagnostic context:
        Lid: 8600    dwParam: 0x6D9      Msg: EEInfo: ProcessID: 8644
        Lid: 12696   dwParam: 0x6D9      Msg: EEInfo: Generation Time: 2014-12-02 14:41:02:119
        Lid: 10648   dwParam: 0x6D9      Msg: EEInfo: Generating component: 2
        Lid: 14744   dwParam: 0x6D9      Msg: EEInfo: Status: 1753
        Lid: 9624    dwParam: 0x6D9      Msg: EEInfo: Detection location: 501
        Lid: 13720   dwParam: 0x6D9      Msg: EEInfo: Flags: 0
        Lid: 11672   dwParam: 0x6D9      Msg: EEInfo: NumberOfParameters: 4
        Lid: 8856    dwParam: 0x6D9      Msg: EEInfo: prm[0]: Unicode string: ncalrpc
        Lid: 8856    dwParam: 0x6D9      Msg: EEInfo: prm[1]: Unicode string:
        Lid: 12952   dwParam: 0x6D9      Msg: EEInfo: prm[2]: Long val: -1712963568
        Lid: 12952   dwParam: 0x6D9      Msg: EEInfo: prm[3]: Long val: 382312662 [Server: GRANEXCH10.domain.dk])
    And the samme error comes for public folder.
    I hope any of you has seen this befor because i have 200 postboxes so it really frustation because its appear randomlly.
    Thanks very mutch.

    Thank you!
    It helped but now i received another error:
    Looks the same, but the first line is:
    The following error was generated when "$error.Clear(); initialize-ExchangeConfigurationPermisssion -DomainController $RoleDomainController
    I tried running /PrepareDomain
    It was successfully but this error keeps coming.
    * The might been another error regarding to the domain before i run /PrepareDomain that solved.
    So you were able to install Exchange Server 2010 without anymore issue?
    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 2010 NLB on Nexus1000v - UCS - Cat4500

    Server Infrastructure: Microsoft Server 2012 Hyper-V installed on UCS Blade Servers. Network infrastructure is Nexus1000v for HyperV - FI62xx (endhost mode) uplinked to Catalyst 4510 Core Switch.
    Plan: Deploy Exchange 2010 NLB with two servers, each with one network card, NLB mode: IGMP multicast
    Configured:
    - Catalyst: static ARP for Cluster VIP
    - Nexus1000v: disabled IGMP snooping on servers VLAN
    All configuration is acting strangely, it works for some clients but not for others, if we stopped one node in NLB, more things stops working but some works fine.
    Nexus1000v configuration guide describes only NLB Unicast scenario.
    I suppose that something is missing in configuration.

    N1k only supports Unicast NLB.  For multicast & multicast+IGMP NLB there are a few things we can do that are not ideal because there will be excessive traffic flooding.
    http://www.cisco.com/en/US/docs/switches/datacenter/nexus1000/sw/4_2_1_s_v_1_5_1/release/notes/n1000v_rn.html#wp117941
    NLB with multicast (non-IGMP)-
    The NLB cluster uses a unicast IP address and non-IGMP multicast mac (03:bf) so IGMP is not used. N1k floods this frame.
    This method could overwhelm the network in some situations.
    1.    Use a dedicated VLAN for NLB VMs to limit mcast replication & flooding.
    NLB with Multicast+IGMP-
    Microsoft violates RFC2236 by putting a unicast IP in the IGMP Group messages.  N1k drops these messages since they violate the RFC.  CSCue32210 - "Add support for Microsoft NLB - Multicast+IGMP mode in Nexus 1000v" is targeted for a future release.  Before this feature exists we can configure the network as follows:
    1.    Dedicate a VLAN for NLB VMs to limit mcast replication & flooding.
    2.    Disable IGMP snooping on that vlan
    vlan 10
    no ip igmp snooping
    3.    Add a static entry on upstream router for NLB cluster IP & shared MAC.
    int vlan 10
    ip arp 14.17.124.40 0100.5e7f.7c28
    4.    Use mac-pinning configuration with manual pinning NLB vEths to one set of uplinks.  This will isolate flooding to a single upstream fabric interconnect & switch.
    port-profile type veth NLB-VM
      channel-group auto mode on mac-pinning relative
      pinning id 0 backup 1   <-these numbers may differ in your environment
    Matthew

  • After Exchange 2010 SP3 upgrade, UAG publised OWA is throwing a "You do not have permissions to view this folder or page" error

    Hi,
    We have an issue with our OWA page.  We are currently publishing OWA via UAG.
    We recently upgraded to Exchange 2010 SP3 and then SP3 Rollup7.  Since the upgrade, we are keep getting the following error after entering our credentials on the login page.  I've tried with every possible browser. 
    You do not have permissions to view this folder or page
    Strangely enough, the mobile phones are sending and receiving emails just fine, the phones use the same OWA link, so it's not an authentication issue, the phones login into the UAG servers with no issues.  I can see this on the Active Sessions screen
    on Web Monitor. 
    I've attempted to connect to the OWA by bypassing the UAG server, so putting in the local OWA address of one of my Exchange servers, it works... so the OWA page is up and running. 
    No error logs get generated on Web Monitor when we receive the permission error, I think this is because it's past authentication, it's on the Exchange layer. 
    Any insight would be helpful?  I'm assuming something changed on the Exchange side after the upgrade.
    Just in case, I've upgraded the UAG and TMG servers to the latest SP and Rollup packets.
    UAG > SP4
    TMG > SP2 Rollup 5

    I've found a solution; UAG requires Basic Authentication over OWA.  For some reason Integrated Windows Authentication got turned on after the SP3 upgrade.
    http://technet.microsoft.com/en-us/library/ee921443.aspx
    Turning Integrated Windows Authentication off via the Client Access OWA settings resolved the issue.  Though beware, you
    have do this on all your Client Access servers.  

  • [SOLVED] Can't add a node to the cluster with error (Exchange 2010 SP3 DAG Windows Server 2012)

    Hi there!
    I have a problem which makes me very angry already :)
    I have two servers Exchange 2010 SP3 with MB role started on Windows Server 2012. I decided to create a DAG.
    I have created the prestaged AD object for the cluster called msc-co-exc-01c, assigned necessary permissions and disabled it. Allowed through the Windows Firewall traffic between nodes and prepared the File Share Witness server.
    Then I have tried to add nodes. The first node has been added successfully, but the second node doesn't want to be added :). Now I can add only one node to the DAG. I tried to add different servers first, but only the first one was added.
    LOGS on the second nodes: 
    Application Log
    "Failed to initialize cluster with error 0x80004005." (MSExchangeIS)
    Failover Clustering Diagnostic Log
    "[VER] Could not read version data from database for node msc-co-exc-04v (id 1)."
    CMDLET Error:
    Summary: 1 item(s). 0 succeeded, 1 failed.
    Elapsed time: 00:06:21
    MSC-CO-EXC-02V
    Failed
    Error:
    A database availability group administrative operation failed. Error: The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode()
    (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed. [Server: msc-co-exc-04v.int.krls.ru]
    An Active Manager operation failed. Error An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed..
    This operation returned because the timeout period expired
    Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.174.1&t=exchgf1&e=ms.exch.err.ExC9C315
    Warning:
    Network name 'msc-co-exc-01c' is not online. Please check that the IP address configuration for the database availability group is correct.
    Warning:
    The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2014-11-17_13-54-56.543_add-databaseavailabiltygroupserver.log".
    Exchange Management Shell command attempted:
    Add-DatabaseAvailabilityGroupServer -MailboxServer 'MSC-CO-EXC-02V' -Identity 'msc-co-exc-01c'
    Elapsed Time: 00:06:21
    UPD:
    when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
    I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
    on both nodes.
    It's confused me, because there is normal connectivity between these DAG members through the main interface.
    Please, help me if you can.

    Hi, Jared! Thank you for the reply.
    Of course I did it already :) I have new info:
    when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
    I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
    on both nodes.
    It's confused me, because there is normal connectivity between these DAG members through the main interface.

  • Exchange 2010 is suddenly unmanageable

    Hi --
    On a SBS 2011 box running Exchange 2010 SP2, Exchange has suddenly become unmanageable. I have no idea what happened overnight to cause this. But I've been trying to get this fixed for two hours already, with no luck.
    Nobody can open OWA. From anywhere. Including from the server itself. IE network diagnostics reveal that "The device or resource (whatever) is not set up to accept connections on port "https".
    The Exchange Management Console won't open. I get the error "The attempt to connect to http://server/PowerShell using "Kerberos" authentication failed: Connecting to remote server failed with the following error message: The WinRM client cannot process the
    request. The authentication mechanism requested by the client is not supported by the server or unencrypted traffic is disabled in the service configuration. Verify the unencrypted traffic setting in the service configuration or specify one of the authentication
    mechanisms supported by the server. To use Kerberos, specify the computer name as the remote destination. Also verify that the client computer and the destination computer are joined to a domain. To use Basic, specify the computer name as the remote destination,
    specify Basic authentication and provide user name and password. Possible authentication mechanisms reported by server: For more information, see the about_Remote_Troubleshooting Help topic."
    Opening an Exchange Management Shell results in the error:
    >>>>>>>>>>>>>>>>>>>>>>>>
    VERBOSE: Connecting to server.domain.local
    [server.domain.local] Connecting to remote server failed with the following error message : The WinRM client sent a
    request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned
    by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troublesh
    ooting Help topic.
        + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
       eption
        + FullyQualifiedErrorId : PSSessionOpenFailed
    VERBOSE: Connecting to server.domain.local
    [server.domain.local] Connecting to remote server failed with the following error message : The WinRM client sent a
    request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned
    by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troublesh
    ooting Help topic.
        + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
       eption
        + FullyQualifiedErrorId : PSSessionOpenFailed
    VERBOSE: Connecting to server.domain.local
    [server.domain.local] Connecting to remote server failed with the following error message : The WinRM client sent a
    request to an HTTP server and got a response saying the requested HTTP URL was not available. This is usually returned
    by a HTTP server that does not support the WS-Management protocol. For more information, see the about_Remote_Troublesh
    ooting Help topic.
        + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExc
       eption
        + FullyQualifiedErrorId : PSSessionOpenFailed
    Failed to connect to an Exchange server in the current site.
    Enter the server FQDN where you want to connect.:
    <<<<<<<<<<<<<<<<<<<<<<<<
    I have checked and double-checked bindings, Kerberos settings, and a slew of other things. I have reset IIS and rebooted the server multiple times. I can't get past this. Everything referenced in the following articles was checked and verified to be as the
    articles said they should be:
    http://blogs.technet.com/b/bshukla/archive/2012/05/04/exchange-management-shell-error-500-internal-server-error.aspx
    http://technet.microsoft.com/en-us/library/ff607221%28v=EXCHG.80%29.aspx
    http://support.microsoft.com/kb/2028305
    I installed and ran the EMTshooter script referenced in http://blogs.technet.com/b/exchange/archive/2010/12/07/resolving-winrm-errors-and-exchange-2010-management-tools-startup-failures.aspx. This it what it reported:
    >>>>>>>>>>>>>>>>>>>>>>>>
    Welcome to the Exchange Management Troubleshooter!
    We recommend that you run the troubleshooter after making changes to
    IIS to ensure that connectivity to Exchange Powershell is unaffected.
    Checking IIS Service...
    Checking the Exchange Install Path variable...
    Checking the Powershell Virtual Directory...
    Checking the Powershell vdir SSL setting...
    Checking the Powershell vdir path setting...
    Checking HTTP Port 80...
    Checking HTTP Port 80 Host Name...
    Testing for errors...
    VERBOSE: Connecting to server.domain.local
    [server.domain.local] Connecting to remote server failed with the following error message : The WinRM client sent a r
        + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportExcep
        + FullyQualifiedErrorId : PSSessionOpenFailed
    The Exchange Management Troubleshooter successfully completed connecting to:
    server.domain.local
    Failed to connect to any Exchange Server in the current site.
    Problem found:
    Looking for error...
    These are the possible causes for this error:
    1. The default http binding has been removed from the Default Web Site. Exchange Powershell needs http to be configured
    so that the IP Address is "All Unassigned", the Port is "80", and the Host Name is "".  A common scenario for changing t
    his is if you are running multiple web sites, and attempting to set up a redirect to https://mail.company.com/owa by req
    uiring SSL on the Default Web Site, and creating another web site to do the redirect back to the SSL-enabled website. Re
    mote PowerShell requires port 80 to be available on the Default Web Site for all Internet Addresses. If you want to set
    up an automatic redirect to /owa and redirect http requests to https, you should follow the instructions located at:
    http://technet.microsoft.com/en-us/library/aa998359(EXCHG.80).aspx
    and follow the directions under the section:
    "For a Configuration in Which SSL is required on the Default Web Site or on the OWA Virtual Directory in IIS 7.0."
    2. The http binding on the Default Web Site has been modified, and the Hostname field configured. To correct this issue,
     you need to clear out the Hostname field under the port 80 bindings on the Default Web Site.
    After each error is resolved, close this window and re-run the tool to check for additional problems.
    <<<<<<<<<<<<<<<<<<<<<<<<
    However, the bindings on the Default Web site are correct (I've checked them multiple times).
    And the server's System, Security and Application logs are devoid of anything that could even begin to explain what is going on.
    And this was all working yesterday ...
    I have automatic replies to modify/remove and have no way to get to them. Outlook on the PCs won't pull up Automatic Replies, claiming that the server is unavailable. On the other hand, email is coming and going fine ...
    I need to get this fixed _now_. Does anybody know how to get to the bottom of this -- and what could have possibly happened to cause this in the first place?
    Thanks
    CL

    Hi --
    C:\Users\Administrator>winrm quickconfig
    WinRM already is set up to receive requests on this machine.
    WinRM already is set up for remote management on this machine.
    C:\Users\Administrator>winrm invoke Restore winrm/Config
    Restore_OUTPUT
    C:\Users\Administrator>winrm get winrm/config
    Config
        MaxEnvelopeSizekb = 150
        MaxTimeoutms = 60000
        MaxBatchItems = 32000
        MaxProviderRequests = 4294967295
        Client
            NetworkDelayms = 5000
            URLPrefix = wsman
            AllowUnencrypted = false
            Auth
                Basic = true
                Digest = true
                Kerberos = true
                Negotiate = true
                Certificate = true
                CredSSP = false
            DefaultPorts
                HTTP = 5985
                HTTPS = 5986
            TrustedHosts
        Service
            RootSDDL = O:NSG:BAD:P(A;;GA;;;BA)S:P(AU;FA;GA;;;WD)(AU;SA;GWGX;;;WD)
            MaxConcurrentOperations = 4294967295
            MaxConcurrentOperationsPerUser = 15
            EnumerationTimeoutms = 60000
            MaxConnections = 25
            MaxPacketRetrievalTimeSeconds = 120
            AllowUnencrypted = false
            Auth
                Basic = false
                Kerberos = true
                Negotiate = true
                Certificate = false
                CredSSP = false
                CbtHardeningLevel = Relaxed
            DefaultPorts
                HTTP = 5985
                HTTPS = 5986
            IPv4Filter = *
            IPv6Filter = *
            EnableCompatibilityHttpListener = false
            EnableCompatibilityHttpsListener = false
            CertificateThumbprint
        Winrs
            AllowRemoteShellAccess = true
            IdleTimeout = 180000
            MaxConcurrentUsers = 5
            MaxShellRunTime = 2147483647
            MaxProcessesPerShell = 15
            MaxMemoryPerShellMB = 150
            MaxShellsPerUser = 5
    C:\Users\Administrator>winrm enumerate winrm/config/listener
    C:\Users\Administrator>netstat -aon | find ":80"
      TCP    0.0.0.0:80             0.0.0.0:0              LISTENING       4
      TCP    0.0.0.0:808            0.0.0.0:0              LISTENING       4856
      TCP    192.168.214.20:80      192.168.214.20:15979   ESTABLISHED     4
      TCP    192.168.214.20:15979   192.168.214.20:80      ESTABLISHED     6336
      TCP    192.168.214.20:15980   192.168.214.20:80      TIME_WAIT       0
      TCP    192.168.214.20:15997   192.168.214.20:8014    SYN_SENT        8528
      TCP    [::]:80                [::]:0                 LISTENING      
    4
      TCP    [::]:808               [::]:0                 LISTENING      
    4856
      TCP    [fe80::adee:f7f8:e6f6:1f35%13]:80  [fe80::adee:f7f8:e6f6:1f35%13]:15926
      TIME_WAIT       0
      TCP    [fe80::adee:f7f8:e6f6:1f35%13]:80  [fe80::adee:f7f8:e6f6:1f35%13]:15973
      TIME_WAIT       0
      TCP    [fe80::adee:f7f8:e6f6:1f35%13]:80  [fe80::adee:f7f8:e6f6:1f35%13]:15978
      TIME_WAIT       0
      TCP    [fe80::adee:f7f8:e6f6:1f35%13]:80  [fe80::adee:f7f8:e6f6:1f35%13]:15982
      TIME_WAIT       0
      TCP    [fe80::adee:f7f8:e6f6:1f35%13]:80  [fe80::adee:f7f8:e6f6:1f35%13]:15984
      TIME_WAIT       0
      TCP    [fe80::adee:f7f8:e6f6:1f35%13]:80  [fe80::adee:f7f8:e6f6:1f35%13]:15989
      TIME_WAIT       0
      TCP    [fe80::adee:f7f8:e6f6:1f35%13]:80  [fe80::adee:f7f8:e6f6:1f35%13]:15990
      TIME_WAIT       0
    C:\Users\Administrator>
    PID 4 is c:\Windows\system32\ntoskrnl.exe
    PID 6336 is DataCollectorSvc.exe
    I'm still getting all the same errors.

  • Relay issue from Unix across Exchange 2003 OWA server in Exchange 2010 environment

    Hi,
    I'm trying to resolve an issue.  We have one Exchange 2003 server left in our environment. The rest is now Exchange 2010.  We are working to decommission this server. Monitoring the SMTP logs, I am working with the various groups to get the traffic
    off this server and onto the Exchange 2010 environment.
    The issue we are finding is with a work flow. This Java app for eBis sends email to users. This is done correctly through Exchange 2010 and gets delivered from our HUB/CAS servers to the target user mailbox. This email has several links the user must click
    for approving or rejecting requests. Upon clicking Approve, a new email window opens (we use Outlook 2010).  The TO address is in the format of [email protected]  Upon clicking Send, our Exchange 2010 HUB/CAS servers accept the
    email, because one of our send connectors has, as address space, *.domain.corp.  However, the email address being used it not an alias on any Exchange 2010 mailbox, so it appears Exchange 2010 is sending this email on to the Exchange 2003 server, which
    also is an SMTP server.  I *think* this server is looking at the address after @ to determine where to send it (ebisserver.domain.corp, which is valid in our DNS), and sends it on to that server, where the java "listener" program intercepts
    the mail, processes it and then saves it to a file somewhere.
    We are at a loss as to how to get Exchange 2010 to do this instead of Exchange 2003... once this traffic is eliminted from Exchange 2003, I can proceed with decommission of this server.  Any help troubleshooting this issue is appreciated.

    The only reason the Exchange 2010 server would route outbound mail through an Exchange 2003 server is that you have an SMTP Connector defined on the Exchange 2003 server that has a more specific domain than you have on the Exchange 2010 server.  You
    should be able to see all your Send Connectors (an SMTP Connector on Exchange 2003 looks like a Send Connector in Exchange 2010) by running Get-SendConnector.
    Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

  • Exchange 2010 coexist with exchange 2013

    Hi All ,
    Planning to have a coexistence scenario in my environment which is mentioned below
    Exchange 2010 - ambiguous url in place - OA enabled 
    For mapi/rpc traffic - mail.domain.in -  exchange 2010
    For https traffic - mail.domain.in - exchange 2010
    mail.domain.in will get resolved in to cas array in exchange 2010 .
    After coexistence On our side we are not going to move the mail.domain.in namespace to exchange 2013 , Instead of that we are going to use a new namespace in exchange 2013 for internal outlook anywhere and it will be outlookmail.domain.in and for the remaining
    exchange 2013 services like pop,imap,owa,active sync url's,external OA will be having mail.domain.in as same as exchange 2010 namespace.
    just consider outlookmail.domain.in is available on the san certificate installed in exchange 2013.
    Note : 
    On my ide I would assume Internal outlook 2010 mapi users will connect directly to exchange 2010 servers on the namespace mail.domain.in
    Likewise i would assume Internal outlook anywhere 2013 users will connect directly to exchange 2013 servers on the namespace outlookmail.domain.in
    Services like pop,imap,owa,active sync ,external OA connections for both exchange 2010 and exchange 2013 from the external world will be routed from firewall to exchange 2013 servers .Then https traffic for exchange 2010 mailbox users will be proxied to 2010
    exchange server via exchange 2013 server.
    question : I would like to know above mentioned scenario is possible or not ?
    On my side I know in my environment i am having ambiguous url's in place and at the same time i don't want the exchange 2010 internal outlook users to connect via exchange 2013 rpc over http even though OA is enabled on exchange 2010.
    So simply i can say i need my internal exchange 2010 mailbox users has to connect via tcp/ip.
    All of you tell me your valuable suggestions.
    Regards
    S.Nithyanandham

    Hi,
    Going Straight to the point... and answering your question...
    The scenario above IS possible For a while... But going ahead in the migration process, You'd face problems once the Exch2013 doesn't know how to handle MAPI connections:
    As per Exchange Team...
    In this scenario where both the MAPI/RPC and HTTP workloads are using the same FQDN you cannot successfully move the FQDN to CAS 2013 without
    breaking your MAPI/RPC client connectivity entirely. I repeat, your MAPI/RPC clients will start failing to connect via MAPI/RPC once
    their DNS cache expires after the shared FQDN is moved to CAS 2013.
    As their recommendation, and I would tell you too by experience, the best option is to really use different internal and external URLs for the clients to connect to.
    change your design to use a specific internal-only FQDN for MAPI/RPC clients. If you are in the middle of a 2010 deployment using an Ambiguous
    URL I recommend you change your ClientAccessArray FQDN to a unique name and update the mailbox database RpcClientAccessServer values
    on all Exchange 2010 mailbox databases accordingly. Fixing this item mid-migration to Exchange 2010 or even in your fully migrated environment will ensure any newly created or manually repaired Outlook profiles are protected, but it will not automatically
    fix existing Outlook clients with the old value in the server field. 
    So the overall for this first point is to enable the OA for all internal users, so as to ease the migration process in the future, even if for the time being its not necessary.
    Also another point you should take into consideration is the version of yours OLK versions, as the minimum supported are as per below:
    Outlook 2007: 12.0.6665.5000 (SP3 + the November 2012 Public Update or any later PU)
    Outlook 2010: 14.0.6126.5000 (SP1 + the November 2012 Public Update or any later PU)
    Outlook 2013: 15.0.4420.1017 (RTM or later)
    I don't know the size of you network, but it might be necessary for you to use an inventory tool in order to identify that.
    As advised, its really worthy to have a look at the following article, thus to clarify your view about this issue.
    Ambiguous URLs and their effect on Exchange 2010 to Exchange 2013 Migrations
    From <http://blogs.technet.com/b/exchange/archive/2013/07/17/3574451.aspx> 
    Hope it can help you!
    Cheers,
    Think before you ask, give detail as much as possible, then ask and you will get help! Always have in mind, people do not guess! :)

  • Exchange 2007 to Exchange 2010 Cross Forest

    Hi
    We have a scenario where we have an Exchange 2007 organization (Org A - Source) and a separate Exchange 2010 organization (Org B - Target). Both the organizations (AD Forests) have two way trusts between them.
    We want to have our Exchange 2007 users have their mailboxes hosted on Exchange 2010 organization. Meaning that the user (AD) accounts of Org A will remain in Forest A but there mailboxes will be available on Exchange 2010 servers in Org B. So we don’t need
    a user / group migration stuff here and mailbox data on Exchange 2007 servers is also not critical (not required to be migrated) so we will be creating new disabled accounts and mailboxes in Org B for each user in Org A and connect the mailboxes. There will
    be a brief period of co-existence between two Orgs (to enable mail-flow) until all the users have their mailboxes active in Org B. Need to figure out a way to achieve this.
    We are planning to follow the steps below:
    Setup name resolution between the forests (although basic connectivity is there and we can ping servers in one forest using IP Addresses from other forest) –
    Please suggest if this is necessary or we can get away with it?
    Setup SMTP namespace sharing for Exchange 2007 SMTP Domain name
    Add Exchange 2007 SMTP domain as authoritative domain to E2K10
    Create EAP for new SMTP Domain
     SMTP Connector Creation for Direct E-mail Routing (Co-exist) Between Forests
    Create disabled Mail Enabled (not Mailbox Enabled) User or Mail Enabled Contact in Org B.
    Can we use Prepare-MoveRequest.ps1 script to create these?
    Once a mail enabled user / contact is created in Org B for all the users, change incoming traffic from Internet for Org A SMTP domain to hit HT server in Org B
    Make changes to Exchange 2010 certificate and install new certificate
    Select a batch of users every day, create new mailbox for them using scripts in Org B and delete the corresponding contact in Org B
    Can someone please confirm if this is correct and point out something I am missing?
    Is there any other way to achieve the same goal?
    Thanks
    Taranjeet Singh
    zamn

    Hi Everyone
    Thanks for the inputs so far. I need to confirm some steps to establish direct email flow unless all the mailboxes are created in target organization, can somebody have a look at the steps below and confirm if they are correct or add something that
    I missed here:
    Setup source Exchange organization:
    a) Add unique SMTP domain for source organization, like @source.local. This domain will be added to all mail enabled objects in this organization and will be used for internal routing only
         i) Add to Accepted Domains list
         ii) Create EAP to add domain to existing objects
    b) Use manual means to stamp SMTP domain to objects in source organization on objects that don’t have EmailAddressPolicyEnabled set to False
    c) Create Send Connector to target forest. The target domain should also have a unique e-mail address, like @target.company.com (in our case 19 SMTP domains including JUBL.COM)
         i) Include the valid SMTP domains and the unique one for internal routing
             (source.local)
         ii) Point to a smart host in the target forest
    d) Set existing SMTP domain (JubilantRetail.com) as “Internal Relay Domain”. The target Exchange org will be authoritative for this domain
    Setup target Exchange organization
    a) Create Send Connector to unique SMTP domain in source forest. Includes shared name space (source.local) and @JubilantRetail.com
    b) Set Default receiver connector, being used by source forest, to allow anonymous connections
    c) Add shared SMTP domain (source.local) to Accepted Domains list as authoritative
    d) Create EAPs to replicate the SMTP domains (e:g JubilantRetail.com and source.local) in the source environment
    Thanks
    Taranjeet Singh
    zamn

  • Exchange 2003 to Exchange 2010 migration steps

    HI ,
    I have migrated windows 2003 to windows 2008.Its successfully migrated.
    Second phase i have a plan to migrate exchange 2003 to exchange 2010.
    My current setup
    windows 2008 64bit (DC)
    exchange 2003 sp2
    1
    Bring the Exchange organization to Exchange Native Mode.
    2
    Upgrade all Exchange Servers to Exchange Server 2003 Service Pack 2.
    3
     Bring the AD forest and domains to Windows Server 2003 Functional (or higher) levels.
    4
     Upgrade at least one Global Catalog domain controller in each AD site that will house Exchange Server
    to Windows Server 2003 SP2 or greater.
    5
     Prepare a Windows Server 2008 (RTM or R2) x64 edition server for the first Exchange 2010 server.
    6
    Install the AD LDIFDE tools on the new Exchange 2010 server (to upgrade the schema).
    7
     Install any necessary prerequisites (WWW for CAS server role).
    8
    Run setup on the Exchange 2010 server, upgrade the schema, and prepare the forest and domains. (Setup runs all in one step or separate
    at the command line.)
    9
     Install CAS server role servers and configure per 2010 design. Validate functionality.
    10
    Transfer OWA, ActiveSync, and Outlook Anywhere traffic to new CAS servers.
    11
     Install Hub Transport role and configure per 2010 design.
    12
     Transfer inbound and outbound mail traffic to the HT servers.
    13
     Install mailbox servers and configure Databases (DAG if needed).
    14
    Create public folder replicas on Exchange 2010 servers using pfmigrate.wsf script, AddReplicaToPFRecursive.ps1, or Exchange 2010
    Public Folder tool.
    15
    Move mailboxes to Exchange Server 2010 using Move Mailbox Wizard or Power Shell.
    16
     Rehome the Offline Address Book (OAB) generation server to Exchange Server 2010.
    17
    1Rehome the public folder hierarchy on the new Exchange Server 2010 admin group.
    18
     Transfer all Public Folder Replicas to Exchange Server 2010 Public folder store(s).
    19
     Delete Public and Private Information Stores from Exchange 2003 server(s).
    20
     Delete Routing Group Connectors to Exchange Server 2003.
    21
    Delete Recipient Update Service agreements using ADS Edit.
    22
    Uninstall all Exchange 2003 servers.
    This  is my plan to migrate.But  i have a doubt in installing exchange 2010 in this scenario.
    Is it necessary to use
    Setup.com /PrepareLegacyExchangePermissions,
    Please help me what excactly i have to do

    I think that <a href="http://www.micronobal.com/blog/2014/5/1/exchange-server-migration-to-the-cloud-ensure-a-seamless-transition" title="Exchange Server Migrations">Exchange Server
    Migration</a>  is a very delicate project and to be taken very seriously as it is a detailed work as well. You are giving us some great tips. 
    Some Articles I would like to share as well:
    <a href="http://www.micronobal.com/blog/2014/5/1/exchange-server-migration-to-the-cloud-ensure-a-seamless-transition" title="Exchange Server Migration to the Cloud - Seamless Transition.">
    Exchange Server Migration to the Cloud</a>
      It takes a lot of time and effort to get it right. Thank you for helping
    Here some information about services for migrations
    <a href="http://www.micronobal.com/business/cloud/advancedtechnologyservices" title="Migrate your email to the cloud.">Business Email migration</a>

  • Unusual 550 5.7.1 Command Not Allowed being sent from Exchange 2010

    Greetings,
    I have an Exchange 2010 server that seems to be rejecting some emails from external domains with 550 5.7.1 Command Not Allowed. I've taken a look at the SMTP Receive logs (below) and can't seem to find any reason why the emails are getting rejected. The sequence
    immediately prior to the 550 being sent is highlighted in bold.
    #Fields: date-time sequence-number local-endpoint remote-endpoint event data context
    2014-11-05T08:42:27.545Z 0 192.168.3.5:25 212.82.97.117:53913 +  
    2014-11-05T08:42:27.545Z 1 192.168.3.5:25 212.82.97.117:53913 * SMTPSubmit SMTPAcceptAnySender SMTPAcceptAuthoritativeDomainSender AcceptRoutingHeaders Set Session Permissions
    2014-11-05T08:42:27.545Z 2 192.168.3.5:25 212.82.97.117:53913 > 220 SERVER.domain.com Microsoft ESMTP MAIL Service ready at Wed, 5 Nov 2014 03:42:27 -0500 
    2014-11-05T08:42:27.657Z 3 192.168.3.5:25 212.82.97.117:53913 < EHLO nm34-vm3.bullet.mail.ir2.yahoo.com 
    2014-11-05T08:42:27.658Z 4 192.168.3.5:25 212.82.97.117:53913 > 250-SERVER.domain.com Hello [212.82.97.117] 
    2014-11-05T08:42:27.658Z 5 192.168.3.5:25 212.82.97.117:53913 > 250-SIZE 
    2014-11-05T08:42:27.658Z 6 192.168.3.5:25 212.82.97.117:53913 > 250-PIPELINING 
    2014-11-05T08:42:27.658Z 7 192.168.3.5:25 212.82.97.117:53913 > 250-DSN 
    2014-11-05T08:42:27.658Z 8 192.168.3.5:25 212.82.97.117:53913 > 250-ENHANCEDSTATUSCODES 
    2014-11-05T08:42:27.658Z 9 192.168.3.5:25 212.82.97.117:53913 > 250-STARTTLS 
    2014-11-05T08:42:27.658Z 10 192.168.3.5:25 212.82.97.117:53913 > 250-X-ANONYMOUSTLS 
    2014-11-05T08:42:27.658Z 11 192.168.3.5:25 212.82.97.117:53913 > 250-AUTH NTLM 
    2014-11-05T08:42:27.658Z 12 192.168.3.5:25 212.82.97.117:53913 > 250-X-EXPS GSSAPI NTLM 
    2014-11-05T08:42:27.658Z 13 192.168.3.5:25 212.82.97.117:53913 > 250-8BITMIME 
    2014-11-05T08:42:27.658Z 14 192.168.3.5:25 212.82.97.117:53913 > 250-BINARYMIME 
    2014-11-05T08:42:27.658Z 15 192.168.3.5:25 212.82.97.117:53913 > 250-CHUNKING 
    2014-11-05T08:42:27.658Z 16 192.168.3.5:25 212.82.97.117:53913 > 250-XEXCH50 
    2014-11-05T08:42:27.658Z 17 192.168.3.5:25 212.82.97.117:53913 > 250-XRDST 
    2014-11-05T08:42:27.658Z 18 192.168.3.5:25 212.82.97.117:53913 > 250 XSHADOW 
    2014-11-05T08:42:27.756Z 19 192.168.3.5:25 212.82.97.117:53913 < STARTTLS 
    2014-11-05T08:42:27.756Z 20 192.168.3.5:25 212.82.97.117:53913 > 220 2.0.0 SMTP server ready 
    2014-11-05T08:42:27.756Z 21 192.168.3.5:25 212.82.97.117:53913 *  Sending certificate
    2014-11-05T08:42:27.756Z 22 192.168.3.5:25 212.82.97.117:53913 * CN=SERVER Certificate subject
    2014-11-05T08:42:27.756Z 23 192.168.3.5:25 212.82.97.117:53913 * CN=SERVER Certificate issuer name
    2014-11-05T08:42:27.756Z 24 192.168.3.5:25 212.82.97.117:53913 * 3BF7DF215EB42FB14FAE1BF7E4369E06 Certificate serial number
    2014-11-05T08:42:27.756Z 25 192.168.3.5:25 212.82.97.117:53913 * 01494AD746353CCE0F198CE83AD4D6A8592C29F5 Certificate thumbprint
    2014-11-05T08:42:27.756Z 26 192.168.3.5:25 212.82.97.117:53913 * SERVER;SERVER.domain.com Certificate alternate names
    2014-11-05T08:42:28.059Z 27 192.168.3.5:25 212.82.97.117:53913 < EHLO nm34-vm3.bullet.mail.ir2.yahoo.com 
    2014-11-05T08:42:28.059Z 28 192.168.3.5:25 212.82.97.117:53913 *  TlsDomainCapabilities='None'; Status='NoRemoteCertificate'
    2014-11-05T08:42:28.060Z 29 192.168.3.5:25 212.82.97.117:53913 > 250-SERVER.domain.com Hello [212.82.97.117] 
    2014-11-05T08:42:28.060Z 30 192.168.3.5:25 212.82.97.117:53913 > 250-SIZE 
    2014-11-05T08:42:28.060Z 31 192.168.3.5:25 212.82.97.117:53913 > 250-PIPELINING 
    2014-11-05T08:42:28.060Z 32 192.168.3.5:25 212.82.97.117:53913 > 250-DSN 
    2014-11-05T08:42:28.060Z 33 192.168.3.5:25 212.82.97.117:53913 > 250-ENHANCEDSTATUSCODES 
    2014-11-05T08:42:28.060Z 34 192.168.3.5:25 212.82.97.117:53913 > 250-AUTH NTLM LOGIN 
    2014-11-05T08:42:28.060Z 35 192.168.3.5:25 212.82.97.117:53913 > 250-X-EXPS GSSAPI NTLM 
    2014-11-05T08:42:28.060Z 36 192.168.3.5:25 212.82.97.117:53913 > 250-8BITMIME 
    2014-11-05T08:42:28.060Z 37 192.168.3.5:25 212.82.97.117:53913 > 250-BINARYMIME 
    2014-11-05T08:42:28.060Z 38 192.168.3.5:25 212.82.97.117:53913 > 250-CHUNKING 
    2014-11-05T08:42:28.060Z 39 192.168.3.5:25 212.82.97.117:53913 > 250-XEXCH50 
    2014-11-05T08:42:28.060Z 40 192.168.3.5:25 212.82.97.117:53913 > 250-XRDST 
    2014-11-05T08:42:28.060Z 41 192.168.3.5:25 212.82.97.117:53913 > 250 XSHADOW 
    2014-11-05T08:42:28.158Z 42 192.168.3.5:25 212.82.97.117:53913 < MAIL FROM:<[email protected]> 
    2014-11-05T08:42:28.158Z 43 192.168.3.5:25 212.82.97.117:53913 * 08D11121D08C9A95;2014-11-05T08:42:27.545Z;1 receiving message
    2014-11-05T08:42:28.159Z 44 192.168.3.5:25 212.82.97.117:53913 > 250 2.1.0 Sender OK 
    2014-11-05T08:42:28.364Z 45 192.168.3.5:25 212.82.97.117:53913 < RCPT TO:<[email protected]> 
    2014-11-05T08:42:28.364Z 46 192.168.3.5:25 212.82.97.117:53913 > 250 2.1.5 Recipient OK 
    2014-11-05T08:42:28.462Z 47 192.168.3.5:25 212.82.97.117:53913 < DATA 
    2014-11-05T08:42:29.275Z 48 192.168.3.5:25 212.82.97.117:53913 * Tarpit for '0.00:00:05' 
    2014-11-05T08:42:34.278Z 49 192.168.3.5:25 212.82.97.117:53913 > 550 5.7.1 Command not allowed 
    2014-11-05T08:42:34.521Z 50 192.168.3.5:25 212.82.97.117:53913 < RSET 
    2014-11-05T08:42:34.521Z 51 192.168.3.5:25 212.82.97.117:53913 * Tarpit for '0.00:00:05' 
    2014-11-05T08:42:39.523Z 52 192.168.3.5:25 212.82.97.117:53913 > 250 2.0.0 Resetting 
    2014-11-05T08:42:39.621Z 53 192.168.3.5:25 212.82.97.117:53913 < MAIL FROM:<[email protected]> 
    2014-11-05T08:42:39.621Z 54 192.168.3.5:25 212.82.97.117:53913 * 08D11121D08C9A95;2014-11-05T08:42:27.545Z;2 receiving message
    2014-11-05T08:42:39.621Z 55 192.168.3.5:25 212.82.97.117:53913 > 250 2.1.0 Sender OK 
    2014-11-05T08:42:39.719Z 56 192.168.3.5:25 212.82.97.117:53913 < RCPT TO:<[email protected]> 
    2014-11-05T08:42:39.719Z 57 192.168.3.5:25 212.82.97.117:53913 > 250 2.1.5 Recipient OK 
    2014-11-05T08:42:39.817Z 58 192.168.3.5:25 212.82.97.117:53913 < DATA 
    2014-11-05T08:42:39.838Z 59 192.168.3.5:25 212.82.97.117:53913 * Tarpit for '0.00:00:05' 
    2014-11-05T08:42:44.837Z 60 192.168.3.5:25 212.82.97.117:53913 > 550 5.7.1 Command not allowed 
    2014-11-05T08:42:45.078Z 61 192.168.3.5:25 212.82.97.117:53913 < RSET 
    2014-11-05T08:42:45.078Z 62 192.168.3.5:25 212.82.97.117:53913 * Tarpit for '0.00:00:05' 
    2014-11-05T08:42:50.079Z 63 192.168.3.5:25 212.82.97.117:53913 > 250 2.0.0 Resetting 
    2014-11-05T08:42:50.177Z 64 192.168.3.5:25 212.82.97.117:53913 < QUIT 
    2014-11-05T08:42:50.177Z 65 192.168.3.5:25 212.82.97.117:53913 > 221 2.0.0 Service closing transmission channel 
    2014-11-05T08:42:50.177Z 66 192.168.3.5:25 212.82.97.117:53913 -  Local
    I have another entry in my logs fro the same sender coming from the same IP which yields the same results. Strangely enough, there are other entries from the same sender coming from different IPs which are delivered just fine. 
    The sender has stated that they only get the rejects when replying to emails from my domain, not when he sends fresh emails.
    Why would Exchange send the 550 5.7.1 in response to a DATA command when it responds with 354 Start mail input; end with <CRLF>.<CRLF> to other DATA commands from a different server?
    Bit of an odd problem, any help would be greatly appreciated.
    Thanks,
    B. Colt

    Thanks for the input Mr. Crowley. I've dumped the Receive Connector configurations, everything seems to be at default values except for logging (I set it to verbose). 
    RunspaceId                              : 17f0dc01-c2a9-45ce-812d-5d47688b6650
    AuthMechanism                           : Tls, BasicAuth, BasicAuthRequireTLS
    Banner                                  : 
    BinaryMimeEnabled                       : True
    Bindings                                : {12.34.56.78:25}
    ChunkingEnabled                         : True
    DefaultDomain                           : 
    DeliveryStatusNotificationEnabled       : True
    EightBitMimeEnabled                     : True
    BareLinefeedRejectionEnabled            : False
    DomainSecureEnabled                     : False
    EnhancedStatusCodesEnabled              : True
    LongAddressesEnabled                    : False
    OrarEnabled                             : False
    SuppressXAnonymousTls                   : False
    AdvertiseClientSettings                 : False
    Fqdn                                    : mail.MYDOMAIN.com
    Comment                                 : 
    Enabled                                 : True
    ConnectionTimeout                       : 00:10:00
    ConnectionInactivityTimeout             : 00:05:00
    MessageRateLimit                        : unlimited
    MessageRateSource                       : IPAddress
    MaxInboundConnection                    : 5000
    MaxInboundConnectionPerSource           : 20
    MaxInboundConnectionPercentagePerSource : 2
    MaxHeaderSize                           : 64 KB (65,536 bytes)
    MaxHopCount                             : 60
    MaxLocalHopCount                        : 12
    MaxLogonFailures                        : 3
    MaxMessageSize                          : 100 MB (104,857,600 bytes)
    MaxProtocolErrors                       : 5
    MaxRecipientsPerMessage                 : 200
    PermissionGroups                        : ExchangeUsers, ExchangeServers
    PipeliningEnabled                       : True
    ProtocolLoggingLevel                    : Verbose
    RemoteIPRanges                          : {0.0.0.0-255.255.255.255}
    RequireEHLODomain                       : False
    RequireTLS                              : False
    EnableAuthGSSAPI                        : False
    ExtendedProtectionPolicy                : None
    LiveCredentialEnabled                   : False
    TlsDomainCapabilities                   : {}
    Server                                  : MYSERVER
    SizeEnabled                             : Enabled
    TarpitInterval                          : 00:00:05
    MaxAcknowledgementDelay                 : 00:00:30
    AdminDisplayName                        : 
    ExchangeVersion                         : 0.1 (8.0.535.0)
    Name                                    : default MYDOMAIN.com
    DistinguishedName                       : CN=default MYDOMAIN.COM,CN=SMTP Receive Connectors,CN=Protocols,CN=MYSERVER,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=My
    Company,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=DOMAIN
                                              ,DC=local
    Identity                                : SERVER\default MYDOMAIN.COM
    Guid                                    : 04d418d8-06f6-4e13-8f3b-439f9c6509b0
    ObjectCategory                          : MYDOMAIN.COM/Configuration/Schema/ms-Exch-Smtp-Receive-Connector
    ObjectClass                             : {top, msExchSmtpReceiveConnector}
    WhenChanged                             : 10/1/2014 3:53:53 PM
    WhenCreated                             : 3/1/2012 2:33:10 PM
    WhenChangedUTC                          : 10/1/2014 7:53:53 PM
    WhenCreatedUTC                          : 3/1/2012 7:33:10 PM
    OrganizationId                          : 
    OriginatingServer                       : SERVER.MYDOMAIN.COM
    IsValid                                 : True
    RunspaceId                              : 17f0dc01-c2a9-45ce-812d-5d47688b6650
    AuthMechanism                           : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
    Banner                                  : 
    BinaryMimeEnabled                       : True
    Bindings                                : {:::25, 0.0.0.0:25}
    ChunkingEnabled                         : True
    DefaultDomain                           : 
    DeliveryStatusNotificationEnabled       : True
    EightBitMimeEnabled                     : True
    BareLinefeedRejectionEnabled            : False
    DomainSecureEnabled                     : False
    EnhancedStatusCodesEnabled              : True
    LongAddressesEnabled                    : False
    OrarEnabled                             : False
    SuppressXAnonymousTls                   : False
    AdvertiseClientSettings                 : False
    Fqdn                                    : SERVER.MYDOMAIN.COM
    Comment                                 : 
    Enabled                                 : True
    ConnectionTimeout                       : 00:10:00
    ConnectionInactivityTimeout             : 00:05:00
    MessageRateLimit                        : unlimited
    MessageRateSource                       : IPAddress
    MaxInboundConnection                    : 5000
    MaxInboundConnectionPerSource           : unlimited
    MaxInboundConnectionPercentagePerSource : 100
    MaxHeaderSize                           : 64 KB (65,536 bytes)
    MaxHopCount                             : 60
    MaxLocalHopCount                        : 12
    MaxLogonFailures                        : 3
    MaxMessageSize                          : 100 MB (104,857,600 bytes)
    MaxProtocolErrors                       : 5
    MaxRecipientsPerMessage                 : 5000
    PermissionGroups                        : AnonymousUsers, ExchangeUsers, ExchangeServers, ExchangeLegacyServers
    PipeliningEnabled                       : True
    ProtocolLoggingLevel                    : Verbose
    RemoteIPRanges                          : {192.168.1.0(255.255.255.0), ::-ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff, 0.0.0.0-255.255.255.255}
    RequireEHLODomain                       : False
    RequireTLS                              : False
    EnableAuthGSSAPI                        : False
    ExtendedProtectionPolicy                : None
    LiveCredentialEnabled                   : False
    TlsDomainCapabilities                   : {}
    Server                                  : MYSERVER
    SizeEnabled                             : EnabledWithoutValue
    TarpitInterval                          : 00:00:05
    MaxAcknowledgementDelay                 : 00:00:30
    AdminDisplayName                        : 
    ExchangeVersion                         : 0.1 (8.0.535.0)
    Name                                    : Default SERVER
    DistinguishedName                       : CN=Default SERVER,CN=SMTP Receive Connectors,CN=Protocols,CN=SERVER,CN=Servers,CN=Exchange Administrative Group (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=MY
    COMPANY,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=MYDOMAIN,DC=l
                                              ocal
    Identity                                : SERVER\Default SERVER
    Guid                                    : fc6ab381-1cf9-4edb-bec4-3a2c092cd4e3
    ObjectCategory                          : mydomain/Configuration/Schema/ms-Exch-Smtp-Receive-Connector
    ObjectClass                             : {top, msExchSmtpReceiveConnector}
    WhenChanged                             : 10/1/2014 3:56:23 PM
    WhenCreated                             : 2/6/2012 11:51:58 AM
    WhenChangedUTC                          : 10/1/2014 7:56:23 PM
    WhenCreatedUTC                          : 2/6/2012 4:51:58 PM
    OrganizationId                          : 
    OriginatingServer                       : SERVER.mydomain.com
    IsValid                                 : True
    I really don't want to turn off the tarpitting and expose myself to tons of spam, although I do have anti-spam filters running. 
    Any thoughts?
    Thanks again,
    B. Colt
    Brian Colt

  • Exchange 2010 Autodiscovery & Outlook Anywhere kind of but really not working

    This is driving me nuts. We have a single Exchange Server 2010 running (everything is on one box). It works fine internally (all Outlook clients can see and grab the login info from the user login). OWA works from outside, mail delivers nicely. My problems
    all seem to stem around some mysterious problem in autodiscover and outlook anywhere.
    Our domain is internally like this: mycompany2.com and outside like this: mycompanyllc.com
    So the mail server inside looks like server1.mycompany2.com and outside: mail.mycompanyllc.com - from what I can see it's all set up correctly in both.
    I've run the connectivity analyzer and apart from a minor certificate warning ('Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled) it passes every test on the site for EAS and Outlook Anywhere
    (and for good measure I ran everything, all green checks!). Autodiscover works in the test, everything gets found and pointed to the right place.
    When I have a user that wants to configure Outlook 2010 or 2013 outside
    the org. they start the wizard, type their name, their email, their password. The server or user can't be found and no matter what they do it won't find it. If you go in and manually configure the
    internal server name, domain, username you can connect. It just won't set it up automatically. The odd thing is, in the analyzer the autodiscovery XML is found and downloaded fine, all the server name info and detail is displayed.
    In Outlook 2013, both Exchange and EAS connection doesn't work even though phones can be set up through EAS (although they require the same kind of manual setup--autodiscover doesn't seem to work even though it keeps telling me everything
    is fine).
    I'm at wits end, all the tests show it's working, but in the real world the server can't be found. It's right on the DNS servers, it's right in the tests, it responds correctly manually. I'd love users to be able to set up their own mail without a 10 page
    printout of all the manual settings. It's all relatively late model hardware, Outlook 2010 or 2013, and a fully patched up to date Exchange 2010 server. Anyone have an idea?
    Curt Kessler - FLC

    We don't use TMG we use a WatchGuard Firewall and it is configured to allow all traffic to this server (that's why manual works fine with Outlook and OWA).
    When I run the get-autodiscovervirtualdirectory it returns my internal server under the Server, and nothing more, so this possibly could be it?? I'm definitely not good at IIS at all, I would need guidance to investigate that further...
    This is my EXRCA results, the first fail is because it tests the root of mydomain.com rather than mail.mydomain.com which is a different server. I've replaced some names for security purposes:
    The Microsoft Connectivity Analyzer is attempting to test Autodiscover for
    [email protected].
    Autodiscover was tested successfully.
    Test Steps
    Attempting each method of contacting the Autodiscover service.
    The Autodiscover service was tested successfully.
    Test Steps
    Attempting to test potential Autodiscover URL https://mydomain.com/AutoDiscover/AutoDiscover.xml
    Testing of this potential Autodiscover URL failed.
    Test Steps
    Attempting to resolve the host name franklinlc.com in DNS.
    The host name resolved successfully.
    Additional Details
    IP addresses returned: 76.79.142.101
    Testing TCP port 443 on host franklinlc.com to ensure it's listening and open.
    The port was opened successfully.
    Testing the SSL certificate to make sure it's valid.
    The SSL certificate failed one or more certificate validation checks.
    Test Steps
    The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server franklinlc.com on port 443.
    The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
    Additional Details
    Remote Certificate Subject: CN=apps.franklinlc.com, OU=Domain Control Validated, O=apps.franklinlc.com, Issuer: SERIALNUMBER=07969287, CN=Go Daddy Secure Certification Authority, OU=http://certificates.godaddy.com/repository, O="GoDaddy.com, Inc.", L=Scottsdale,
    S=Arizona, C=US.
    Validating the certificate name.
    Certificate name validation failed.
     <label for="testSelectWizard_ctl12_ctl06_ctl00_ctl00_ctl02_ctl01_tmmArrow">Tell
    me more about this issue and how to resolve it</label>
    Additional Details
    Host name franklinlc.com doesn't match any name found on the server certificate CN=apps.franklinlc.com, OU=Domain Control Validated, O=apps.franklinlc.com.
    Attempting to test potential Autodiscover URL https://autodiscover.mydomain.com/AutoDiscover/AutoDiscover.xml
    Testing of the Autodiscover URL was successful.
    Test Steps
    Attempting to resolve the host name autodiscover.mydomain.com in DNS.
    The host name resolved successfully.
    Additional Details
    IP addresses returned: 76.xx.xx.xx this is the mail server IP address
    Testing TCP port 443 on host autodiscover.franklinlc.com to ensure it's listening and open.
    The port was opened successfully.
    Testing the SSL certificate to make sure it's valid.
    The certificate passed all validation requirements.
    Test Steps
    The Microsoft Connectivity Analyzer is attempting to obtain the SSL certificate from remote server autodiscover.mydomain.com on port 443.
    The Microsoft Connectivity Analyzer successfully obtained the remote SSL certificate.
    Additional Details
    Remote Certificate Subject: CN=mail.franklinlc.com, OU=Domain Control Validated, O=mail.mydomain.com, Issuer: SERIALNUMBER=xxxxxxxxxxxxx, CN=Go Daddy Secure Certification Authority, OU=http://certificates.godaddy.com/repository, O="GoDaddy.com, Inc.", L=Scottsdale,
    S=Arizona, C=US.
    Validating the certificate name.
    The certificate name was validated successfully.
    Additional Details
    Host name autodiscover.mydomain.com was found in the Certificate Subject Alternative Name entry.
    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 = 9/28/2012 10:20:20 PM, NotAfter = 9/28/2015 10:20:20 PM
    Checking the IIS configuration for client certificate authentication.
    Client certificate authentication wasn't detected.
    Additional Details
    Accept/Require Client Certificates isn't configured.
    Attempting to send an Autodiscover POST request to potential Autodiscover URLs.
    The Microsoft Connectivity Analyzer successfully retrieved Autodiscover settings by sending an Autodiscover POST.
    Test Steps
    The Microsoft Connectivity Analyzer is attempting to retrieve an XML Autodiscover response from URL https://autodiscover.mydomain.com/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>Curt Kessler</DisplayName>
          <LegacyDN>/o=mydomain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=Curt Kessler</LegacyDN>
          <DeploymentId>14a1e263-943a-4609-865c-ba22802e45aa</DeploymentId>
        </User>
        <Account>
          <AccountType>email</AccountType>
          <Action>settings</Action>
          <Protocol>
            <Type>EXCH</Type>
            <Server>FLC5.internaldomainname.com</Server>
            <ServerDN>/o=mydomain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=FLC5</ServerDN>
            <ServerVersion>7383807B</ServerVersion>
            <MdbDN>/o=mydomain/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=FLC5/cn=Microsoft Private MDB</MdbDN>
            <ASUrl>https://mail.mydomain.com/ews/exchange.asmx</ASUrl>
            <OOFUrl>https://mail.mydomain.com/ews/exchange.asmx</OOFUrl>
            <OABUrl>https://mail.mydomain.com/OAB/9c85c0c4-48f4-4aa8-99b2-f640651b130a/</OABUrl>
            <UMUrl>https://mail.mydomain.com/ews/UM2007Legacy.asmx</UMUrl>
            <Port>0</Port>
            <DirectoryPort>0</DirectoryPort>
            <ReferralPort>0</ReferralPort>
            <PublicFolderServer>FLC5.internaldomainname.com</PublicFolderServer>
            <AD>PRIME.internaldomainname.com</AD>
            <EwsUrl>https://mail.mydomain.com/ews/exchange.asmx</EwsUrl>
            <EcpUrl>https://flc5.internaldomainname.com/ecp/</EcpUrl>
            <EcpUrl-um>?p=customize/voicemail.aspx&amp;exsvurl=1</EcpUrl-um>
            <EcpUrl-aggr>?p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1</EcpUrl-aggr>
            <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;</EcpUrl-mt>
            <EcpUrl-ret>?p=organize/retentionpolicytags.slab&amp;exsvurl=1</EcpUrl-ret>
            <EcpUrl-sms>?p=sms/textmessaging.slab&amp;exsvurl=1</EcpUrl-sms>
          </Protocol>
          <Protocol>
            <Type>EXPR</Type>
            <Server>mail.mydomain.com</Server>
            <ASUrl>https://mail.mydomain.com/ews/exchange.asmx</ASUrl>
            <OOFUrl>https://mail.mydomain.com/ews/exchange.asmx</OOFUrl>
            <OABUrl>https://mail.mydomain.com/OAB/9c85c0c4-48f4-4aa8-99b2-f640651b130a/</OABUrl>
            <UMUrl>https://mail.mydomain.com/ews/UM2007Legacy.asmx</UMUrl>
            <Port>0</Port>
            <DirectoryPort>0</DirectoryPort>
            <ReferralPort>0</ReferralPort>
            <SSL>On</SSL>
            <AuthPackage>Ntlm</AuthPackage>
            <EwsUrl>https://mail.mydomain.com/ews/exchange.asmx</EwsUrl>
            <EcpUrl>https://mail.mydomain.com/ecp/</EcpUrl>
            <EcpUrl-um>?p=customize/voicemail.aspx&amp;exsvurl=1</EcpUrl-um>
            <EcpUrl-aggr>?p=personalsettings/EmailSubscriptions.slab&amp;exsvurl=1</EcpUrl-aggr>
            <EcpUrl-mt>PersonalSettings/DeliveryReport.aspx?exsvurl=1&amp;IsOWA=&lt;IsOWA&gt;&amp;MsgID=&lt;MsgID&gt;&amp;Mbx=&lt;Mbx&gt;</EcpUrl-mt>
            <EcpUrl-ret>?p=organize/retentionpolicytags.slab&amp;exsvurl=1</EcpUrl-ret>
            <EcpUrl-sms>?p=sms/textmessaging.slab&amp;exsvurl=1</EcpUrl-sms>
          </Protocol>
          <Protocol>
            <Type>WEB</Type>
            <Port>0</Port>
            <DirectoryPort>0</DirectoryPort>
            <ReferralPort>0</ReferralPort>
            <Internal>
              <OWAUrl AuthenticationMethod="Basic, Ntlm, Fba, WindowsIntegrated">https://flc5.internaldomainname.com/owa/</OWAUrl>
              <Protocol>
                <Type>EXCH</Type>
                <ASUrl>https://mail.mydomain.com/ews/exchange.asmx</ASUrl>
              </Protocol>
            </Internal>
            <External>
              <OWAUrl AuthenticationMethod="Fba">https://mail.mydomain.com/owa/</OWAUrl>
              <Protocol>
                <Type>EXPR</Type>
                <ASUrl>https://mail.mydomain.com/ews/exchange.asmx</ASUrl>
              </Protocol>
            </External>
          </Protocol>
        </Account>
      </Response>
    </Autodiscover>
    I've replaced my public domain with mydomain.com and my internal domain with internaldomainname.com, and hidden the IP, but everything else is the same. The tests all pass
    Curt Kessler - FLC

  • Exchange 2010 DAG netowrk replications issues - Causing database copies to be disconnected and resynchronizing.

    My
    environment is as follows.<o:p></o:p>
    We have 3 exchange 2010 servers.<o:p></o:p>
    EX1, EX2, DREX1. All servers are exchange 2010 14.2 build 247.5<o:p></o:p>
    EX1 and EX2 have two nics, one LAN and one for BACKUP <o:p></o:p>
    The dag is configured to to communicate to all three.<o:p></o:p>
    The IP for EX1 is 192.168.100.51 - LAN, switch A; 160.100.3.51 - BACKUP, switch B<o:p></o:p>
    The IP for EX2 is 192.168.100.52 - LAN, switch A; 160.100.3.52 - BACKUP, switch B<o:p></o:p>
    DREX1 is located in another network. It is in another building connected via vpn. The ip
    for DREX1 is 192.170.100.51. There is no BACKUP network for this server<o:p></o:p>
    (These are not the actual address, but the concept is similar)<o:p></o:p>
    The dag network configuration is as follows.<o:p></o:p>
    DAGNetworkDR has a subnet of 192.170.100.0/24; Network Interface of 192.170.100.51<o:p></o:p>
    DAGNetwork01 (LAN) has a subnet of 192.168.100.0/24; Network Interfaces of 192.168.100.51
    and 192.168.100.52<o:p></o:p>
    DAGNetwork02 (BACKUP) has a subnet of 160.100.3.0/24; Network Interfaces of
    160.100.3.51 and 160.100.3.52<o:p></o:p>
    Last Friday, 3/7/14 something happened.<o:p></o:p>
    To lead up to that, I noticed the issue because we have DPM 2010 making 15minute express
    full backups of our exchange databases when I reviewed the backup jobs, the
    exchange database backups using dpm2010 failed all weekend long starting at
    11:00pm that Friday.<o:p></o:p>
    The issue that occurred was that the database copies went to a status of Disconnected and
    Resynchronizing, and after about 30 seconds, the status would show
    Resynchronizing.<o:p></o:p>
    All attempts to resolve this with the research methods failed.  Deleting the
    logs and reseeding failed, suspending, then rebuilding failed.<o:p></o:p>
    Creating a new database worked, creating a database copy worked, but seeding the copy
    failed. All with the same pattern, a status of Disconnected and
    Resynchronizing, and after about 30 seconds, and the status would show
    Resynchronizing.<o:p></o:p>
    The database was mounted on EX2, and seeding to EX1
    DREX1 has no issues.<o:p></o:p>
    All the DAG networks were in a good status, all Green and all up.  I could ping from
    EX1 to EX2 and from EX2 to EX1 on both networks fine.<o:p></o:p>
    In the middle of the week, about 3/12/14, we resolved the issue. We rebooted EX1, no
    fix, but after rebooting EX2, it all resolved.  It did a fail over to DREX1. I think it failed to do the failover to EX1. However, when it came back up, it was happy, it was reseeding slowly. After about an hour and a half, it
    was all healthy.<o:p></o:p>
    We thought it was all good EXCEPT, on Friday night at 11:00pmish on 3/14/14, the same
    issue occurred; a status of Disconnected and Resynchronizing, and after about
    30 seconds, the status would show Resynchronizing.<o:p></o:p>
    The database was mounted on EX2 and seeding to EX1 again. I did not notice the
    issue until I performed my review of the backup jobs again on Monday.<o:p></o:p>
    Late Monday morning, my boss and I were looking at more articles, but all the same results,
    delete the database copy and reseed. Which we knew would not work.<o:p></o:p>
    I mentioned that it was strange because the networks were all up. What made us try the next
    scenarios was just "luck" I guess. I made a statement about not remembering
    which networks DAG replication took place over.  Again, we have a LAN and
    a BACKUP network.  Bother were listed to use replication, so we decided to
    disable replication over the BACKUP network in the EMC. Immediately, the
    database copies switch to healthy and started seeding.<o:p></o:p>
    Later that evening I enabled replication over the BACKUP network and it failed again with
    a status of Disconnected and Resynchronizing, and after about 30 seconds, the
    status would show Resynchronizing.  I disabled the replication over the
    BACKUP network and the database copy went back to healthy<o:p></o:p>
    The last round of windows updates were pushed to these boxes the Friday before the
    issues began, 2/28/14.  I don't believe the updates to be the issue. <o:p></o:p>
    Can anyone make any suggestions as to where to look?  It worked with the BACKUP
    network enabled to so long that is eluding me as to why the issues would start
    all of a sudden. I am also confident that the switch configuration for the
    BACKUP network has not been changed at all in at least 2-3 months.  I am
    still open to look at the config. Please help if you can.<o:p></o:p>
     <o:p></o:p>
    Lastly, this is more of a monitoring thing, if anyone can suggest a good way to monitor
    the database copies so that I can be alerted when the status changes.  We
    use WhatsUpGold 16.2 to monitor the devices.  <o:p></o:p>
    Thanks for any future assistance.<o:p></o:p>
    Ian
    Ian

    You don't have to enable the Replication on Backup Network.
    You should collapse your DAG network.
    http://blogs.technet.com/b/timmcmic/archive/2011/09/26/exchange-2010-collapsing-dag-networks.aspx
    http://blogs.technet.com/b/samdrey/archive/2012/12/04/exchange-2010-dag-collapse-the-mapi-networks-in-a-dag.aspx
    Post the result of Below command:
    Get-DatabaseAvailabilityGroupNetwork 
    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.

  • Outlook 2010 using Exchange 2010 - cannot send this item after updating draft email

    I have a client who has the following setup.
    SBS 2011 server (Exchange 2010) and a Windows 2008 R2 Terminal Server (with Office 2010 SP1 installed).
    This particular user has a Windows XP PC with Office 2010 SP1 installed (joined to SBS 2011 domain).
    This user creates a email at their office on their PC and saves it in draft to continue working on it when they get home.
    At home they RDP into the terminal server and load outlook and start updating their saved (Draft) email.  They then try to send it and the following error pops up.  "Cannot send this item".
    If they try to save the changes they have made it pops up with "The operation failed".
    I have tried various settings all with the same results.
    Office 2010, Office 2010 SP1, Online mode and Cache mode (on the Windows XP PC).
    Any ideas? 

    Hi Rajkumar,
    OK. After further testing I have narrowed it down to the email signature?
    If I save a draft email in Outlook on the Fat client (Windows XP + Office 2010), then go straight into Drafts folder and open the email and add one line of text and try to send or save again it fails.
    If I don't have a signature, it works fine.
    I currently trying to determine what part of the signature it doesn't like (it is quite a large signature, multiple images and a disclaimer etc).  I'm having mixed results - I can remove the signature totally from the draft email and then it will save
    or send fine. 
    Strange that it can save the email to Draft in the 1st place but doesn't like updating it a 2nd time???
    I have also created a new outlook profile (online mode) with the same results.

  • Exchange 2010 /hosting shared mailbox issue

    Hello everyone.
    I had an issue come up in our Exchange 2010 with /hosting switch deployment (currently at SP2).
    We have several organizations and shared mailboxes configured and working on some. We add Full access permissions via Powershell + Send as rights and it auto configures and works just fine.
    Last week though, one of several people that uses a specific shared mailbox started getting the error: "Unable to open your default e-mail folders. The Microsoft Exchange Server computer is not available. Either there are network problems or the
    Microsoft Exchange Server computer is down for maintenance." (Error ID: 300)
    The other users can still work just fine. Configuring the account in another PC shows the same problem (so it's not the local profile).
    Creating 2 users, giving nr1 full access to nr2 generates the same error.
    In another org though, i was able to give full access to another acount to an existing user and it worked (although the auto-mapping didn't, had to add it manually)
    I'm out of ideias. Any sugestions?
    EDIT: Did a couple more tests on another Org. On this one everything works with the shared folder access with old and new accounts but strangely the auto-mapping doesn't.
    It seems that this is an issue with the mapping.
     

    Hi,
    From your description, I recommend you manually update or create your Outlook profile with RPC encryption and check the result. Here is the steps on Outlook 2007 for your reference:
    1. Select your profile, and then click Properties, click E-mail Accounts.
    2. Select the Microsoft Exchange Server account, and then click Change.
    3. In the dialog box that contains your mailbox server and user name, click More Settings.
    4. In the Microsoft Exchange Server dialog box, click the Security tab.
    5. Click to select the Encrypt data between Microsoft Office Outlook and Microsoft Exchange check box, and then click OK.
    6. Click Next, and then click Finish.
    For more information, here is a kb for your reference.
    Connection issues and error messages in Outlook for a mailbox on a server that is running Exchange Server 2010
    http://support.microsoft.com/kb/2735060
    Hope this can be helpful to you.
    Best regards,
    Amy Wang
    TechNet Community Support

Maybe you are looking for