Solved

Exchange 2010 migration to 2013

Posted on 2014-09-16
13
306 Views
Last Modified: 2014-09-24
Hi im migrating exchange 2010 to 2013

Ive installed exchange 2013 now and i deleted the defaut receive connectors on it

Can someone post screenshot of the settings of the default connector because my client that are on my exchange 2013 cannot send email  ... The get stuck in the outbox folder in outlook

They can receive mail

Thanks !
0
Comment
Question by:jfguenet
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 7
  • 5
13 Comments
 

Author Comment

by:jfguenet
ID: 40326696
i tried to recreate one but i cannot get to make it work...
0
 
LVL 12

Expert Comment

by:Md. Mojahid
ID: 40327243
If only the default one was deleted, then Go into the ECP then "Mail Flow" click on the "Receive connectors" at the top. Now click the "+" symbol to add one.

The name would be something like, "Default *servername*"

Server should have the FQDN of the Exchange server.

Role would be "Hub Transport"

Type would be "Internet"

Network Adapter bindings leave default to "All Available"

Then click on "Finish"

Now click on the new connector, and then click the little "Pencil" to edit it.

Click on "Security" on the left and make sure the following have check boxes.

Transport Layer Security (TLS)
Basic Authentication
Offer Basic authentication only after starting TLS
Integrated Windows Authentication
Exchange Server authentication
Then under "Permission Groups" make sure the following have check boxes in them

Exchange Servers
Legacy Exchange Servers
Exchange Users
Then left hand side click "Scoping"

Make sure that in "Remote network settings" that 0.0.0.0-255.255.255.255 is listed. You can also add the IPv6 equivlant since the default does have this which is "ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff"

Then below that in the "Network Adapter settings" make sure that All available IPv4 and IPv6 are in there for port 25. Then click "Save".

You may need to restart the services or reboot the server to take full effect.

Then, don't delete the default connectors anymore. ;-)

http://www.techieshelp.com/setup-exchange-2013-receive-connector/
0
 

Author Comment

by:jfguenet
ID: 40328864
Ok i created it back the defaut receive connector

But why client on exchange 2013 database cannot send email to internal user and external users

I can receive emails

Thanks for your help !
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
LVL 17

Expert Comment

by:Brad Bouchard
ID: 40329059
Did set your firewall to allow port 25 (SMTP) traffic from the internal IP of the new 2013 Exchange Server going out?  If not, then mail won't go out.
0
 

Author Comment

by:jfguenet
ID: 40329089
Well i turn out the firewall for now on so it should no be a prblem
0
 
LVL 17

Expert Comment

by:Brad Bouchard
ID: 40329112
Did *you set...
0
 
LVL 17

Expert Comment

by:Brad Bouchard
ID: 40329113
Do you mean turned it off, not out?
0
 
LVL 17

Expert Comment

by:Brad Bouchard
ID: 40329117
By firewall I'm referring to your network firewall as well, and not just Windows Firewall.  Although, you should turn Windows Firewall off on the server, or allow the proper exclusions for it.  Check both of them.
0
 

Author Comment

by:jfguenet
ID: 40330110
Yes i mean turn it off sorry

Everything about the fw is ok

The email just stay in the outbox

Is there a way to see the error on the exchange 2013 server or my exchange 2010

If it stay in the outbox is it something wrong with the smtp send connector ?

Thanks !
0
 
LVL 17

Expert Comment

by:Brad Bouchard
ID: 40330900
Have you restarted all Exchange related services?
0
 

Author Comment

by:jfguenet
ID: 40330908
yes i even reboot the server
0
 

Accepted Solution

by:
jfguenet earned 0 total points
ID: 40332956
Nevermind i find the solution myself i rebuild a new exchange 2013 on a lab and found out that i needed the receive connector

Default Frontend "name of the server"

As soon i created this email was sending fine
0
 

Author Closing Comment

by:jfguenet
ID: 40341126
I found the solution myself
0

Featured Post

NFR key for Veeam Backup for Microsoft Office 365

Veeam is happy to provide a free NFR license (for 1 year, up to 10 users). This license allows for the non‑production use of Veeam Backup for Microsoft Office 365 in your home lab without any feature limitations.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Background Information Recently I have fixed file server permission issues for one of my client. The client has 1800 users and one Windows Server 2008 R2 domain joined file server with 12 TB of data, 250+ shared folders and the folder structure i…
This article lists the top 5 free OST to PST Converter Tools. These tools save a lot of time for users when they want to convert OST to PST after their exchange server is no longer available or some other critical issue with exchange server or impor…
In this Micro Tutorial viewers will learn how to restore their server from Bare Metal Backup image created with Windows Server Backup feature. As an example Windows 2012R2 is used.
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…

623 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question