Exchange 2013-SP1/Outlook 2013 connectivity issue.

We couldn't make Outlook 2013 (latest updates) to connect to our Exchange 2013-SP1 through the Internet.
Any PC inside the LAN (on the domain or outside the domain) can connect normally.
Any PC outside the LAN (WAN) cannot connect, it keep showing this error:
"The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
OWA is working fine from the WAN, smartphones (Android & Apple) are also working fine from the WAN.
Port 443 is open on the firewall.
So what we are missing!

Hi,
Firstly, I'd like to say, in Exchange 2013 SP1, Outlook 2013 SP1 clients may use MAPI over HTTP to connect to the server.
Before going further, let's confirm if they use MAPI over HTTP: Get-OrganizationConfig | FL MapiHttpEnabled
If the value of the above property is true, I recommend the following troubleshooting:
1. Check if your Exchange 2013 SP1 server is running on Windows Server 2012 R2.
2. Check MAPI virtual directory settings: get-MapiVirtualDirectory |fl
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Similar Messages

Cannot connect to an Exchange account in Outlook 2013 using "Microsoft Exchange Server or Compatible Service"

Dear All,
I cannot connect to my Exchange account in Outlook 2013 using "Microsoft Exchange Server or Compatible Service".
First I would like to present my network environment, I have 4 physical servers;
The first one is holding the Domain Controller 1, IP@: 192.168.1.10
The second server is holding the additional Domain Controller which it is DC2, IP@: 192.168.1.11
The third server is holding the Exchange 2013 Mailbox, IP@: 192.168.1.15
And the last server is holding the Exchange 2013 CAS-HT, IP@: 192.168.1.16
I am doing the steps below:
1-Creating a new profile in outlook and start configuring the exchange account by entering the IP address of the Exchange-CAS Server, 192.168.1.16
2-entering the account name: [email protected]
3-Go to "More Settings" > "Connection" > "Connect to Microsoft Exchange using HTTP" > and entering the "Exchange Proxy Settings"
4-type the exchange CAS Server URL, https://192.168.1.16
5-Check the "Connect using SSL Only"
6-Authentication Settings: "NTLM Authentication", and pressing Apply
7-When I press the "Check Name" button, a message occurred> "The action cannot be completed. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action".
8-I go back to the "Exchange Proxy Settings" and I Uncheck the "Connect using SSL Only" and pressing Apply
9-i press the "Check Name" Button, a small window occurred to enter a Username and Password, so I enter the Administrator username and the administrator password and pressing "OK", but nothing is changed, I tried to enter my
username and password in the small window and I still got the same result.
I cannot verify the account name and I cannot complete the process.
I appreciate you kind assistance.

Hi,
To narrow down the cause, I’d like to recommend the following troubleshooting:
1. Try to login the test account through OWA.
2. Check the Autodiscover settings: get-clientaccessserver |fl autodiscoverserviceinternaluri
3. Check the result of directly accessing the following URL:
https://autodiscover.domain.com/autodiscover/autodiscover.xml
Thanks,
Angela
Angela Shi
TechNet Community Support

Can' add Exchange account to Outlook 2013

Hi,
We have an Exchange 2013 server which as far as I know is fully working - Outlook clients on the domain connect fine, OWA works fine and mobile devices work fine.
However I have a problem when trying to add an Exchange account to Outlook 2013 when this computer is on another domain (separate network, separate domain, separate company).
I assume Outlook is searching for an Exchange server which isn't there but how can I get around this?
Thanks

Hi,
Please try to alter the authentication method on the relevant CAS servers to Basic and test the issue. For details:
http://technet.microsoft.com/en-us/library/bb124503%28v=exchg.141%29.aspx
Thanks,
Rebecca Tu
TechNet Community Support

Exchange 2013 w/Outlook 2013 "The name of the security certificate is invalid or does not match the name of the site"

