Exchange 2013 - outlook cannot connect server

Hi,
I have installed exchange server 2013 to testing it in my home lab. DC - domain.local and exchange - sub.domain.com. Internet connection is with dynamic IP from ISP - router (PPPoE). My ISP provide DDNS and I got sub.domain.com for dynamic
IP. Also ISP is blocking port 25. I've asked ISP to unblock port 25 and i don't know if they unblock it. For exchange server i use smart host for relay.
Problem: If i use port forwarding (25) mail flow is normal intern - extern. This was tested with OWA, but outlook cannot connect to exchange server: logging on mail server failed.
If i don't use port forwarding (25) outlook connect to exchange server, but i cannot receive email from external.
Please give me a hand on this.
Thank you.

Hi Radu,
how do you connect Outlook with Exchange? Usually you're using MAPI/RPC/HTTPS so there is no dependency with SMTP. How did you configure your Outlook? How did you configure your CAS Settings?
Please verify your CAS is configured correctly and you are using Outlook AnyWhere, see
http://technet.microsoft.com/en-us/library/hh529912(v=exchg.150).aspx
Regards,
Martin

Similar Messages

Exchange 2013 Outlook Anywhere connection issues when using F5 VIP

Hello,
We are in the process of deploying Exchange 2013 into our Exchange 2010 Org. We are using an F5 to load balance all services. We are doing some initial testing and have not cut over autodiscover or other URLs yet to 2013. We are using host files
on the local testing machines to point the URLs to 2013. OWA, Activesync, ecp work with no issue through the F5 VIP. However, we are having issues with Outlook. If our host file entries point to a single server, Outlook functions
normally. If the host file entries point to the F5 VIP, it keeps prompting for creds and will never connect.
Just wondering if anybody has run into this or has any guidance as far as OA and F5 deployment.
Thanks

Hi,
Please check your Load Balance configuration and make sure the namespace used for Load Balance has been included in the Exchange certificate. For example: mail.domain.com and autodiscover.domain.com.
If possible, please share your load balance configuration with us for further analysis. Here are some references about the Load Balance Scenario:
http://blogs.technet.com/b/exchange/archive/2014/03/05/load-balancing-in-exchange-2013.aspx
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 Outlook Client connectivity

I'm migrating from Exchange 2010 to Exchange 2013 and on the final stages. I pointed the external and internal DNS records to Exchange 2013. I moved one mailbox to Exchange 2013 and then tried to create a new Outlook client profile and bring the mailbox
up however the client would not connect. It stated trying to connect encrypted and unencrypted. It did not work. I checked nslookup and the IPs are all set pointing to Exchange 2013. I then checked my certificates. I have a certificate that is a wild card.
When I checked assigned services on my wild card it had IIS and SMTP assigned. Also in IIS on the default site bindings what should you use as a certificate on the two https settings? Originally they were the local generated certificate. I changed them to
the wild card no luck. Please assist.

Try running through this and see if it gives you some ideas on what is wrong:
https://testconnectivity.microsoft.com/
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

Exchange 2013, Outlook 2007 clients Problems with Outlook Anywhere connection

Hi everyone,
I have a mail system Exchange 2013 SP1, on Windows Server 2012 R2.
I have only one mail server with the Client Access and Mailbox roles Server.
I have a Wildcard certificate type *. Mydomain.com.
All connections to the Outlook Anywhere Outlook 2010, Outook 2013 work correctly.
The ActiveSync connections are working properly, too.
But Outlook 2007 clients connecting with Outlook Anywhere asking for credentials continuously fail continuously.
How can I solve this?
thank you very much
Microsoft Certified IT Professional Server Administrator

Hi,
Based on my experience, we need to set Outlook provider with the domain name if it's wildcard certificate:
Set-OutlookProvider -Identity EXPR -CertPrincipalName msstd:*.domain.com
http://technet.microsoft.com/en-us/library/cc535023(EXCHG.80).aspx
Thus, I recommend you try the above configuration and test the Outlook connection again.
Thanks,
Angela Shi
TechNet Community Support

Exchange 2013 - Outlook 2010 - 550 5.1.0 RESOLVER.ADR.InvalidInSmtp; encapsulated INVALID address inside an SMTP address

