Outlook does not connect to Exchange 2013 after name change due to marriage

When launching Outlook and clicking through the setup wizard to create a new profile, Outlook auto-discovers the correct email alias. When establishing a connection it successfully checks network connectivity and successfully searches the email settings.
When it attempts to logon to the mail server the error comes up.
"The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
Clicking "Check Name" gives the error:
"The name cannot be resolved. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
The same result occurs with a manual setup.
We are running Exchange Server 2013. User workstations are running Outlook 2013 on Windows 7 Pro. All updates have been applied as of March 31, 2015.
All name changes have been made in AD and Exchange. Old aliases and new aliases are set in Exchange. Offline Address books are updated daily. The local profile and registry settings have been updated on the workstation and the user is successfully logging
into the profile. The issue is only with Outlook 2013. User can access mail through OWA and ActiveSync on their mobile device.
Logging the user into another workstation and running the wizard returns the same results, which rules out the possible problem being with the workstation.

Hi,
According to your description, I understand that failed auto-configure Outlook with error “The name cannot be resolved. The connection to Microsoft Exchange is unavailable…”, however OWA works fine.
If I misunderstand your concern, please do not hesitate to let me know.
Are all account or any special user experience this question?
If OWA works fine, it indicate that the mailbox database is mounted, and mailbox works well.
I notice that you have changed the account name before issue arise, because external access, the client locates the Autodiscover service on the Internet by using the primary SMTP domain address from the user's email address.
More details about Autodiscover service, for your reference:
https://technet.microsoft.com/en-us/library/bb124251.aspx?f=255&MSPPError=-2147217396
Please try below command to force update address list, GAL, OAB, then test again:
Get-AddressList | update-AddressList
Get-GlobalAddressList | update-GlobalAdressList
Get-OfflineAddressBook | Update-OfflineAddressBook
If the issue persists, please wait for some time to complete configuration.
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]
Allen Wang
TechNet Community Support

Similar Messages

OUtlook 2013 can not connect to exchange 2013 after exchange maibox member of DAG failed.

hi ALL
OUtlook 2013 can not connect to exchange 2013 after exchange maibox member of DAG failed.
Exchange environment contains 2 Exchange Mailboxesserver ,( one Failed , virtual Machine)
2 cas Servers
first databases could not be mounted but after we run the below command , users can use OWA but outlook could not connect
Start-DatabaseAvailabilityGroup -Identity DAG -MailboxServer MBX1
please support
thanks

Hi,
According to your description, I understand that Outlook client cannot connect to Exchange server 2013 while one member of DAG failed.
If I have misunderstand your concern, please do not hesitate to let me know.
I want to double confirm whether all account store in MBX1 experience this issue, users in MBX2 works fine.
Please run following command to double check the database status:
Get-MailboxDatabase –Status | select Name,Mounted,MountedOnServer
If it works in OWA, the issue may be related to Outlook side. Please run “Test E-mail AutoConfiguration” and “Outlook Connection Status” to get more details, expecial the setting of proxy server, it’s more helpful
for further troubleshooting.
Additional, please try to recreate a profile for testing. Besides, please move active DB back to MBX1.
Best Regards,
Allen Wang

Outlook can't connect with Exchange 2013 after migration from Exchange 2007