I've completed an upgrade from Exchange 2003 to Exchange 2013 and I have one last SSL message that I can't get rid of. I've installed a 3rd party cert that is working great for webmail and cell phone access but for some reason the Outlook 2010/2013
clients get prompted for a security warning. I just implemented the SSL cert yesterday and I've noticed that new installs of Outlook seem to work just fine. My Outlook 2013 client doesn't prompt me with the message but I have other users who are
still getting the "The name of the security certificate is invalid or does not match the name of the site" error. The domain on the cert error show up as server.mydomain.local. I've gone through all the virtual directories and pointed
all of my internal and external URL's to https://mail.mydomain.com. This made one of the two warnings go away but not the second. I've dug around on google and gone through everything I could find here and as far as I can tell my internal
and external url's are configured properly and I can't figure out where this error is originating from. Any ideas on where I should look outside of the virtual directories?
I'm including a good link I found that contains all of the virtual directories I updated. I've checked them through both CLI and GUI and everything looks good.
http://www.mustbegeek.com/configure-external-and-internal-url-in-exchange-2013/
http://jaworskiblog.com/2013/04/13/setting-internal-and-external-urls-in-exchange-2013/

Hi,
When the Outlook connect to Exchange 2013/Exchange 2010, the client would connect to Autodiscover service to retrieve Exchange service automatically from server side. This feature is not available in Exchange 2003 Outlook profile.
Generally, when mailbox is moved to Exchange 2013, the Outlook would connect to server to automatically update these information. It needs time to detect and update the changes in server side. I suggest we can do the following setting For autodiscover service:
Get-ClientAccessServer | Set-ClientAccessServer –AutodiscoverServiceInternalUri https://mail.mydomain.com/autodiscover/autodiscover.xml
Please restart IIS service by running IISReset in a Command Prompt window after all configuraions.
Regards,
Winnie Liang
TechNet Community Support

Troubleshooting for RPC over https (Outlook Anywhere) connection issue

