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 :

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-29ff9bcebf17

Open in new window

FireBallITAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Gareth GudgerCommented:
Hey Cahit,

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?
0
FireBallITAuthor Commented:
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
0
FireBallITAuthor Commented:
some times it returns

'550 5.1.1 RESOLVER.ADR.RecipNotFound; not found'
0
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Gareth GudgerCommented:
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/
0
FireBallITAuthor Commented:
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
0
Gareth GudgerCommented:
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.
0
FireBallITAuthor Commented:
how should i create autodiscovery records ?
0
Gareth GudgerCommented:
You can do this one of two ways. But you need to create a DNS record with your external DNS provider.

If you have autodiscover.yourdomain.com on your SSL certificate, you can create an A or CNAME record called autodiscover.

If you don't have autodiscover on your SSL certificate then you can create an SRV record (as long as your external DNS provider support them).
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
FireBallITAuthor Commented:
thank you
0
Gareth GudgerCommented:
Glad to help!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.