Hello!

We have a Terminal Server where published Outlook.

When user logon on server and use Outlook with the same user account - everything is all right. But when we use another account in Outlook (another from that we used to logon to server), it waits 20 minutes and then logons. In Wireshark traffic we see that server tries to bind with DC located in its Site on port 88, but then DC sends TCP Reset to it. After that Terminal server sends bind join request again and binds. But then goes to other DCs from different Sites, many of them are unavailable. I checked 88, 3268 and 389 ports with telnet on first DC, all they opened. All subnets linked to right Sites. Why Outlook tries all DCs in all Sites to authenticate? Or may be find Exchange Server?

Thank you.

HI,

we have issue connecting (outlook, Thunderbird) to exchange using SMTP outgoing setting

Our environment consist of (2 cas server behind loadbalancer, 2 DB with DAG enabled), exchange 2013

received connector configured as below:

--------------------------------------------------------------------

Identity         : SPT-EXC-MBX01\Client Proxy EXC-MBX01
Bindings         : {0.0.0.0:995, 0.0.0.0:993, 0.0.0.0:587, [::]:587}
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
PermissionGroups : AnonymousUsers, ExchangeUsers, ExchangeServers, Custom
RequireTLS       : False
EnableAuthGSSAPI : True

Identity         : SPT-EXC-MBX02\Client Proxy EXC-MBX02
Bindings         : {0.0.0.0:587, [::]:587}
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS, ExchangeServer
PermissionGroups : AnonymousUsers, ExchangeUsers, ExchangeServers, Custom
RequireTLS       : False
EnableAuthGSSAPI : True


Identity         : SPT-EXC-CAS03\Client Frontend EXC-CAS03
Bindings         : {[::]:587, 0.0.0.0:587}
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS
PermissionGroups : AnonymousUsers, ExchangeUsers, Custom
RequireTLS       : False
EnableAuthGSSAPI : True

Identity         : SPT-EXC-CAS04\Client Frontend EXC-CAS04
Bindings         : {[::]:587, 0.0.0.0:587}
AuthMechanism    : Tls, Integrated, BasicAuth, BasicAuthRequireTLS
PermissionGroups : AnonymousUsers, ExchangeUsers, Custom
RequireTLS       : False
EnableAuthGSSAPI : True

----------------------------------------------------------------------------

outlook configured to use smtp outgiong port 587 using TLS,

