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

How to configure Exchange server 2007 email

I installed Exchange Server 2007 on a server with MS Server 2008 R2 Std. It is connected to the Internet through WAN 1 which comes through a Zyxel Zywall USG 100 firewall. The domain is through Godaddy who is also providing the current IMAP email service. I added MX & A records in Godaddy to point it to the server using the static public IP address. I used MXToolbox to test the connection. It shows the server at mail."mydomain".com & the public IP address but fails the SMTP test because of no response on port 25.  On the Exchange Management Console/Microsoft Exchange/Server Configuration/Hub Transport/Receive Connectors/Default "server name" the FQDN is mail."mydomain".com & under the network tab ports 25, 80 & 443 are available for all IP addresses to receive mail. Anonymous users are permitted under Permission Groups. I unchecked Exchange Server authentication under the Authentication tab to allow changing the FQDN. I have not modified any settings on the Windows or Zyxel firewalls because I read that SMTP was built in on the server & I assumed the ZyXel firewall would allow it by default since it already works with POP & IMAP. I also used Microsoft Remote Connectivity Analyzer using a test email address created in the server & had the same results.
0
Albatross1953
Asked:
Albatross1953
2 Solutions
 
Joshua GrantomSystems AdministratorCommented:
I think you still need to allow the ports 25,10,443 through your firewall for the public IP to the exchange server.
0
 
Thomas GrassiSystems AdministratorCommented:
Also allow port 1025

Most providers block port 25

Allow both plus above

In the router check your port forwarding  access list etc
0
 
Simon Butler (Sembee)ConsultantCommented:
"Also allow port 1025"

Where did you get that port from? Opening another port for SMTP access is not going to help at all, because everyone else is using port 25. Therefore that advice is completely useless.

"...25,10,443..."

I presume you meant 80 there. Again not required and poor security practise to do so. The only ports that you need to open for Exchange to work correctly are 25 and 443. No others. Everything else is optional.

Changing the FQDN on the receive connector is a waste of time. People only do it to pass the dumb tests at MXtoolbox. I would encourage you to reverse that change and leave it as the default. It will have no effect on the operation of your email.

This is either a firewall misconfiguration or the ISP blocking the port.
Check if the ISP allows inbound port 25, they may do so, but you have to call them first.

Simon.
0
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

 
Joshua GrantomSystems AdministratorCommented:
No I did not mean port 80, I meant port 110 but yes it is optional. If they're going to use any type of POP3 client.

Also, when calling the ISP make sure that they create the reverse DNS record.
0
 
Albatross1953Author Commented:
This installation failed. The domain went offline while I was trying to open a port on the firewall. I had to shut down the exchange server to get it working again. I'll remove it & start over tomorrow when the office is empty. Port 110 & 80 must already be open because the POP3 email is working with those ports. Port 25 did not work so that mat be the problem.
0
 
Albatross1953Author Commented:
I have port 25 open on the firewall. I got a response on MX lookup. It said email was ready to use. When I try to create an exchange account in Outlook it says The connection to Microsoft Exchange is unavailable. Outlook must be online or connected to complete. I ran Mircrosoft Remote Connection analyzer & failed because the certificate names didn't match. I installed a certificate & got the same results. Godaddy said to create a CName record using Autodiscover as Host. That kicked the MX lookup back to the old server. The business owner wants this working yesterday. What else should I do?
0

Featured Post

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

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