<style type="text/css">P { margin-bottom: 0.21cm; }</style>
Hello,
recently we've done a Exchange 2007 sp3 to 2013 sp1. Users can conect perfectly with OWA and with his iphone clients.
But the problem is they can't connect from his Outlook clients (2010, 2013), both internaly and externaly. Always fails with the message: The Connection to Exchange it is not avaliable.... Can't resolve the name of Exchange server.
To try to resolve it we've done:
- Check Outlook anywhere configuration en EAC: it is configure with and external url mail.company.com and internal server.domain.local. The security is the default Negociation, but we've tried all.
- Check the internal dns, there are records for mail.company.com and exchangeserverdomain.local pointing to the exchange local ip. Also there is a public zone company.com with the record mail.caompany.com pointing to the exchange local ip. Also we've made
records autodiscover.company.com and autodiscover.domain.local pointing to the exchange local ip.
- In the public dns from our domain there is the record A and MX pointing our public ip. There aren't any record Autodiscover but we think that the manial conection should work.
Check certificates: we've made a new self-signed certificate including all this internal and external domains and for all services.
- Check Outlook Anywhere block: we've cheked.
Currently server state:
- Old Exchange 07 server can't start, it was in very bad state and we achieved migrate the mailbox to the new server, after that we tried to uninstall, but it crashes with a public folder replication error. We got uninstall all the roles
unless the mailbox. After a restart it can't start.
-The new Exchange 2013 looks great, there isn't any trail of the old server, or we haven't seen anything in the EAC or shell.
I paste below the result of Microsoft Remote conectivity analaizer, with Outlook anywhere test. It is clear that there is a problem with that.
Sorry because the test is in spanish and I translated it with google, from here I only can access the tool in spanish.
We continue to try to resolve the problem.
Thanks to all in advance!
Testing RPC / HTTP connectivity.
Error in testing RPC / HTTP.
additional Details
Elapsed time: 24295 ms.
Test steps
Connectivity Analyzer Microsoft is trying to test Autodiscover for [email protected] .
Error in automatic detection test .
additional Details
Elapsed time: 24294 ms.
Test steps
Attempting each method of contacting the Autodiscover service .
Failed to properly contact the Autodiscover service using all methods.
additional Details
Elapsed time: 24294 ms.
Test steps
Trying to prove possible Autodiscover URL https://empresa.com/AutoDiscover/AutoDiscover.xml
Error in testing this potential Autodiscover URL .
additional Details
Elapsed time: 1509 ms.
Test steps
Attempting to resolve the host name in DNS empresa.com .
The host name is resolved correctly .
additional Details
IP addresses returned : 80.36.252.194
Elapsed time: 507 ms.
Testing TCP port 443 on the host to ensure empresa.com listening or is open.
The port was opened successfully.
additional Details
Elapsed time: 464 ms.
Testing the SSL certificate to make sure it is valid.
The SSL certificate is not exceeded one or more certificate validation checks .
additional Details
Elapsed time: 537 ms.
Test steps
Connectivity Analyzer Microsoft is attempting to obtain the SSL certificate from remote server on port 443 empresa.com .
Connectivity Analyzer Microsoft successfully obtained the remote SSL certificate.
additional Details
Remote Certificate Subject : CN = mail.empresa.com , issuer : CN = mail.empresa.com .
Elapsed time: 454 ms.
Validating the certificate name .
The certificate name was validated successfully .
additional Details
Hostname empresa.com was found at the entrance of the alternative subject name of the certificate.
Elapsed time: 1 ms.
Is validating the trusted certificate .
Validation Error trusted certificate.
Test steps
Connectivity Analyzer Microsoft is trying to build certificate chains for certificate CN = mail.empresa.com .
Could not build a certificate chain for the certificate.
Tell me more about this issue and how to resolve
additional Details
The certificate chain did not end in a trusted root . Root = CN = mail.empresa.com
Elapsed time: 31 ms.
Trying to prove possible Autodiscover URL https://autodiscover.empresa.com/AutoDiscover/AutoDiscover.xml
Error in testing this potential Autodiscover URL .
additional Details
Elapsed time: 21723 ms.
Test steps
Attempting to resolve the host name in DNS autodiscover.empresa.com .
The host name is resolved correctly .
additional Details
IP addresses returned : 46.16.56.40
Elapsed time: 498 ms.
Testing TCP port 443 on the host to ensure autodiscover.empresa.com listening or is open.
The specified port is blocked , not listening or does not generate the expected response .
Tell me more about this issue and how to resolve
additional Details
Network Error communicating with the remote host.
Elapsed time: 21224 ms.
Attempting to contact the Autodiscover service with the HTTP redirect method .
Error when trying to contact the Autodiscover HTTP redirect method .
additional Details
Elapsed time: 606 ms.
Test steps
Attempting to resolve the host name in DNS autodiscover.empresa.com .
The host name is resolved correctly .
additional Details
IP addresses returned : 46.16.56.40
Elapsed time: 14 ms .
Testing TCP port 80 on the host to ensure autodiscover.empresa.com listening or is open.
The port was opened successfully.
additional Details
Elapsed time: 202 ms.
Connectivity Analyzer Microsoft is checking the automatic detection of host empresa.com for an HTTP redirect to the Autodiscover service.
Connectivity Analyzer Microsoft could not get a HTTP redirect response for Autodiscover .
additional Details
Web exception occurred because an HTTP 404 response was received - Unknown NotFound . Headers received: Connection : close Content- Length: 1209 Content- Type: text / html Date: Wed, 12 Mar 2014 15:27:58 GMT Server : Apache/2.2.9 (Debian ) PHP/5.2.6-1 +
lenny3 with Suhosin -Patch X -Powered -By : PHP/5.2.6-1 + lenny3 HTTP Response Headers : Connection : close Content- Length: 1209 Content- Type: text / html Date: Wed, 12 Mar 2014 15:27: 58 GMT Server : Apache/2.2.9 (Debian ) PHP/5.2.6-1 + lenny3 with
Suhosin -Patch X -Powered -By : PHP/5.2.6-1 + lenny3
Elapsed time: 388 ms.
Attempting to contact the Autodiscover service using the method of DNS SRV redirect server.
Connectivity Analyzer Microsoft could not contact the Autodiscover service using the DNS SRV redirect method .
additional Details
Elapsed time: 186 ms.
Test steps
Trying to find the SRV record in DNS _autodiscover._tcp.empresa.com .
Not the Autodiscover SRV record in DNS found .
Tell me more about this issue and how to resolve
additional Details
Elapsed time: 186 ms.
Checking for a CNAME record for Autodiscover in DNS for your domain " empresa.com " to Office 365.
Could not validate the Autodiscover CNAME record in DNS. If your mailbox is not in Office 365 , you can ignore this warning.
Tell me more about this issue and how to resolve
additional Details
No Autodiscover CNAME record for your domain ' empresa.com ' .
Elapsed time: 268 ms.
jspt

