The name cannot be resolved. New account on Exchange 2013
So here is the deal.
We created a new account for a new employee on our nice shiny new Exchange Server 2013.
When we try to setup the user account on outlook we are prompted with the following:
"The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
So then I try to manually configure the account by first adding the FQDN on the exchange server then the IP Address and I receive:
"The name cannot be resolved. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
AWESOME!
So here are a few things I try to determine if it's the user profile, the computer, or the account itself.
- I log on as myself on the same computer and attempt to add my account on outlook... SUCCESS! so now I know it's not the computer.
I log them on to another computer and attempt to do the same... FAIL... I still get the error. So we know it's not the profile or the outlook version as one attempt was on outlook 2010 and the other on outlook 2013.
- So i go back to the original computer and see if I can manually configure the account and exchange proxy settings... SUCCESS!!! it worked! and now the end user can log onto their outlook with no issues.
My problem is that I shouldn't have to do this and would sure like to know why all the accounts I'm creating now will not just auto configure.
Also, I compared the account memberships and permissions to another similar working account in AD to ensure all things were the same... Could this be service related on the server side? Perhaps a DNS issue?
I've checked the services on the server and all of them minus anything pop3 is running.
I KNOW FOR SURE THE PROBLEM IS NOT ON THE LOCAL COMPUTER BUT IN OUR SERVER ENVIRONMENT
I'm not sure how relevant this is to my issue but, we do have 2 different types of emails... for example;
our main doman email usually looks like
user@ABCinc.com
but we also have
user@DEFinc.com & user@GHIinc.com
this specific user has email:
user@DEFinc.com only...
not sure if that makes sense but I figured I'd throw it out there just in case... Also the account was created through the ECP on exchange and not on ADUC (i didn't do it, i swear!)
We created a new account for a new employee on our nice shiny new Exchange Server 2013.
When we try to setup the user account on outlook we are prompted with the following:
"The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
So then I try to manually configure the account by first adding the FQDN on the exchange server then the IP Address and I receive:
"The name cannot be resolved. The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete this action."
AWESOME!
So here are a few things I try to determine if it's the user profile, the computer, or the account itself.
- I log on as myself on the same computer and attempt to add my account on outlook... SUCCESS! so now I know it's not the computer.
I log them on to another computer and attempt to do the same... FAIL... I still get the error. So we know it's not the profile or the outlook version as one attempt was on outlook 2010 and the other on outlook 2013.
- So i go back to the original computer and see if I can manually configure the account and exchange proxy settings... SUCCESS!!! it worked! and now the end user can log onto their outlook with no issues.
My problem is that I shouldn't have to do this and would sure like to know why all the accounts I'm creating now will not just auto configure.
Also, I compared the account memberships and permissions to another similar working account in AD to ensure all things were the same... Could this be service related on the server side? Perhaps a DNS issue?
I've checked the services on the server and all of them minus anything pop3 is running.
I KNOW FOR SURE THE PROBLEM IS NOT ON THE LOCAL COMPUTER BUT IN OUR SERVER ENVIRONMENT
I'm not sure how relevant this is to my issue but, we do have 2 different types of emails... for example;
our main doman email usually looks like
user@ABCinc.com
but we also have
user@DEFinc.com & user@GHIinc.com
this specific user has email:
user@DEFinc.com only...
not sure if that makes sense but I figured I'd throw it out there just in case... Also the account was created through the ECP on exchange and not on ADUC (i didn't do it, i swear!)
ASKER
But why would the autodiscover work on existing users?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Understand and Configure AutoDiscover
https://technet.microsoft.com/en-us/library/bb124251%28v=exchg.150%29.aspx
Will.