Outlook connectivity to Exchange 2013 on .local domain
I need to reconnect Outlook to an Exchange Server that was in an internal .local domain. I recently changed from .local to .org internally and set up a new Exchange Server in the new domain. The old Exchange Server is in the .local domain. I have the old .local DNS server pointing to the old Exchange Server and the .local domain is isolated. I have one PC that is still a member of the .local domain. When trying to recreate an Outlook account, at the "Logging on to the mail server" stage, I get the message: "The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action." The SSL Certificate might be the problem, because it is for the .org domain. I have read that a self-signed SSL cannot be used for Outlook. I also know I can no longer get an SSL with a .local fqdn. OWA will let me log on, but then returns a completely blank page, whether from the PC or on the server using localhost. I need to accomplish this to access the old Public Folders.
Suggestions?
Suggestions?
Don Thomson
Have you tried isolating the old local server from the network (disable the Nic) then load Outlook on the old server if it's not already on there. when you set up the Exchange profile just use 'localhost' and bypass the dns entries. Once you can see the old files/public/folders - export them to a usb drive or dvd.
Hi,
you didn't write what Outlook are you using. Is it 2016?
As for certificates, you can use self signed, and that is not a problem. I have a client that is using self signed cert on Exchange 2016, with no problem. If you don't mind cert error pop up, that is :)
Have you checked to where is AutoDiscover pointing on that old Exchange?
Run: C:\>Get-ClientAccessServic
Maybe it is turned off or something...
Regards,
Ivan.
you didn't write what Outlook are you using. Is it 2016?
As for certificates, you can use self signed, and that is not a problem. I have a client that is using self signed cert on Exchange 2016, with no problem. If you don't mind cert error pop up, that is :)
Have you checked to where is AutoDiscover pointing on that old Exchange?
Run: C:\>Get-ClientAccessServic
Maybe it is turned off or something...
Regards,
Ivan.
ASKER
Exchange 2013, Outlook 2013, Autodiscover is working because it instantly finds my account info and auto-fills the setup form. "Get-ClientAccessService" is not recognized as the name of a cmdlet, function . . . ." I used Get-ClientAccessServer and the command returned https://mail.domainname.org/autodiscover/autodiscover.xml.
ASKER
I have installed/updated Outlook 2013 on the server.
I disabled the NIC and entered my information, using localhost (tried localhost, \\localhost \localhost .localhost and :localhost) for the server name & my username, then clicked "Check name." Error: "The connection to Microsoft Exchange is unavailable. Your network adapter does not have a default gateway."
I re-enabled the NIC and got the error: "The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
I tried the above with "Use cached mode" both checked & unchecked.
I disabled the NIC and entered my information, using localhost (tried localhost, \\localhost \localhost .localhost and :localhost) for the server name & my username, then clicked "Check name." Error: "The connection to Microsoft Exchange is unavailable. Your network adapter does not have a default gateway."
I re-enabled the NIC and got the error: "The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
I tried the above with "Use cached mode" both checked & unchecked.
ASKER
I thought it might have to do with the EWS directory. However, I deleted/recreated EWS, then reset all the virtual directories. Still the "failure to connect" error. OWA went from a blank screen after login to a "something went wrong" page error.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Solved it myself