Hello,
We have the Self-signed certificate that comes with Exchange, and we've created a new self-signed including all our domains mail.company.com, domain.local, exchange13.domain.local, autodiscover.company.com, autodiscover.domain.local.
below I print you the result os the comand Get-ClientAccesServer | fl . Now we've configured a SPC objetct folow the instructions of Wizard
Exchange Server Deployment from Microsoft. We've executed the commands in our new Exchange 13, but can't did it in the old Exchange:
$AutodiscoverHostName = "autodiscover.contoso.com"Get-ExchangeServer | Where {($_.AdminDisplayVersion -Like "Version 8*") -And ($_.ServerRole -Like "*ClientAccess*")} | Set-ClientAccessServer -AutoDiscoverServiceInternalUri https://$AutodiscoverHostName/Autodiscover/Autodiscover.xmlThis is the result of
RunspaceId                           : 89c86f8e-d156-4480-b31d-59215976879b
Name                                 : EXCHANGE13
Fqdn                                 : EXCHANGE13.domain.local
ClientAccessArray                    :
OutlookAnywhereEnabled               : True
AutoDiscoverServiceCN                : EXCHANGE13
AutoDiscoverServiceClassName         : ms-Exchange-AutoDiscover-Service
AutoDiscoverServiceInternalUri       : https://autodiscover.company.com/Autodiscover/Autodiscover.xml
AutoDiscoverServiceGuid              : 77378f46-2c66-4aa9-a6a6-3e7a48b19596
AutoDiscoverSiteScope                : {Nombre-predeterminado-primer-sitio}
AlternateServiceAccountConfiguration :
IsOutOfService                       : False
WorkloadManagementPolicy             : DefaultWorkloadManagementPolicy_15.0.825.0
Identity                             : EXCHANGE13
IsValid                              : True
ExchangeVersion                      : 0.1 (8.0.535.0)
DistinguishedName                    : CN=EXCHANGE13,CN=Servers,CN=Exchange Administrative Group
                                       (FYDIBOHF23SPDLT),CN=Administrative
Groups,CN=First Organization,CN=Microsoft
                                       Exchange,CN=Services,CN=Configuration,DC=domain,DC=local
Guid                                 : e83055fe-217b-4ed6-9cd0-7711097baf99
ObjectCategory                       : domain.local/Configuration/Schema/ms-Exch-Exchange-Server
ObjectClass                          : {top, server, msExchExchangeServer}
WhenChanged                          : 09/03/2014 12:46:07
WhenCreated                          : 08/03/2014 19:15:54
WhenChangedUTC                       : 09/03/2014 11:46:07
WhenCreatedUTC                       : 08/03/2014 18:15:54
OrganizationId                       :
OriginatingServer                    : severdc.domain.local
ObjectState                          : Unchanged
I hope this stuff can help you.
Thanks!!
jspt