Hello,
I have issue when sending email to some addresses. Server respond with:
Remote Server returned '550 5.1.0 RESOLVER.ADR.InvalidInSmtp; encapsulated INVALID address inside an SMTP address (IMCEAINVALID-)'
My enviroment: Exchange 2013, Outlook 2010 - no cached mode. Issue happend with two email addresses but not always.
Any suggestion, how to resolve issue?
Thx.

Hi Tomas,
Does this issue occur in OWA? How is the impact, only one user or all users?
Please try to run Outlook under safe mode to avoid add-ins and AVs.
If there is any 3rd party add-ins, please try to disable them for testing.
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Mavis Huang
TechNet Community Support

Error During install Exchange 2013 through Powershell on Server 2012 "Mailbox role: Client Access service"

Dear all
During install Exchange 2013 through Powershell on Server 2012 I got this error in Mailbox role: Client Access service :
The following error was generated when "$error.Clear();
$BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";
new-OwaVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController
set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
" was run: "An error occurred while creating the IIS virtual directory 'IIS://MONAMBX2.mona.local/W3SVC/2/ROOT/o
wa' on 'MONAMBX2'.".
The following error was generated when "$error.Clear();
$BEVdirIdentity = $RoleNetBIOSName + "\OWA (Exchange Back End)";
new-OwaVirtualDirectory -Role Mailbox -WebSiteName "Exchange Back End" -DomainController $RoleDomainController
set-OwaVirtualdirectory -Identity $BEVdirIdentity -FormsAuthentication:$false -WindowsAuthentication:$true;
" was run: "The operation couldn't be performed because object 'MONAMBX2\OWA (Exchange Back End)' couldn't be fo
und on 'MonaDc1.mona.local'.".
Any advice please !!

I can't answer your question but I had a similar issue when I was trying to move our mailbox database off the C: drive. Our environment still has an Exchange 2007 server in it and when I was trying to move the database on the 2013 server, I would get
error messages saying the database does not exist. It seemed like it was trying to move the database on the 2007 server from the similar error messages that I was getting. To get around it, I deleted the database and created a new one on the drive
where we wanted it.
I discovered this when I was configuring the Antispam settings. I deleted our 2007 settings, added them to the 2013 shell, the settings appeared on our 2007 server. The shell on 2013 was making changes to 2007.
I'm not sure if there is a "Get|Set or New" command that I/we should be using when this happens. Or maybe my issues will be fixed if I just remove the Exchange 2007 server? I'm not ready to do that yet because I can't configure the spam filtering
on 2013 yet with its shell not being able to make the changes that we need.
I don't know if your environment is in coexistence mode like mine.
Hopefully someone else out there has an answer or can tell us when/how the shell can make the appropriate changes to the 2013 server. Does this happen after the 2007 server is removed?

Exchange active sync cannot connect to server after migration mailbox user from exchange 2007 to exchange 2013 coexistence

Hello, everyone, my name is rafl
I have a problem with exchange 2013 active sync.
I have installed exchange 2013 coexistence with legacy exchange 2007, I have to migrate user mailboxes: [email protected] from exchange 2007 to exchange 2013.
but any problem with active sync connection on the mobile device after moving mailbox user. I reconfigure the exchange ActiveSync external connection domain (latest.domain.com) on mobile device replacing legacy exchange ActiveSync external connection domain
(legacy.domain.com)
the process of moving mailboxes successfully without error.
Access OWA for exchange 2007 and exchange 2013 is running normally
access mail from Outlook running normally
Certificate request has been installed and has no problem with it
The OWA virtual directory is configured for internal and external connections and different from the legacy exchange
The autodiscover virtual directory is configured for internal and external connections and different from the legacy exchange
ActiveSync virtual directory is configured for internal and external connections and different from the legacy exchange
user mailboxes are still on exchange 2007 is not problematic.
only problem with Exchange Active Sync on mobile devices, where I set up an email with android, iphone, windows phone. the error message: cannot connect to the server.
but, if I create a new user and create user mailboxes directly in exchange server 2013, ActiveSync can run without error on mobile device, access through OWA, MsOutlook, Outlook Anywhere also run normally.
only the results of user migration from exchange 2007 to exchange 2013 which is troubled with exchange ActiveSync connection.
any ideas for this problem, and what should I check on the exchange server ..?