thunderbird detect it to use 587 and Kerbers/GSSAPI ( but can't send email also)

receive connector on both server show the below error:

-----------------------------

EXC-CAS03\Client Frontend EXC-CAS03,08D6AED1441FE0A0,30,10.10.210.107:587,10.10.210.13:38544,*,,Setting up client proxy session failed with error: 421 4.2.1 Unable to connect
EXC-CAS03\Client Frontend EXC-CAS03,08D6AED1441FE0A0,32,10.10.210.107:587,10.10.210.13:38544,*,,"Setting up client proxy session failed with error: 441 4.4.1 Error encountered while communicating with primary target IP address: ""Failed to connect. Winsock error code: 10061, Win32 error code: 10061."" Attempted failover to alternate host, but that did not succeed. Either there are no alternate hosts, or delivery failed to all alternate hosts. The last endpoint attempted was 10.10.210.103:465"
EXC-CAS03\Client Frontend EXC-CAS03,08D6AED1441FE0A0,34,10.10.210.107:587,10.10.210.13:38544,>,451 4.7.0 Temporary server error. Please try again later. PRX5 ,

-------------
and sometimes
EXC-CAS03\Client Frontend EXC-CAS03,08D6AED1441FE0A0,35,10.10.210.107:587,10.10.210.13:38544,-,,Remote(SocketError)

--------------------------------------------------

any help here please.

All of my Outlook Calendar entries are hidden in the calendar (The next several do show in the calendar pane of the mail windowl)  If I add an appointment, the counter on the left hand side increments, but the new entry is also hidden - unless it is recent enough to show in the mail window as noted above.

How do I "unhide" my calendar entries?

Windows server 2012 R2(ADFS + EXCHANGE)

Build: AdminDisplayVersion : Version 15.0 (Build 1263.5)

When setup according: https://technet.microsoft.com/en-us/library/dn635116(v=exchg.150).aspx

Error:

Event code: 3005
Event message: An unhandled exception has occurred.
Event time: 5/10/2017 2:31:40 AM
Event time (UTC): 5/9/2017 6:31:40 PM
Event ID: d6f90872e3d74ecb8f82ac8caf258337
Event sequence: 2
Event occurrence: 1
Event detail code: 0
 
Application information:
    Application domain: /LM/W3SVC/1/ROOT/owa-7-131388282971179591
    Trust level: Full
    Application Virtual Path: /owa
    Application Path: C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\owa\
    Machine name: MAIL
 
Process information:
    Process ID: 1268
    Process name: w3wp.exe
    Account name: NT AUTHORITY\SYSTEM
 
Exception information:
    Exception type: AdfsConfigurationException
    Exception message: Encryption certificate is absent
   at Microsoft.Exchange.Security.Authentication.Utility.GetCertificates()
   at Microsoft.Exchange.Security.Authentication.AdfsSessionSecurityTokenHandler.CreateTransforms()
   at Microsoft.Exchange.Security.Authentication.AdfsFederationAuthModule.FederatedAuthentication_ServiceConfigurationCreated(Object sender, ServiceConfigurationCreatedEventArgs e)
   at Microsoft.IdentityModel.Web.FederatedAuthentication.get_ServiceConfiguration()
   at Microsoft.IdentityModel.Web.HttpModuleBase.Init(HttpApplication context)
   at System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers)
   at System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context)
   at System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context)
   at System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext)

 
 
Request information:
    Request URL: https://mail.sky.lab:443/owa/
    Request path: /owa/
    User host address: 192.168.21.1
    User:  
    Is authenticated: False
    Authentication Type:  
    Thread account name: NT AUTHORITY\SYSTEM
 
Thread information:
    Thread ID: 25
    Thread account name: NT AUTHORITY\SYSTEM
    Is impersonating: False
    Stack trace:    at Microsoft.Exchange.Security.Authentication.Utility.GetCertificates()
   at Microsoft.Exchange.Security.Authentication.AdfsSessionSecurityTokenHandler.CreateTransforms()
   at Microsoft.Exchange.Security.Authentication.AdfsFederationAuthModule.FederatedAuthentication_ServiceConfigurationCreated(Object sender, ServiceConfigurationCreatedEventArgs e)
   at Microsoft.IdentityModel.Web.FederatedAuthentication.get_ServiceConfiguration()
   at Microsoft.IdentityModel.Web.HttpModuleBase.Init(HttpApplication context)
   at System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers)
   at System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context)
   at System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context)
   at System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext)
 
 
Custom event details:

ECP Access----------------

<!-- Web.Config Configuration File --><configuration><system.web><customErrors mode="Off"/></system.web></configuration>

-----------------------------

OWA ACCESS

https://mail.sky.lab/owa/auth/errorFE.aspx?httpCode=500

This isn't easy to explain but I'll try. Picture a 3 company scenario. Person from company A sends a meeting request to someone at company B. The person at Company B ropes in another person at Company C by forwarding the meeting invite. That invite will be sent with the originator's address as the Sender. With more and more companies doing anti-spoof enforcement(DMARC, etc), this means the message is going to be blocked.

I had a long dead exchange 2007 server. It was offline for some time with no problems as everyone was moved to exchange 2013.

I ran a recovery server for 2007 on a temporary server and then uninstalled 2007 from it as the old exchange server was heavily corrupt.

After exchange 2007 was removed from the network, I have several local workstations that are getting errors when using Outlook 2016:

Cannot start Microsoft Outlook. Cannot open the Outlook window. The set of folders cannot be opened. Network problems are preventing connection to Microsoft Exchange.

Closing and reopening Outlook sometimes works and sometimes get's the error and fails to open.

