[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 51
  • Last Modified:

Exchange Not Receiving External Mail

Hi Everyone, Im at a total loss here and nowhere to go.

Background

So I've installed Server 2012 Datacenter running Hyper-V only.
Instide I have Server 2012 R2 Standard with Essentials Installed for remote web access and another Standard Instalation with Exchange 2016

named them

DISCOVERY12 (Domain Controler with Essesntials) 192.168.0.3
DISCOVERYEX (Exchange Server 2016 installed) 192.168.0.4

So I have manage to set it all up and I can access me remote web at remote.mydomain.com and i can access owa at mail.mydomain.com

I can send and receive mail internally but only send mail external and not receive any external mail.

Ports are 80 going to 192.168.0.3
Ports are 443 going to 192.168.0.3
Ports are 25 going to 192.168.0.4

When I check the ports on http://www.yougetsignal.com/tools/open-ports/ I get the 80 and 443 is open but 25 is closed but 25 is definitely being forward to my exchange server.

Now, a netstat search on 25 only gives me

TCP 0.0.0.0:25

When I open telnet on the exchange server and type in open mail.mydomain.com 25 it seems to connect
When I type Helo i get DISCOVERYEX.home.local

Not sure if you should be able to telnet from a remote computer but it doesn't want to connect to that address from my work computer on that port.

I've added a External Receive Connector and chose
Frontend Transport
Internet
All available IPv4 Addressees and
port 25

What else am i missing here
0
Marlo Schlebusch
Asked:
Marlo Schlebusch
  • 4
  • 2
  • 2
  • +2
1 Solution
 
MAS EE MVETechnical Department HeadCommented:
Hi,
Please open www.canyouseeme.org and check 25 port is listening.

Please make sure you have enough free space on the Exchange installation drive.

Ports are 80 going to 192.168.0.3   --> Why this is going to DC? It is supposed to be pointed to Exchange.
Ports are 443 going to 192.168.0.3 --> Why this is going to DC? It is supposed to be pointed to Exchange.
0
 
Jason CrawfordExchange EngineerCommented:
Did you add an MX record in public DNS?
0
 
Marlo SchlebuschAuthor Commented:
Did you add an MX record in public DNS?

I use to run sbs2011 and mx records still stand from them
0
Free tool for managing users' photos in Office 365

Easily upload multiple users’ photos to Office 365. Manage them with an intuitive GUI and use handy built-in cropping and resizing options. Link photos with users based on Azure AD attributes. Free tool!

 
Marlo SchlebuschAuthor Commented:
Hi,
Please open www.canyouseeme.org and check 25 port is listening.

Please make sure you have enough free space on the Exchange installation drive.

Ports are 80 going to 192.168.0.3   --> Why this is going to DC? It is supposed to be pointed to Exchange.
Ports are 443 going to 192.168.0.3 --> Why this is going to DC? It is supposed to be pointed to Exchange.

So 80 and 443 is going to the DC because of remote web access on remote.mydomain.com but im using arr to rout those ports from mail.mydomain.com to 192.168.0.4 as well. That part is working fine as i can access remote web on port 443 on 192.168.0.3 and OWA on 443 on 192.168.0.4

canyouseeme.org reports success as well
0
 
Jason CrawfordExchange EngineerCommented:
Did you add the Receive Connector in response to this issue or did you add it beforehand?  Unlike 2010, Exchange 2013/2016 will receive email out of the box and requires no additional configuration.  After verifying the disk isn't full on the affected server as -MAS suggested it would be a good idea to enable protocol logging on your front end Receive Connector and send a few more test emails.  If no logs are generated the problem is either with DNS or your firewall.

https://technet.microsoft.com/en-us/library/aa997624(v=exchg.160).aspx
0
 
Procastin8orCommented:
Are you using the same IP address for the mail server as you were using for the "sbs2011" server? If not have you updated internal and external DNS to reflect the correct IP addresses?

Can you telnet to port 25 on the mail server from outside your network?

have you tried https://testconnectivity.microsoft.com/ ?
0
 
Marlo SchlebuschAuthor Commented:
Hi, using the same IP as before  one thing I have noticed is that  this is happening

Attempting to test potential Autodiscover URL

https://mydomain.co.uk:443/Autodiscover/Autodiscover.xml how do i change it to
https://mail.mydomain.co.uk:443/Autodiscover/Autodiscover.xml
0
 
MAS EE MVETechnical Department HeadCommented:
@Marlo
Clients will try to reach the server by domain.com then by autodiscover.domain.com.
So you can ignore this error (i.e. 1st attempt).
Client should reach the server by autodiscover.domain.com.
0
 
Marlo SchlebuschAuthor Commented:
Okay, thanks

So owa is working now and I can connect my phone to it as well and but when i run outlook on a domain computer it refuses to connect to the server and says "The connection to Microsoft Exchange is unavailable. Outlook must me online or connected to complete this action"
0
 
Seth SimmonsSr. Systems AdministratorCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 4
  • 2
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now