RPC over https (ROH), well known as Outlook Anywhere, is more frequently used. Even in Exchange 2013, Outlook no longer connects CAS server via MAPI.
In this thread, we will discuss about the troubleshoot checklist about the RPC over https (Outlook Anywhere) connection issue. In order to make it more logical, I’d like to divide the whole troubleshooting to the following processes:
1. Client side to CAS side
2. CAS side to MBX side
[Issues between Client side to CAS side]
In Exchange 2013, Outlook Anywhere is enabled by default. Different from this, Outlook Anywhere in Exchange 2007 and 2010 need to be manually enabled. Thus, please firstly check if the RPC over HTTP component has been installed:
Click Start, and then click Control Panel.
Double-click Programs and Features.
In the left pane of Server Manager, click Features.
In the right pane, click Add Features.
Check if the RPC over HTTP component has been selected.
If the ROH connectivity issue only happens on certain users, the property MAPIBlockOutlookRpcHTTP can be checked:
Get-CASMailbox name | fl MAPIBlockOutlookRpcHttp
2. Confirm if Exchange server is blocked. Ping the Exchange server FQDN on client machine and confirm if it can return the proper IP address.
3. Check if the RPC Proxy server is responding correctly:
rpcping -t ncacn_http -s ExchServer -o RpcProxy=RPCProxyServer -P "user,domain,*" -I "user,domain,*" -H 2 -u 10 -a connect -F 3 -v 3 -E -R none
If 200 code returns, the test is successful.
4. Check if Outlook Anywhere host names are added in the certificate:
To get host names, the following command can be used: get-outlookanywhere |fl *hostname
5. To use the Shell to test Outlook Anywhere connectivity, use the
Test-OutlookConnectivity cmdlet.
[Issues between CAS side to Mailbox side][RZ1]
A. Check if it can connect to store’s port:
RpcPing –t ncacn_http –s ExchangeMBXServer -o RpcProxy=RpcProxyServer -P "user,domain,password" -I "user,domain,password" -H 1 –F 3 –a connect –u 10 –v 3 –e 6001
If it returns as following: Completed 1 calls in 60 ms 16 T/S or 60.000 ms/T, it means the RPC Ping Utility test succeeds.
B. Check if it can Connect to DsProxy Service:
RpcPing –t ncacn_http –s ExchangeMBXServer -o RpcProxy=RpcProxyServer -P "user,domain,password" -I "user,domain,password" -H 2 –F 2 –a connect –u 10 –v 3 –e 6004
If it returns as following: Completed 1 calls in 60 ms 16 T/S or 60.000 ms/T, it means the RPC Ping Utility test succeeds.
C. Check the following registries:
[Disable the auto update]
1).Open Regedit and navigate to:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeServiceHost\RpcHttpConfigurator\RpcHttpConfigurator
2).Set the PeriodicPollingMinutes value to 0.
[Check the RpcProxy ValidPorts]
1).On the RPC proxy server, start Registry Editor (Regedit).
2). In the console tree, locate the following registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\RpcProxy
3). In the details pane, right-click the ValidPorts subkey, and then click Modify.
4). In Edit String, in the Value data box, type the following information:
ExchangeServer :6001-6002; ExchangeServerFQDN :6001-6002; ExchangeServer :6004; ExchangeServerFQDN :6004
Note:
ExchangeServer is the NetBIOS name of your Exchange server. ExchangeServerFQDN is the fully qualified domain name (FQDN) of your Exchange server. If the FQDN that is used to access the server from the Internet differs from the internal FQDN, you must use
the internal FQDN.
[Check the 6004 port settings in registry]
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeSA\Parameters
Value name: HTTP Port
Value type: REG_DWORD
Value data: 0x1772 (Decimal 6002)
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeSA\Parameters
Value name: Rpc/HTTP NSPI Port
Value type: REG_DWORD
Value data: 0x1774 (Decimal 6004)
D. Check if the RPC ports are used by other applications instead of Exchange by using : netstat –o
Then it will return all active TCP connections and the process ID (PID) for each connection.
After that, please check the application based on the PID on the Processes tab in Windows Task Manager and confirm if it’s Exchange server.
Additionally, ExRCA is a perfect tool to test the whole connection between client side and Mailbox side:
https://testconnectivity.microsoft.com/
1. On the ExRCA website, under Microsoft Office Outlook Connectivity Tests, select Outlook connectivity, and then select Next at the bottom of the page.
2. Enter the required information on the next screen, including email address, domain and user name, and password.
3. Choose whether to use Autodiscover to detect server settings or to manually specify server settings.
4. Accept the disclaimer, enter the verification code, and then select Verify.
5. Select Perform Test.
<Resource for reference>
How does Outlook Anywhere work (and not work):
http://blogs.technet.com/b/exchange/archive/2008/06/20/3405633.aspx
How to use the RPC Ping utility to troubleshoot connectivity issues with the Exchange over the Internet feature in Outlook 2007 and in Outlook 2003:
http://support.microsoft.com/kb/831051
Test Outlook Anywhere Connectivity:
http://technet.microsoft.com/en-us/library/ee633453(v=exchg.150).aspx
[RZ1]It’s part, please re-layout
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

I've just restored the M11 to Windows XP with the disks provided and Outlook Anywhere connected without issue. As strange as it sounds, this looks to be isolated to this particular model of laptop and Windows 7.
I've used the same Enterprise copy of Windows 7 and Office on a variety of laptops and pc's and none have come across this problem. The only commonality I can see is the hardware and OS.
Aftery trying to troubleshoot this unsuccessfully with Microsoft tech support for a few hours, they eluded to the fact that this +could+ be a hardware related problem. (driver, adapter properties, etc)

Nickname caché in C# VS 2013 for Outlook 2013.

I use VS 2013 and Outlook 2013.
How can I manage Nickname caché and contacts from Outlook using C# in Unit Test Project in VS 2013 ?
About it, any step-by-step guide, or Getting Started - Quick Start that can be completed in 15-20 minutes?
I get you a good step-by-step guide sample like
http://berniecook.wordpress.com/2013/01/13/getting-started-with-git-and-visual-studio-step-by-step-guide/
I wanted to quickly cover off several assumptions before we get started: install (requisites, tools required), configure, an running quickly. Target will be an "go and ready" sample. Maybe better an real application sample.
Any final _solution_ with **full source code** sample application ? _IMHO, better samples for minimize learning curve are real applications with full source code and good patterns&practices_
www.kiquenet.com/profesional

