FireBall
asked on
Exchange migration problem
We have migrate Exchange 2010 SP3 to 2013 CU6
Ex email server name was mail and the newer one's name is posta
when we shut down ex mail server some outlook's return limited connection error , all clients connectiong exchange from outlook via ip address not with domain names and also we are using an email gateway this is why our mx records different then it is so we are redirecting emails to ip address directly from the mail gateway but sometimes it logs some errors like this
Some computers getting smtp errors (smtp connector was created on ex 2010 but what does matters 2013 see connector ? )
when we open back ex 2010 server every thing returns to normal so so. hw that should be possible this are the results of diag :
Ex email server name was mail and the newer one's name is posta
when we shut down ex mail server some outlook's return limited connection error , all clients connectiong exchange from outlook via ip address not with domain names and also we are using an email gateway this is why our mx records different then it is so we are redirecting emails to ip address directly from the mail gateway but sometimes it logs some errors like this
Some computers getting smtp errors (smtp connector was created on ex 2010 but what does matters 2013 see connector ? )
when we open back ex 2010 server every thing returns to normal so so. hw that should be possible this are the results of diag :
PS C:\Users\administrator.> dcdiag
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
***Error: posta is not a Directory Server. Must specify /s:<Directory Server> or /n:<Naming Context> or nothing to
use the local machine.
ERROR: Could not find home server.
PS C:\Users\administrator.> repadmin /showrepl
Repadmin: running command /showrepl against full DC ad.xxxx.com
Default-First-Site-Name\AD
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: dab63121-51f8-48ee-aa92-29ff9bcebf17
DSA invocationID: dab63121-51f8-48ee-aa92-29ff9bcebf17ASKER
Have you moved all mailboxes to 2013?
Yes
What migration documentation are you following?
We just installed brand new 2013 cu6 without any error log then start migrate tool on ecp
Why are you using an IP address to configure Outlook clients?
Yes not a domain name we are using ip address on server name
Are you using a 3rd party certificate on Exchange?
yes we bought from rapidssl for web app.
Are you using split-brain DNS?
No just simple Active directory & dns server
Have you configured all your internal and external URLs in Exchange?
Yes we do we have no problem on owa and we get no error while migration
What version of Outlook are your clients using?
2013
Yes
What migration documentation are you following?
We just installed brand new 2013 cu6 without any error log then start migrate tool on ecp
Why are you using an IP address to configure Outlook clients?
Yes not a domain name we are using ip address on server name
Are you using a 3rd party certificate on Exchange?
yes we bought from rapidssl for web app.
Are you using split-brain DNS?
No just simple Active directory & dns server
Have you configured all your internal and external URLs in Exchange?
Yes we do we have no problem on owa and we get no error while migration
What version of Outlook are your clients using?
2013
ASKER
some times it returns
'550 5.1.1 RESOLVER.ADR.RecipNotFound
'550 5.1.1 RESOLVER.ADR.RecipNotFound
Hey Cahit,
I think something might be wrong with DNS or the URLs. Take a look at my article on 2013 namespace design and implementation. See if this helps.
https://supertekboy.com/2014/07/08/designing-simple-namespace-exchange-2013/
I think something might be wrong with DNS or the URLs. Take a look at my article on 2013 namespace design and implementation. See if this helps.
https://supertekboy.com/2014/07/08/designing-simple-namespace-exchange-2013/
ASKER
but maybe the problem should be mailgateway because our mx records points to mail border
then it forward to ip address of the new mail server .
is there any way to set auto discovery on dns server to point outlook calls to the exchange instead of mx records
then it forward to ip address of the new mail server .
is there any way to set auto discovery on dns server to point outlook calls to the exchange instead of mx records
Your mail gateway and MX records are only for mail flow.
Autodiscover needs to point to the Exchange server directly. Not the mail gateway. So use a CNAME or A record to point to the public IP of your Exchange server. Forward ports 80 and 443 through your firewall to Exchange.
Autodiscover needs to point to the Exchange server directly. Not the mail gateway. So use a CNAME or A record to point to the public IP of your Exchange server. Forward ports 80 and 443 through your firewall to Exchange.
ASKER
how should i create autodiscovery records ?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
thank you
Glad to help!
DCDIAG is just for Domain Controllers, so that is why the test is failing. It is not an Exchange Server test. If you are uncertain about the health of your domain controllers then rerun the test from a DC, or specify the /S switch as indicated in the help.
We do need more information for this problem though.
Have you moved all mailboxes to 2013?
What migration documentation are you following?
Why are you using an IP address to configure Outlook clients?
Are you using a 3rd party certificate on Exchange?
Are you using split-brain DNS?
Have you configured all your internal and external URLs in Exchange?
What version of Outlook are your clients using?