i have run the activesync test connectivity and get some error :
Testing TCP port 443 on host domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 3091 ms.
Testing TCP port 443 on host autodiscover.domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 21072 ms.
Testing TCP port 80 on host autodiscover.domain.co.id to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
A network error occurred while communicating with the remote host.
Elapsed Time: 21049 ms.
I have allowed access to port 443 (https) and 80 (http) on the firewall and re-run testconnectivity, but still with the same results. if I enable active sync for users who created directly in Exch 2013 there is no problem with the ActiveSync, just a problem
for users who moved from Exch 2007 to Exch 2013. @Android, iPhone, and Blackberry the error message "cannot connect to the server"

Outlook cannot connect after mailbox move from Exchange 2007 to 2013

I am in the middle of migrating an Exchange Server 2007 to 2013. Everything went fine up until I moved the first mailbox. I can access the mailbox via OWA, but not Outlook 2010. When I checked the account settings, the server is incorrect. It shows [email protected]
If I manually enter the name of the Exchange 2007 server, it changes to the Exchange 2013 server, as it should. I save the settings, open Outlook, the connection fails, and the server setting is changed to [email protected]
I then ran the Microsoft Connectivity Analyzer. There are 2 lines which caught my attention:
AutoDiscoverInternalRpcClientServer
[email protected]
AutoDiscoverHomeMdbDn
/o=mydomainMail/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/cn=Configuration/cn=Servers/cn=[email protected]/cn=Microsoft Private MDB
I've checked and rechecked everything and can't seem to locate my error.
Any thoughts? Thanks.

Totally correct!
If you don't plan to maintain Outlook then you plan to fail :(
Additional links etc are in here:
http://blogs.technet.com/b/rmilne/archive/2013/07/18/patching-exchange-don-t-overlook-outlook.aspx
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

Exchange 2010 - Exchange 2013 Outlook 2010 resolves wrong server

Hello,
We are upgrading from exchange 2010 to 2013.
Now I have migrated a testmailbox, but when I try to configure it in outlook it tries to connect to the Exchange 2010 server instead of the Exchange 2013 server.
I have configured outlook manually like described on the following url:
http://www.zerohoursleep.com/2013/02/manual-outlook-configuration-with-exchange-2013/
At the "Check Name" step, it will not resolve the Exchange 2013 server guid but the Exchange 2010 server... but the mailbox is migrated to Exchange 2013...
When I try to launch outlook an error occurs: Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize your folders with your Outlook data
file (.ost)."
Can someone help me out please?
Thx!

Are you sure the mailbox move completed? What happens when you log into OWA? Are you having AD replication issues in your environment?
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

Exchange 2013 - Outlook 2007 - Server name GUID

Hi Guys.
I am hoping someone can shine some light on something for me.
Right now I have the following with roles.
1 x Exchange 2010 - MBX & CAS
1x Exchange 2013 - MBX
1 x Exchange 2013 - CAS
Mix of Outlook 2007 & 2010
I migrated a user from Exchange 2010 over to Exchange 2013 and the process went fine. Email flow is working, OWA and Active Sync again working ok.
However when we opened Outlook 2007 it displayed a message to say an Administrator had made changes and we needed to restart Outlook. No issues there.
Outlook connected up fine and everything works. However when you look in the mail profile for the Exchange server name i see something like
[email protected]
Also Outlook Anywhere is ticked and when you untick it from the client and then open it again it comes back.
Are the above items of migration?

Hi,
RPC is no longer a supported direct access protocol. This means that all Outlook connectivity must take place using RPC over HTTP (also known as Outlook Anywhere).
Outlook clients no longer connect to a server FQDN as they have done in all previous versions of Exchange. Outlook uses Autodiscover to create a new connection point comprised of mailbox GUID, @ symbol, and the domain portion of the user’s primary SMTP
address.
To expand on this a little bit, I worked an issue with a new Exchange 2013 environment for 3 days before figuring out that you do NOT specify a server name where it asks for it in Outlook, you use the format mentioned above.
For reference, I received a very particular error from testconnectivity.microsoft.com that made no sense until I discovered the server name format. If a test fails with a 404 HTTP Not Found error and an X-CasErrorCode of MailboxGuidWithDomainNotFound,
this is most likely your problem. Its very frustrating that Microsoft does not have it documented anywhere exactly what this error means, would have saved me a lot of time and energy.