Hello,
The
Concepts (Outlook 2013 developer reference) section in MSDN provides a lot of How To articles.
It looks like you need to automate Outlook to get access to contacts. You may find the
C# app automates Outlook (CSAutomateOutlook) sample project helpful.

"The Connection to Microsoft Exchange is unavailable" when adding second Exchange account to Outlook 2013

I have a problem that I've found to be typical, just haven't found anything that describes my exact problem.
I'm having trouble adding a second Exchange 2010 server account to Outlook 2013 in one of the computers of the domain. Outlook 2013 will complain with "The Connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete
this action".
I've Googled and found many threads with the same error... however most of those seem to be either a problem with the server, or the Global Catalog in Active Directory, or the "connection method" (I've tried all found solutions to no avail).
This is not the case, since the first account is added with absolutely no problem. It can send and receive and I can delete the outlook profile and recreate it and it'll give no problems. I have this problem only when adding a second account.
This is a fresh Windows 8.1 install with an up-to-date Outlook 2013. I have other computers in the same domain and network, with the same setup (Win 8.1 + Outlook 2013) configured with two exchange accounts with no problem.
There are no connectivity problems, I can access that same account through OWA and in other computers on the network... the Global Catalog seems to be fine (shows two active DCs, which is correct).
I've tried deleting and recreating the outlook profiles, repairing the outlook installation, even deleting all outlook files in AppData and letting it recreate them, with no success.
Any hints of what could be going on?
Before I speak, I have something important to say.

Hi Javier,
Thank you for the update.
I have tested on my lab and get following result.
Lab: Exchange 2010, CAS Array (CAS01+CAS02), MBX01, DC
Type Server Field
Check name result
Changed Server Field
CAS01.domain.com
Yes
CASArray.domain.com
CASArray.domain.com
Yes
CASArray.domain.com
DC.domain.com
Yes
CASArray.domain.com
MBX01.domain.com
No
"The Connection to Microsoft Exchange is unavailable"
Based on my knowledge, the reason why inputing DC FQDN in the Server Field fixes this issue is that Outlook performs AD Lookup and finds the account configuration from AD, then back the CAS Array FQDN in the Server Field instead of DC FQDN.
Exchange 2010 is different from Exchange 2013, if you are using Exchange 2013, we need to input MailboxServerGUID.domain.com into Server Field.
If there is anything I’ve misunderstood, please don’t hesitate to let me know.
Thanks,
Steve Fan
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Outlook Users connection issues after Mailbox Migration from 2007 to 2013

Hi,
We have a coexistance between Exchange 2007 SP3 and Exchange 2013 CU7. There is an issue when after migrating the user from exchange 2007 mailbox to exchange 2013, the outlook keeps on prompting for password when it is being launched. Checking the Connection
Status we found that there is a connection to the old 2007 Server and the type is Exchange Public Folder. I have migrated the public folder and checked the Mailbox of the user and found that the DefaultPublicFolderMailbox is set to the 2013 Public Folder Mailbox.
If I check my 2013 MailboxDatabase Properties, It sill shows that PublicFolderDatabase Properties is still pointing to the 2007 Public Folder Database. Any resolution on this?
Another issue is, We set outlook anywhere on the 2013 to use basic authentication, however, when users are migrated to 2013 the Outlook client changes to NTLM. even if we set the outlook to basic to make it work, it still comes back to NTLM after a while.
I did most of the resolutions online to use powershell to make changes to outlook anywhere but no luck. any suggestions is highly appreciated.
Thanks & Regards,
Arthur

Hi,
For the first problem, please check the msExchHomePublicMDB attribute for mailbox database in Exchange 2013, you can check this attribute in ADSIEdit.
If this attribute is pointing to Exchange 2007 public folder database, please set to blank. After that, please restart the information service.
And for the second question, I suggest we open a new case for this issue. In order to avoid confusion and keep track of troubleshooting steps, we usually troubleshoot one
issue per thread in order to find a resolution efficiently.
Thanks for your understanding.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Belinda Ma
TechNet Community Support

Upgraded to Exchange 2010 now outlook 2013 can't connect externally