Outlook 2007 does not connect to exchange at computer startup

Hi all :)
Here's the situation we're encountring: we are using exchange 2010 with outlook 2007 clients. The issue is that at the startup of the computer, outlook does not connect to exchange (it opens up but it marks that it's not connected to exchange). After trying
a few times it connects and stays stable (if I close outlook and I open it again, it connects normally).
This suggests that there's may be a DNS problem: The client is having an issue resolving the name, but once it does and the IP of exchange is available in the cache, outlook doesn't face any issues.
So I ran some nslookup commands and I noticed the following:
when I try to resolve the name of exchange, the request times out twice before providing the answer.
This issue occurs only for forward lookups (when I try to resolve the same IP for the hostname, there's no timeout)
I also noticed that this issue only occurs when I run nslookup from the client machines (no timeout when I run it from exchange for instance).
Any ideas about what the problem might be? Could it be something else other than DNS?
Thank you all for your help.

Hi all,
The problem seems not to be related to DNS. Our exchange 2010 organization was actually migrated from a 2007 one. Since then we noticed this issue of outlook taking too much time to connect and sometimes disconnects. I was messing around into adsiedit and
I noticed that a decomissioned Mailbox Server from our old exchange 2007 organization still exists among the new exchange 2010 objects.
To further look into it, I ran best practise analyser, the result (to my surprise) was that exchange is still trying to contact the old exchange 2007 server.
I ran some network trafic captures with Network Monitor, but I was not very successful interpreting anything.
I uploaded the .cap files with the best practise analyser report and a print screen of the old server into adsiedit objects. I hope you'll be able to help with it.
I took the network captures on the two CAS Servers (configured in a CAS array) and on a client machine. The IP addresses are as follow:
client 192.168.0.47
Domain Controller1 192.168.1.205
Domain Controller2 192.168.1.213
CAS1 192.168.2.216
CAS2 192.168.2.217
CAS Array 192.168.2.218
Download Link: https://onedrive.live.com/redir?resid=9360346C01880F58%21935
Thanks,

Since upgrading to iOS 6 my iPhone now does not connect to my 2013 elantras Bluetooth set up where as with the previous version of iOS it connected seamlessly. Please let me know if you have any solutions. Thanks

Since upgrading to iOS 6 my iPhone now does not connect to my 2013 elantras Bluetooth set up where as with the previous version of iOS it connected seamlessly. Please let me know if you have any solutions. Thanks

Have you checked to see if Elentra has a firmware update since the new iOS release?

TS3276 iCloud email on OSX 10.8 does not connect to the server after sleep

iCloud email on OSX 10.8 does not connect to the server after sleep. The only way I can reconnect the iCloud email is to restart the computer. Does anyone have any ideas how to resolve this issue?

I would suggest you try opening "Mail">click on "Mailboxes" in the Menu Bar> and select "Rebuild" from the list. That may solve it.

My ipod works in itunes but does not appear in "my computer" after I changed the properties

My ipod works in itunes but does not appear in "my computer" after I changed the properties.
First off, I'm using Windows XP (and Mac SnowLeopard) Here's how it started. For some reason my ipod started showing up as a camera when I plugged it in. It works fine in itunes, though. But when I tried to access it from "my computer" it only
showed me the one and only picture I had on my ipod. I deleted that picture hoping it would no longer show up as a camera. When it still did I right-clicked on it in "my computer" and selected "properties". Under "autoplay" I
chose for it to 'not show up' or 'take no action' or some such deal when I plugged it in. I thought that would stop it from popping up the window that asks whether i want to 'open camera wizard' or 'open camera scanning' or 'open folder to view files' or 'take
no action' , etc. But now it won't show up in "my computer" at all. I also have a Mac with SnowLeopard. When I plugged my ipod into it my ipod doesn't show up in "finder" either! So basically my problem is not a mechanical one with hardware
or software; yht ipod still works fine in itunes. I just need to undo the change I made. I've searched all around my preferences, utilities, options, etc. It shows up on my "Device Manager" but not on "Disk Management".
Any help would be very much appreciated. Thanks.

Hi,
To show up in Windows Explorer, you can try placing the iPod into
disk mode.
Moreover, i recommend you to
restore ipod to factory settings.
If this issue still persists, locate to device manager, uninstall and reinstall USB Mass Storage Device driver.
Here is an article you can refer to below:
http://support.apple.com/kb/TS1369
To get more help, you can also redirect to apple support forum:
http://www.apple.com/support/ipod/
Thanks!
Andy Altmann
TechNet Community Support

Mail does not connect to mail servers after 10.5.7 update

Updated Macbook Air with 10.5.7 update. The update went without problems.
After starting the computer, the Mail program does not connect to the mail servers - IMAP, POP, SMTP.
Otherwise the internet connection is OK for other programs, connection is through WIFI - Airport Extreme, Time Capsule... In all cases the same problem with Mail - showing the following
The server error encountered was: The connection to the server “mail.mac.com” on port 993 failed (error 1: Operation not permitted)
The connection doctor shows
Mail was able to connect to the internet
and for all the servers - could not connect, check your connection...
Did repair of keychain and permissions - no change in status of Mail... any ideas?

This is what shows up in console: (maybe someone who can understand this can help us!)
15.05.09 16:38:26 Mail[1478] GET /internetservices/issupport/1_27a4cv2b6061/clientConfig.plist (FAILED), httpStatusCode:-1, errorType:100 (domain=NSPOSIXErrorDomain, code=1), transactionState:5, txnId:2F42C0AC-8189-4309-B914-AB3759688961, auto-retries=2, manual-retries=0
15.05.09 16:38:26 Mail[1478] GET /internetservices/issupport/1_27a4cv2b6061/clientConfig.plist (FAILED), httpStatusCode:-1, errorType:100 (domain=NSPOSIXErrorDomain, code=1), transactionState:5, txnId:DD2C955C-DAD7-4CAF-BFD7-79B75F6C93E0, auto-retries=2, manual-retries=0
15.05.09 16:38:27 Mail[1478] POST /Info.woa/wa/XMLRPC/accountInfo (FAILED), httpStatusCode:-1, errorType:100 (domain=NSPOSIXErrorDomain, code=1), transactionState:5, txnId:D4B63982-058D-4AF4-ADBB-CF84E9DDE8EF, auto-retries=2, manual-retries=0
15.05.09 16:39:32 Mail[1485] GET /internetservices/issupport/1_27a4cv2b6061/clientConfig.plist (FAILED), httpStatusCode:-1, errorType:100 (domain=NSPOSIXErrorDomain, code=1), transactionState:5, txnId:13DE143D-0FE5-443B-834E-253082F0E448, auto-retries=2, manual-retries=0
15.05.09 16:39:32 Mail[1485] GET /internetservices/issupport/1_27a4cv2b6061/clientConfig.plist (FAILED), httpStatusCode:-1, errorType:100 (domain=NSPOSIXErrorDomain, code=1), transactionState:5, txnId:EAE08B1B-6DEE-459B-8903-0E4700B3087B, auto-retries=2, manual-retries=0
15.05.09 16:39:32 Mail[1485] POST /Info.woa/wa/XMLRPC/accountInfo (FAILED), httpStatusCode:-1, errorType:100 (domain=NSPOSIXErrorDomain, code=1), transactionState:5, txnId:ABEB15F4-5650-4230-BDA8-ED1512B59443, auto-retries=2, manual-retries=0

Outlook 2013 asks for credentials but does not connect for Exchange email, but only when out of office

Hi,
New employee wishes to use his Office 365. Have loaded onto new PC, connected to exchange, loaded his folders, everything is fine.
When he leaves the office and connects at home, he is asked for credentials.
I have tried the usual credentials: [email protected] and domain\user
With each attempt, Outlook displays disconnected
The password is correct, OWA he can log on fine, he has no problem when returning to the office. He has all the correct permissions in AD.
No other user has a problem when away from the office, but every other user is using Office 2010
Advice appreciated.

Hi,
Please make sure the user has enable Outlook Anywhere in Outlook.
To turn on Outlook Anywhere, on the Connection tab, under
Outlook Anywhere, check Connect to Microsoft Exchange using HTTP, and then click
Exchange Proxy Settings. Your Exchange admin must enable this feature and provide you the proxy settings. For more information, please refer:
http://office.microsoft.com/en-in/outlook-help/use-outlook-anywhere-to-connect-to-your-exchange-server-without-a-vpn-HP010355551.aspx
Best Regards,
Steve Fan
TechNet Community Support

Outlook clients on Windows XP not connecting to Exchange 2013

Previously outlook on XP machines were working fine with a SAN certificate having the mail.company.com as common name. Since we're moving to Exchange Hybrid we reissued the certificate and made company.com as the common name after that change all Outlook
on XP machines are not able to connect to the Exchange 2013. It is always asking for password. Outlook clients on windows 7 and 8 have no problem.
I wanted to run the below commands but I'm worried that it may break the connections of the Windows 7 and 8 machines:
Set-OutlookProvider
EXCH -CertPrincipalName msstd:mail.XXX.com
Set-OutlookProvider
EXPR -CertPrincipalName msstd:mail.XXX.com
Is it safe to run the commands or I should just reissue again the certificate and make the mail.company.com as the common name? Will there be any issues with Exchange 2013 hybrid if I do this?

I just reissued the certificate and all Outlook on windows xp are working now.

XP Outlook 2007 not connecting to exchange server for office365 mail

Here is the deal it is the workstation it self no one can get there account to connect through outlook on the work station the person who's work station it is can connect with outlook on other work stations.
1. First thing it does is continues to prompt for user name/ password window.
2. After 2 popups of name/ password It states "Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The connection to Microsoft Exchange is unavailable. Outlook must
be online or connected to complete this action."
3. I have then gone through control panel > mail > Show Profiles > Removed the only profile > Add profile > Pop-up for username/ password appears > fill it in > Add new email account then pops-up > fill in Name, Email Adress,
Password, Retype Password > Configuring - green checkmark on "Establish network connection" - bullet arrow at "Search for johndoe@blankcom server settings" then pop-up for "User Name: Password:" form filled in
- pop-up reappears and form filled out for 10 times > cancel > pop-up "The action cannot be complerted. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action." >
Click "OK" > Microsoft Exchange form pop-up "Microsoft Exchange server:/Mailbox:" form is already filled out Click "OK" > pop-up "The action cannot be complerted. The connection to Microsoft Exchange
is unavailable. Outlook must be online or connected to complete this action." but green Check mark next to "Search for johndoe@blankcom server settings" > pop-up "The action cannot be complerted. The connection
to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action." Click "OK" > Verify Settings form appears "E-mail Adress: Password: Retype Password:" form filled out click "Retry"
> green check mark turns to bullet arrow at "Search for johndoe@blankcom server settings" the back to pop-up "The action cannot be complerted. The connection to Microsoft Exchange is unavailable. Outlook must be online
or connected to complete this action." > Click "OK" > Microsoft Exchange form pop-up "Microsoft Exchange server:/Mailbox:" form is already filled out Click "OK" > Cannot Log on to Server
> I cancel and seek help
3. Have ran MCATest Results are auto discover successful with errors. Errors are as follows
1>Testing TCP port 443 on host dot.ny.gov to ensure it's listening and open.
The specified port is either blocked, not listening, or not producing the expected response.
Additional Details
A network error occurred while communicating with the remote host.
2> Analyzing the certificate chains for compatibility problems with versions of Windows.
Potential compatibility problems were identified with some versions of Windows.
Additional Details
The Microsoft Connectivity Analyzer can only validate the certificate chain using the Root Certificate Update functionality from Windows Update. Your certificate may not be trusted on Windows if the "Update Root Certificates" feature isn't enabled.
Please help

Yes we have narrowed it back to the workstation as the user can sign on other workstations through outlook and when using the control right click and checking connectivity activity. This work station tries to connect to the right server name as the
one that does connect. But it hangs up there using the same server name, type- directory, status-connecting then asks for user name password. No change is status after it is filled out and OK is pressed.

On Windows 2012 Terminal Server Outlook fails to connect to Exchange 2013

I have a new install of Windows 2012.  I have two physical servers. One is a W2012 std Domain Controller ("DC"). The Second is configured as W2012 HyperV  ("HV"). Under HV I have
two VMs. One VM is W2012/Exchange 2013 ("ExchVM) and the other is W2012/Terminal Server ("VMTS"). All systems are behind a firewall appliance. Exchange is working via Outlook and OWA internally and externally. The self
created SSL must be installed manually on external machines since it comes up as an untrusted certificate. Once installed remote outlook works and OWA works. I have configured the terminal server and I am able
to login remotely as various users under my "TS group". The problem is when ever I attempt to open Outlook for the 1st time, it fails to connect to the exchange server.   (Open Outlook 2013, click next
on the splash screen, "Yes" Add an Email Account splash screen, click next, Auto Account screen populates NAME and Email Address correctly, click next, Searching for mail server settings..., check on establishing network connection, check on searching
for alias@ domain, then fails the logging on to the mail server) The error reads: "Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The
connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."   I am connected in RDS from offsite, and from the RD session I can access shared folders on ExchVM and DC. I have
tried have verified the server Exchange server name is correct via "Get=ClientAccessServer" command. I have also tried to use the guid via "Get-Mailbox
ALIAS | fl name, exchangeguid. Keep in mind all desktop users on the network are connecting to Outlook without issue.
I would appreciate any thoughts on solving this issue.

Hi,
According to your workaround, it seems that the Outlook Anywhere configuration in Outlook client is not correct when using the Autodiscover service.
Once you connected to Exchange server by manually settings, please run Test E-mail AutoConfiguration tool in external Outlook client to check the autodiscover service:
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 check the Log tab and confirm whether the Autodiscover service is connected successfully. Also confirm if the connection issue happens to all external users when they open Outlook for the 1st time. In Exchange server, please make sure
autodiscover.domain.com has been included in your Exchange certificate which is assigned with IIS service.
Regards,
Winnie Liang
TechNet Community Support

Outlook does not reconnect to correct server after failover

Using Exchange 2013 SP1 with Outlook 2010 SP2, some clients did not fail over their HTTP connections when DNS was altered for the Exchange SCP, trying to find the reason why or if this is a software bug. Restarting Outlook ratifies this problem,
autodiscover works as expected and DNS (including cache) on the client are showing the correct info (ie updated Exchange Server).

Hi,
Please try to re-create profile for testing.
Thanks
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Mavis Huang
TechNet Community Support

Redirect emails in OWA and Outlook 2010 not working in Exchange 2013

I have an new install of Exchange 2013 with all updates.
When I setup an inbox rule to redirect messages to another contact it is not working.
When I used Outlook 2010 and ran the rule manually I received this error:
"the redirect action is not currently supported with run rules now"
It seems that I didn't setup up something correctly in Exchange 2013 or a feature is not turned on. Please assist.
In the EM console when I setup forwarding that is working. Its the inbox rule redirect not working.

Hi,
From your description, I recommend you use the following cmdlet to ensure that the DeliverToMailboxAndForward parameter is set to $True.
Get-Mailbox <identity> | fl DeliverToMailboxandForward
If this parameter is false, you can use the Set-Mailbox cmdlet to set it and check the result.
Hope this can be helpful to you.
Best regards,
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]
Amy Wang
TechNet Community Support

Outlook RT not connecting to Exchange

Outlook RT will not connect to our Exchange Server. The W8 Mail app connects with no problem and have been using since the start. It cannot resolve the username and will not connect even though it asks for and accepts
my Exchange password. I contacted Surface tech support and they were absolutely clueless. No help at all. Is there anything special that needs to be done on the MS Exchange side for Outlook for RT. We connect with iDevices and W8 Phones
using Activesync with no issues. I realize this is a "Preview" release but you would think the tech support would at least propose some reasonable fix suggestions. The support person seemed to be looking on blogs for help while I sat
on the phone...dissapointing.

I get all that, and my RTs are configured. I've even got scripts to automate the process when a new user account is added to the device.
I think Mattias had the clearest response on the issue and since then we've all moved on.
What I'm saying is that why do we have to manually configure outlook on an RT for an on-prem connection even though every other device that we can throw at it (being the exchange server) just auto connects.
What I don't have are SRV records in the public DNS, and that probably might be a cause, but like others commenting in this thread I don't get the logic behind an MS device that is so far the only device that I can't get to automatically connect to my MS
environment.
What really weirds me out is that I can even get the standard RT mail client to connect to my exchange via autodiscover, but not outlook.
So I'd like to skip as much of the usual diagnostic info as I can and reiterate that for my domain the Remote Connectivity Analyzer reports everything as configured correctly, if it didn't I'd be back on same noob forum and certainly not in here.

Outlook does not connect to Exchange 2013 after name change due to marriage

Similar Messages

Maybe you are looking for