Quantcast
Channel: Exchange Server 2013 - Administration, Monitoring, and Performance 论坛
Viewing all articles
Browse latest Browse all 8719

Outlook 2013 shows single http connection to FQDN of CAS Server

$
0
0

Hi Everyone

I have recently installed a new Exchange 2013 Server in an existing exchange 2010 Organization.
I have already moved all the mailboxes to the new server and stopped the services on the old one.
Mailflow is working correctly, outlook clients can connect, and generally all seems to be working fine.

The Problem is, that I'm seeing a weird connection on the outlook clients, that I can't figure out.

You should know, that I set all my access URLs to a common hostname. let's say it's "mail.contoso.com"
If I run the set of commands noted below on my CAS, all access URLS are given back as set to that common hostname.

Get-OutlookAnywhere | Select Identity,Server,ExternalHostname,Internalhostname
Get-OwaVirtualDirectory | Select Identity,ExternalURL,InternalURL | fl
Get-ECPVirtualDirectory | select Identity,ExternalURL,InternalURL| fl
Get-ActiveSyncVirtualDirectory | Select Identity,InternalUrl,ExternalUrl| fl
Get-WebServicesVirtualDirectory | Select Identity,ExternalURL,InternalURL | fl
Get-OabVirtualDirectory | Select Identity,InternalURL,ExternalURL| fl
Get-ClientAccessServer | Select Name, Identity,AutoDiscoverServiceInternalURI | fl

The reason for doing this is so internal and external clients can use the same hostname to connect to exchange, and only a single SSL Certificate is needed.

Now, the connection I see that I'm stumped about is shown, when I Ctrl+Rightclick on the outlook taskbar icon and select "connection status"
It shows a lot of connections, all pointing to that common hostname "mail.contoso.com" that I configured.
Except for one. It shows the servers internal FQDN and is shown as HTTP, not HTTPS as the others. Also, it is of the type "Exchange Mail". But other "Exchange Mail" Connections are having the correct hostname displayed and are HTTPS Connections.

Is there any way to figure out what exactly that connection is made for and where it gets the FQDN of the server from?

It is not causing troubles and since it is HTTP not HTTPS, it also does not trigger a certificate warning.
However, I would really like to know what kind of connection this is, and why it is not secured.

The Outlook client in question is located internally, and does only have the one exchange account configured. It has some shared mailboxes attached, as well as a few shared calendars.
But all these other mailboxes also run on the same exchange 2013 server.

Any ideas as to what this connection is for?
Did I forget to set another value in Exchange?

Thanks for any hints or tips.





Viewing all articles
Browse latest Browse all 8719

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>