Outlook 2013 used to connect to my exchange server via our TMG before upgrading to 2010. At first the clients were changed back to NTLM all the time but I fixed that and we now see basic with SSL. Now we get repeated logon.
I have used rpc connectivity analyser and it tells me that my (self issued) certificate doesn't chain properly - but the signing certificate is loaded on the client (by Enterprise CA policy) and looking at the mail server certificate in the certificate manger
reports the certificate to be good and correctly shows the chain (so is this a problem in the anyalyzer or does outlook constrcut its certificate chain using a different code library than say IE?).
Oddly Windows 8.1's mail cient works flawlessly when outlook 2013 goes into loops?
Any suggestions?
ICHC

Hi ICHC,
Just as Ed said, we should create new rule on TMG during the upgrading.
Found an blog for your reference:
Upgrade from Exchange 2007 to Exchange 2010 - Part II
https://www.simple-talk.com/sysadmin/exchange/upgrade-from-exchange-2007-to-exchange-2010---part-ii/
Disclaimer:
Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software of information found there. Please make sure
that you completely understand the risk before retrieving any suggestions from the above link.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Unable to configure multiple Exchange accounts in Outlook 2013

This is a complicated issue so I will try to describe it the best I can.
I have a client with two SBS servers for two different organizations in two different locations. Each server handles completely different domains. Let's call them A and B.
The issue is this...using Outlook 2010 or 2013 on clients at location B, I can configure Outlook for the users mailbox on server B just fine. Some of the users at location B also have mailboxes on server A. When I add a 2nd Exchange account for
the users mailbox on server A, things get weird.
Sometimes, when I start Outlook after adding the 2nd Exchange account, Outlook will show only one mailbox, but it is incorrect. The top level will show it is a mailbox on server B, but it contains email from server A. When this happens, email
actually transfers from one mailbox to the other. I have to close Outlook quickly before things get out of hand. About a year ago, I determined that if the user has the same username and password for their mailbox on server A and server B, this would
cause the problem. So I changed the users' username on server B and it seemed to work with Outlook 2010.
Now, a year later, we have a new user with Outlook 2013 with a mailbox on server A and server B, who works in location B. I setup Outlook 2013 with mailbox B and it's fine. I add a 2nd Exchange account for mailbox A to their Outlook Profile,
and when I launch Outlook, it shows both. BUT, the mailbox A has nothing in it, and the status shows "This folder has not yet updated. CONNECTED". Mailbox B shows "All folders up to date. Connected to Microsoft Exchange".
Also, existing email from mailbox A starts showing up in mailbox B. If I go into mail account settings, I get the "Outlook is using temporary mailbox" dialog, meaning something has moved. If I look at the two accounts, both look
to be using the same OST file, even though under data files, there are two OST files, one for each mailbox account. If I delete the 2nd Exchange account (A), Outlook works again for the single mailbox on server B.
I've tried configuring the accounts without cached mode, but that doesn't work either. Mailbox B had a delegate account (Full access permissions) to another account on server B, but I have tried removing that also, but no change.
I cannot figure out why I cannot have two Exchange accounts, one from each server (A and B) in Outlook 2013/2010 at the same time.
HELP!
Thank for any ideas. I hope I haven't made this too confusing. One last thing...when I add the 2nd Exchange mailbox, I authenticate with the username on server A with domain\username and their password. The authentication seems to be accepted
fine and without error. I have also tried configuring the 2nd account using "automatic" instead of configuring manually. Same problem.

