• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 33
  • Last Modified:

Exchange Server 2013 Incoming Mail (receive connector)

I am installing an Exchange Server 2013 for the first time.

It is sitting on a single server (Server 2012 R2 Domain Controller). This is the main server in the organisation and has Exchange installed on it.

Everything apart from the receiving emails is working.

I have pointed port 25 from the firewall to the internal IP of the server.

When I look at the "receive connector" in the Exchange Admin Centre I have 5 connectors. Client Frontend, Client Proxy, Default Frontend, Default and outbound proxy.

None use port 25. Also if I look at the scoping the remote network settings are ffff.ffff.ffff.ffff.ffff.ffff.ffff.ffff. (is this right.

Am I missing something. I dont receive and bounce backs to email acccunt I am sending from.


Optima Systems
Optima Systems
1 Solution
Marwan OsmanCommented:
////one use port 25. Also if I look at the scoping the remote network settings are ffff.ffff.ffff.ffff.ffff.ffff.ffff.ffff. (is this right.

//// yes that is right, it means that the exchange server is able to receive message from anywhere.
Marwan OsmanCommented:
you must see the port 25 configured in the send connectors, to view the send connectors configuration, open exchange management shell and run it as administrator, run the cmdlet  Get-SendConnector |fl

you will see the send connector setting including the port 25
Marwan OsmanCommented:
are you able to send internally?
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Optima SystemsNetwork EngineerAuthor Commented:
Send an receive internally is fine. I found that the hosting co of the domain have not entered the new external IP correctly so until that refreshes I don't know if that's the problem  
If they change it and it still doesn't work I will come back to you. Sending externally works perfectly.
Will SzymkowskiSenior Solution ArchitectCommented:
It is sitting on a single server (Server 2012 R2 Domain Controller).
Exchange 2013 is not recommended to be installed on a Domain Controller. Will it install? Yes, will you run into issues? More than likely. See the link below. I would not recommend this setup either does Microsoft.


Nathan HawkinsTechnical Lead - Network SecurityCommented:
Tho not supported dont let that stop you. Personally I dont think thats a good design... Too many eggs in one basket - one blown CPU or even motherboard and there goes your domain everything AND email and probably a few other things...

Anyway, your default receive connector MUST be port 25...

For IP Address: set it to

 and Network adapter bindings: set to (All available IPv4), port 25

Restart your Exchange transport and Exchange information store services and you should be receiving email.
On default frontend Servername connector port 25 should be configured and Anonymous users should be selected.

Default FrontEnd <server name>   Accepts connections from SMTP senders over port 25. This is the common messaging entry point into your organization.

you can refer the ling https://moonstarit.wordpress.com/2013/05/14/receive-connector-on-exchange-2013/ written by sonat yaylali
Optima SystemsNetwork EngineerAuthor Commented:
Dear All
Many thanks for the comments. However is was the DNS entry on the hosting site that was the proble.

Now that's sorted mail is flowing fine.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now