I'm using a self-signed certificate as I'm going to go to Exchange 2016 eventually. The certificate has both the 2013 and 2007 servers in it. The certificate wasn't changed after 2007 was uninstalled.

I've deleted and remade the Outlook profile on the affected workstations. I've rebooted them since the 2007 uninstall.

These workstations might have been powered off or rebooted when the recover server and uninstall were taking place.

I've deleted and reimported the certificate on the affected workstation and no change.

On one workstation, after the Outlook profile was deleted, and a new one was attempted to be created but it didn't auto detect the email attached to the account until after a reboot.

Is this limited to those workstations or will it spread to everyone?

Thanks!

I have sent out a meeting request through Outlook 2016.  Most attendees have responded. Sometime later I want to add attachments WITHOUT resending the meeting invite AND so delegates can open the attachments. 

'Send update' button resends the invite - not what I want to do.

'Save' only I can see attachments. 

Hello, we just recently updated our single Exchange 2013 server to CU21.  Outlook works as normal, however when attempting to use OWA, the following error is encountered:

:-(

something went wrong

Sorry, we can't get that information right now.  Please try again later.  If the problem continues, contact your helpdesk.

X-ClientId: CJPL - QMHG - 0EFG - NQVPPWDQ X-FEServer: 7Y7TV12 Date: 3/28/2019 3:39:44 PM

On the Exchange Server's application log, the following ASP.NET 1309 warning is displayed:

Thanks,

Joel

Hi everyone, I have the question as the title. 

When I access mailbox via OWA, I found account cannot be locked out immediately after a big enough number of failed logins. After some research, I found IIS caches account status locally and refresh it every 15 minutes, by default. I can reset it to some other values somehow. However, when I look at the failed login counter of this account maintained at AD, it increases immediately after each failed login. Then I'm wondering how it works. Does the IIS on Exchange report failed login result every time to AD (Domain Controller) but not update the user token? To some reason, I need to know how it works in more details.

I searched this problem for a while but all the web pages related to this problem post by other guys are shut off (seems an old question). Any thoughts or links are helpful! Thanks!

Hello,

I am brand new to exchange server and I would like to add a link on the sign in page for smart-card enabled users to sign in with their certificate, similar to how ADFS works but I don't want to force all authentication with smart card.

Jacob

Hey,

Correct me if I'm wrong, but isn't so that OWA should work on both ways when you have e.g. E2007 in old forest and E2013 on new forest?

I have ForestA with E2007 and ForestB with E2013. Some users are migrated from E2007 to E2013 and mail flows and availability services are working just fine. Also when user is moved they profiles are updated automatically.

But now the OWA added some grey hairs to me:
Case1:
when open OWA using the owa.ForestA.com E2007 users are working, E2013 users gets error:
Outlook Web Access could not find a mailbox for ForestB\User01. If the problem continues, contact technical support for your organization and tell them the following: The mailbox may be stored on a Microsoft Exchange 2000 or Microsoft Exchange 2003 server, or the Active Directory user account was created recently and has not yet replicated to the Active Directory site where this Client Access server is hosted. 

Case 2:
When OWA is opened using the owa.ForestB.com E2013 users are working, but E2007 users get an error:
X-OWA-Error: Microsoft.Exchange.Clients.Owa2.Server.Core.OwaUserHasNoMailboxAndNoLicenseAssignedException

E2013 users have Mail User object in ForestA and E2007 users have Mail User object on ForestB. Also both Mail User objects have the ExternalAddress attribute populated.

I have a feeling that this is based on the Autodiscover config, but I have not figure out which part of that..

Petri

HI Everyone

I have use of the outlook web application through work and I currently cannot send mail with attachments,

I am running windows 10

In Internet Explorer the send and the save buttons do not work however the other buttons work along that bar

In Google Chrome and Microsoft Edge the Send works but the Attachment window will not open, a block appears on the page for a moment where the window would be and then disappears.

Any help would be great

Hi all!

I have a strange situation with MAPI over HTTP protocol.

When user is on a corporate network all is OK and working just fine.

Situation A:

User goes to public network and open Outlook 2016/2019. In few seconds there will be username&password prompt. If you enter the credentials and save them everything is just fine and working OK.

Situation B:

I now have saved credentials from situation A. Now I login back to corpo network and change my password. Then I restart my PC and still on corpo network open Outlook. All OK.

Then I go to public network and credential prompt is back again.

So points are:

Outlook is working just fine when internal

Outlook will prompt for credentials when domain user is on external network

If you save the creds you are good till next password change

This is NOT OK as it should always use Windows logon session credentials

More info:

Mixed Outlook 2016/2019 with literally latest patches applied.

Exchange server 2013 CU22

Outlook anywhere set to negotiate and SSL offloading enabled

Certs are OK

Output of mapi virtual dir:

IISAuthenticationMethods        : {Ntlm, OAuth, Negotiate}
MetabasePath                    : IIS://INTERNALSERVER/W3SVC/1/ROOT/mapi
Path                            : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\mapi
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags         : {}
ExtendedProtectionSPNList       : {}
AdminDisplayVersion             : Version 15.0 (Build 1473.3)
Server                          : INTERNALSERVER
InternalUrl                     : https://mail.domain.com/mapi
InternalAuthenticationMethods   : {Ntlm, OAuth, Negotiate}
ExternalUrl                     : https://mail.domain.com/mapi
ExternalAuthenticationMethods   : {Ntlm, OAuth, Negotiate}
AdminDisplayName                :
ExchangeVersion                 : 0.10 (14.0.100.0)
Name                            : mapi (Default Web Site)

On AD we have set user logon name to proper UPN format: user@domain.com
Users are logging in to their PC with DOMAIN\user   format.

So why are only external users getting password prompts?

Thanks for help in advance :) !