OK, I have done some more testing as you suggested. I created yet another new profile with just mailbox A. When I start Outlook, I see the users mailbox, plus a mailbox that the user has been given Full Permissions to (a delegate?). There
is one more mailbox that this user has full permissions to, but it did not auto-add itself, so I added the mailbox through the account properties. Now, all three mailboxes at location A are in Outlook (users mailbox and 2 delegate mailboxes). In
Outlook, on the left, has at the top the users main mailbox, and then below it are two other "branches" for the delegate mailboxes. I did NOT use cached exchange mode, btw.
I quit Outlook and edited the profile, adding another exchange account for the users mailbox at location B. I did a "check-name" and authenticated OK.
I launched Outlook, and the same (wrong) thing happens. On the left pane of Outlook, at the top, it shows it is the users mailbox at location B (the main branch says Mailbox name -- location B), but all the folders and content are from mailbox at location
A. Outlook has mixed it up, and it is at this point that email starts moving between mailboxes, so I quit Outlook quickly. It did show the two delegate mailboxes from location A, but there were just three "branches", and nowhere is there
the real mailbox B.
Can it have anything to do with the fact that these accounts have delegates (or are given full manage permissions to other mailboxes on the server)??
UPDATE: I just determined something. When looking at the Outlook email accounts dialog, for each account it shows the default delivery location. For the first account (location A), it shows:
"Selected account delivers new messages to the following location: usersemail@locationA\Inbox".
When I add the users mailbox for location B, it shows:
"Selected account delivers new messages to the following location: usersemail@locationB\Inbox".
However, when I start Outlook, and see that things are wrong and quit, I go back into the accounts dialog, and BOTH accounts are set to deliver to the SAME location:
"Selected account delivers new messages to the following location: usersemail@locationA\Inbox".
So now, the 2nd exchange account has changed it's location to deliver to mailbox A instead of B.
Crazy stuff.

Auto-Mapping with Full Access Mailboxes-not working in exchange 2010 clients outlook 2013

hello, I have exchange server 2010, the clients are running outlook 2013, I set an mailbox for automapping (full access) but when i restart client it does not appear in the client. i also did the command in the exchange shell, no errors. how can i fix this.

no sp info shows with the
Get-ExchangeServer | Format-List Name, Edition, AdminDisplayVersionName
Edition : Enterprise
AdminDisplayVersion : Version 14.0 (Build 639.21)
chart says
Exchange Server 2010 November 9, 200914.00.0639.021
is that the issue need sp 1?

Sent emails, from replies, to email in Shared Exchange mailbox folders - Outlook 2013 - Office 365 Midsize Business

1. Outlook 2013 lets replies to emails from another folder than inbox wind up in that same folder.
Options - email - save - a checkbox
2. A registry setting lets email sent from shared exchange mailboxes wind up in the "sent objects" folder of that mailbox.
http://social.technet.microsoft.com/Forums/en-US/57f9f9dc-cc00-4910-a09e-1ea201dbf05c/action?threadDisplayName=office-365-outlook-2010-quotdefault-email-reply-or-fromquot-address
I need feature 1. to show up in the shared mailbox as well as the default mailbox. All my problems would be solved if I could have this behaviour in the inbox folder of the shared mailbox as well.
UniSent helped us with this on SBS2003 and Outlook 2003- 2007 but does the same trick as the registry setting in Office 2013.
cheers

Hi,
There is no build-in setting in Outlook to achieve this, you may try a code solution here:
http://social.technet.microsoft.com/Forums/en-US/ad92302a-7e60-4114-a79a-b9759a7368c1/move-sent-mails-to-other-mailbox?forum=officeitproprevious
Since we are not the best source for coding, if you need any assistance on the code sample, you can post a question in Outlook for Developers forum:
http://social.msdn.microsoft.com/Forums/office/en-US/home?forum=outlookdev
Thank you for the understanding.
Regards,
Steve Fan
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Cannot add Second Exchange Account to Outlook 2013

Cannot add second exchange account to same profile on Outlook 2013. I went through control panel, mail and tried to add the second exchange account there but I keep getting rundll32 has stopped working error. Using Windows 8.1. Any suggestions on what
I should do?

Hi,
I have some suggestions to troubleshoot this problem.
Run Windows on Clean Boot mode. Here is the link.
http://support.microsoft.com/kb/929135
Reinstall Office
Following are the steps for configuring multiple-account in Outlook.
Click File in Outlook then click Account Settings.
Choose E-mail Accounts.
Click New and input your Second Exchange Account information, then click
Next.
If the issue persists, please post your issue in Outlook forum. Here is the link.
http://social.technet.microsoft.com/Forums/office/en-US/home?forum=outlook
Thanks.

Certificate errors with Exchange 2013 and Outlook 2013