Exchange 2013 outlook server name is my owa URL not hash

i was migrating from exchange 2003 to 2010 to 2013.
after the migration and i install the exchange 2013 with exchange 2010 and configured it. the outlook not working with users that migrated to exchange 2013, and working well with the users already existing on exchange 2010.
when i try to fix this issue i set my outlook provider using this commend Set-OutlookProvider EXPR -CertPrincipalName
"msstd:mail.mydomain.com"
but unfortunately it's impacted the server name in client outlook.
then i removed the outlook provider and create it again. but with no change. then i uninstall the CAS server and install it again but with now change too.
now the outlook server name is my URL "mail.mydomain.com" and i need to recover it to be hash like "[email protected]"
the outlook client version outlook 2010 sp2 & and outlook 2013

Hi,
Is there any error when you connect your Exchange 2013 mailbox in Outlook? Also confirm if the problematic users can access Exchange 2013 mailbox from OWA.
Generally, Outlook uses Autodiscover service to auto setup Exchange account in Outlook. We can check the Autodiscover service in Exchange 2013 (mail.mydomain.com is pointed to Exchange 2013):
Get-ClientAccessServer | FL Identity,fqdn,*autodiscover*
Set-OutlookAnywhere -Identity "Exch13\Rpc (Default Web Site)" -InternalHostname mail.mydomain.com -ExternalHostname mail.mydomain.com -InternalClientAuthenticationMethod Ntlm -ExternalClientAuthenticationMethod Basic -ExternalClientsRequireSsl
$True -InternalClientsRequireSsl $true
Also make sure the name which is used in the AutoDiscoverServiceInternalUri has been included in your Exchange certificate with
IIS service. We can restart IIS service by running IISReset /noforce from a Command Prompt window.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 user cannot mail 2010 user

Hello All, I am migrating from 2010 to 2013. The Exchange Server Deployment Assistant is proving very helpful thus far. I created a mailbox in 2013 and attempted to email a 2010 user. No luck - the email gets stuck in the queue "Last Error: 400 4.4.7
Message delayed". I can see that it is attempting to send the email to the correct database in 2010 but that is the extent of my troubleshooting knowledge.
I have yet to complete the step "Enable and Configure Outlook Anywhere" which states: "To allow your Exchange 2013 Client Access server to proxy connections to your Exchange 2010 servers, you must enable and configure Outlook Anywhere
on all of the Exchange 2010 servers in your organization." - I haven't yet done this because I didn't want anything destructive to happen to the current 2010 server, but perhaps to enable a 2013 user to send to a 2010 user this step needs to be completed
- thoughts? Btw, 2010 can successfully email a 2013 user. Is it a particular receive connector that I need to modify?
Cheers, db.

Hi Dennis,
if you go to your Ex 2010 Server, please install Telnet-Client ; you can do this from Powershell using "install-windows-Feature telnet-client".
1. run a Powershell or CMD
2. telnet exchange2013server 25
Does it connect using the Exchange 2013 CAS / Transport Server Name?
If no, please check
1. is there any anti Virus / Firewall Software blocking the Connection?
2. is there any Firewall on the Network blocking the SMTP Connection?
3. does your receive connector include the subnet of your Exchange 2013 CAS server?
If you cannot connect verify please the remote IP range includes your new servers , check it running
Get-ReceiveConnector | fl name,binding,remoteipranges
from Powershell. If required, use set-receiveconnector to Change it.
http://technet.microsoft.com/de-de/library/bb125140(v=exchg.150).aspx
Regards,
Martin

Exchange 2013 Users cannot access Public folder in Exchange 2007 SP3

Dears,
i am working in Upgrading Exchange 2007 to Exchange 2013 CU7,, I came to know with CU7 we have new way for coexistence with legacy Public Folder
https://technet.microsoft.com/en-us/library/dn690134(v=exchg.150).aspx
i did the steps exactly as it is in the article, but now users in Exchange 2013 always prompt for username /password when opening outlook and i found they still trying to connect to Exchange 2007 PF Server using HTTPS and failed..
BTW, Outlook anywhere is disabled in EX2007 and as per this article Q/A , it is no more needed
http://blogs.technet.com/b/exchange/archive/2014/11/07/on-premises-legacy-public-folder-coexistence-for-exchange-2013-cumulative-update-7-and-beyond.aspx
the issue now, still users getting prompted and cannot connect to PF in EX2007,,
your help is appreciated
thanks
Mufleh