Hi, I have an issue on my exchange infra but only on one node when the user open OWA and click on one mail nothing happen but with the light version of OWA i have a error message see below.

If a move the mailbox to another server it works fine.

If you could help me it will be great

Thanks in advance

Request
Url: https://ServerName.test.local:444/owa/forms/basic/BasicReadMessage.aspx?ae=Item&t=IPM.Note&id=RgAAAABtsX1mK%2fl4T7cbHzR429apBwD6k5YvymVgTa0EFcGxreiBAAAAAAEMAAD6k5YvymVgTa0EFcGxreiBAAABVrJOAAAJ
User host address: @IP
User: XXX
EX Address: /o=TEST/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Recipients/cn=3b139caa39f24b1e9220931d9623474d-Test-Michel-A
SMTP Address: XXX@test.local
OWA version: 15.0.1395.3
Mailbox server: ServerName.test.local

Exception
Exception type: System.UriFormatException
Exception message: Invalid URI: The format of the URI could not be determined.

Call stack

I have 3 exchange servers and one of them went down. I remember configuring a file with the IP of the exchange server that went down. I want to remove the IP so I can connect to the other servers. Anyone know what the file path/name of the file I am looking for. 

Hello

I'm hoping somebody might be able to assist me in finding an issue.

I've 2 mailboxes that, starting last month, intermittently request a password when using Outlook 2013 or 2016.

Both these mailboxes are in addition to the users main mailboxes, which don't prompt for details.

I've not been able to find anything wrong with the mailbox and Exchange reports the mailbox and database in good health.

This only seems to affect users that have a second mailbox on their profile, or in our case the users are given full access to the mailbox so it appears in their folder list within Outlook.

What's strange is, that we ignore the message or cancel it, you can still get to the mailbox.  If you decided to enter your domain credentials in, you're prompted to enter them 4 times.  Now, this could be a coincidence but we have 4 domain controllers so I wondered if it Outlook is trying to authenticate to each of those.

I've reset the password, removed the Windows Credentials (via Control Panel) and also re-created Outlook profiles, all have no affect.

I'm open to suggestions if anybody has any, please.  :o)

Thanks, Richard