Hello, I wonder if someone could help.
I've recently set up a network with one Windows 2012 domain controller and one windows 2012 server running Exchange 2013.
Clients run Outlook 2013 and are all one the same Lan. Outlook's setup wizard finds the exchange server automatically and sets up the profile. However if I choose the manual setup and enter the server
name and user name it does not find the server.
When I check the server name in Outlook it shows as
[email protected] rather than the real name of the server: AYCEX01.AYC.local.
When Outlook is opened there is a certificate error saying "The name on the security certificate is invalid or does not match the name of the site." and another error saying "There is
a problem with the server's security certificate. The name on the security certificate is invalid or does not match the name of the target site mail.ardfernyacht.co.uk. Outlook is unable to connect to the proxy server. (Error code 10)
The external address by which users connect to OWA and active sych is mail.ardfernyacht.co.uk. The
certificate which is used is one automatically generated by Exchange.
Any suggestions you may have would be appreciated.
Many thanks,
Ruaridh
Ruaridh Mackintosh

Self sign cert wont work With autodiscover.For that you need 3rd part or from Your own CA.
Please follow this guide to install CA in Your domain:
http://careexchange.in/how-to-install-certificate-authority-on-windows-server-2012/
Please follow this guide to request New cert in Exchange 2013:
http://exchangeserverpro.com/create-ssl-certificate-request-exchange-2013/
Your cert must contain external hostname of Your mail.domain.com
Also configure Your Virtual directories to contain internal and external hostname:
http://blogs.msdn.com/b/mvpawardprogram/archive/2013/03/18/virtual-directories-exchange-2013.aspx
Regarding servername when using autodiscover,it should automatically resolve mailbox guid instead of servername.
Please check if Your DNS is setup With autodiscover.domain.local (which is pointed to Your Exchange server)
Hope this helps!
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

Exchange 2013 with Outlook 2013 - Not getting pop-up or mail tips for attachments exceeding max size

Our environment is Exchange Server 2013 CU3 and Outlook 2013 in cached mode. We have a transport rule that sets the max attachment size to 20 mb.
If someone sends an attachment larger than 20 mb they receive an NDR letting them know the message wasn't delivered because it exceeded the max attachment size. We would like for the user to be prevented from sending the message at all or to at least
get a mail tip before they try to send the message. The Outlook pop-up message that says "The file you're attaching is bigger than the server allows. Try putting the file in a shared location ..." isn't being generated for us. Not sure if that's
because we're running Exchange or not. If that pop-up isn't going to work it would be nice if the user could at least get a mail-tip warning them that the attachment exceeds the limit. But it doesn't look likes there's a mail-tip for attachment size, only
for message size. And, I've found that the message size mail-tip only works if the limit is set on the user. It doesn't seem to work if the limit is set via a transport rule.
Has anyone else gotten Outlook to present the pop-up or a mail-tip when exceeding attachment size? Any help you can offer would be greatly appreciated.

Thanks but I performed all of those trouble shooting prior to posting to the forum. But, I have found the answer!
After referring to this article;
http://technet.microsoft.com/en-us/library/bb124345(v=exchg.150).aspx
I removed the 10mb default limits from the organization config and chose to set the attachment and message size limits in our environment via transport
rules instead. That is the only way you can actually set an attachment size limit.
I had read this article several times searching for an answer;
http://support.microsoft.com/kb/2813269#appliesto
The key is here;
"If you are using an Exchange Server account, the 20-MB attachment
limit for Internet email accounts is not used by Outlook 2013. Instead, Outlook uses the limit that is configured on your Exchange server. To modify the setting that is used to control the size of a message that is sent through an
Exchange Server account, follow these steps."
The steps that follow are for Exchange 2010 but they show setting organization limits not server limits. And note that it
says the size of a message, not the size of an attachment. Since mail-tips for message size are not displayed when the limit is set via the transport rules I thought it
was possible that the same inconsistency might apply to the attachment pop-up warning. I set the organization limits and voila! The pop-up now displays when an attachment that exceeds the message size limit is added to a message.
This is exactly what I wanted. Now users won't fill up their sent items trying to send large attachments that just bounce anyway.
It would be wonderful if Microsoft would provide information about what features of Outlook are affected when you apply message size limits at the
various levels.

Exchange 2013-SP1/Outlook 2013 connectivity issue.

Similar Messages

Maybe you are looking for