I ran into the same situation recently, and found out that you need to make sure InternalClientsRequireSSL is set to false.
To verify: Run Get-OutlookAnywhere | fl Identity, *ssl
If it is true, try setting it to false.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread

Move Exchange 2013 to new Virtual Server including settings?

Since we have a failing VM Exchange 2013, we need to move the installation to a new server. We have created a new Hyper-V Server 2012 and installed a new Exchange 2013 on it. After connecting the new server to the domain we can see all settings and users
of the existing Exchange Installation.
Since the old server has a corrupt RAID, we need to move all data and settings to the new server. We have moved some user mailboxes with the ecp to the new server. They are still working, but mailtraffic takes exactly 1 hour now?! Also these users who logon
with Outlook now get the error message 'problem with the safetycertificate of the proxyserver (translated)'. The mail still works, but 1 hour delay.
Can we now move the other mailboxes too? And if we have moved them, how can we move the settings of this server? If we shutdown the old server, will Exchange (the moved one) still be up and running? Because we are afraid that when we shutdown the old server
it will not boot again.
Thanx for any tips of leads in the right direction.

1. Outgoing mail from https://echange/owa is
working.
Did you try https://ip-address-of-newserver/owa and send an email outside?
2. Outlook 2010 does not start, cannot find mailboxes to open, so user won't have mail in the morning.
Get-OutlookProvider -Identity EXCH | FL
If is field CertPrincipalName empty type following:
Set-OutlookProvider EXCH -CertPrincipalName msstd:FQDN-YOUR-MAIL-SERVER
After this it should work (assuming all your mailboxes moved to the new server).
Please check this to see you the mailbox servername
http://www.zerohoursleep.com/2013/02/manual-outlook-configuration-with-exchange-2013/
3. Incoming mail cannot be delivered by the Barracuda (connection refused).
Ensure Barracuda is sending email to the new server and new server is not blocking incoming traffic.
4. OWA and ECP not working from outside (public IP).
Ensure you NAT is correct by site. Check it is listening to the port using http://www.canyouseeme.org/
Please check these and get back
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Exchange 2013 + Outlook 2010, Security Alert

A small customer has Outlook 2010 connecting to Exchange Server 2013 on a Windows 2008
R2 server at a remote site. Recently, the users began receiving a security
alert ("The identity of this web site or the integrity of this connection
cannot be verified", "The name on the security certificate is invalid
or does not match the name of the site"). This occurs every time a user
opens Outlook, and when they click on "Yes" they are able to use
Outlook normally. <o:p></o:p>
This problem began not long after 1) the wildcard ssl certificate was renewed and 2)
Exchange 2013 was updated to the most recent SP and CU. It is noteworthy that
the PCs being used are not members of the domain. The users also receive this
error if they use Outlook to connect from their home PCs. <o:p></o:p>
The Exchange server passes connectivity and autodiscover tests. I have checked all the URLs
in Exchange Server. I have tried changing authentication, re-enabling the the
*.domain.ca certificate, I have not been able to reproduce the error on my own
laptop from the customer's site. <o:p></o:p>
This problem is not critical, but it is annoying for the users, and I have tried
just about everything I can find on the Internet to resolve it. <o:p></o:p>
Any suggestions? <o:p></o:p>

Hi,
Please run the following command to set the CertPrincipalName parameter which specifies the Secure Sockets Layer (SSL) certificate principal name required for connecting to Exchange from an external location to have a try:
Set-OutlookProvider EXPR -CertPrincipalName msstd:*.domain.ca
If the issue persists, please follow the steps below to check Exchange services for the problematic users :
Open Outlook - press CTRL key - right click on the Outlook icon from right bottom corner taskbar -
Test Email AutoConfiguration. Put your email address - uncheck use guessmart and secure guessmart authentication - click Test to check your Autodiscover service.
Please collect the information in the Log tab and Results tab.
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 - outlook cannot connect server

Similar Messages

Maybe you are looking for