Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!
Learn how Concerto can help you.
Solved
Exchange 2007 cannot send or receive
Posted on 2009-05-17
I am hoping someone can help me. I am running Exchange 2007 SP1 on a Windows 2008 Sp1 server. I am not able to send or receive emails externally, internally works fine. Looking over some of the similar cases non seem to resolve my problem. looking in the queue viewer I am seeing the following message:
451 4.4.0 Primary Target IP address responded 421 4.2.1 unable to connect.
I have, as a test removed my anti-virus software. i also made sure that RRAS was disabled as well as the Windows firewall. Addtionally i called my ISP, Comcast, and verified that they are not blocking port 25. When i do a netstat -a i do not see port 25.
Looking at the protocol logs i am seeing this error:
2009-05-17T21:56:24.536Z,I
451 4.4.0 Primary Target IP address responded 421 4.2.1 unable to connect.
I have, as a test removed my anti-virus software. i also made sure that RRAS was disabled as well as the Windows firewall. Addtionally i called my ISP, Comcast, and verified that they are not blocking port 25. When i do a netstat -a i do not see port 25.
Looking at the protocol logs i am seeing this error:
2009-05-17T21:56:24.536Z,I
[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-
7
5- +2
23 Comments
How about your router/firewall - are you allowing the access rule to send mail.....I mean is your router set to allow smpt mail.
What type of router are you using?
What type of router are you using?
Other than that is your Internet Send Connector set up properly. I guess I should have also asked if this was working and then stopped working, if this is a migratin from ex03 , or a fresh move to ex07.
Assumming you have all your ports correctly forwarded. In Exchange 2007 you must create a send connector and a recieve connector. By default, exchange 07 creates a receive connector, but it is for your internal network. So create a new one. In addition to that, you must add your domain.com to accepted domains list.
http://www.computerperformance.co.uk/exchange2007/exchange2007_smtp_connector.htm#Receive_Connectors_-_Designing_Inbound_Message_Flow_
Jorge
http://www.computerperformance.co.uk/exchange2007/exchange2007_smtp_connector.htm#Receive_Connectors_-_Designing_Inbound_Message_Flow_
Jorge
Is the port 25 opened to send and receive mails on your firewall.
Do we have send connector and is the Exchange 2007 Hub server the master for that.
Also do we have Receive connector having anonymous users option checked on it.
Can you run EXBPA and try a command telnet localhost 25 on the exchange server.
Do we have send connector and is the Exchange 2007 Hub server the master for that.
Also do we have Receive connector having anonymous users option checked on it.
Can you run EXBPA and try a command telnet localhost 25 on the exchange server.
Hi there,
The error message clearly states for a pure connection issue (i would modify yet anything in Exchange at this point).
As mentionned before: Does your Firewall allows the traffic on port 25 ?
If this applies, have you set the NAT properly to the Exchange Hub transport ?
Can you try to TELNET your MX Address on port 25 from Outside your network ?
The error message clearly states for a pure connection issue (i would modify yet anything in Exchange at this point).
As mentionned before: Does your Firewall allows the traffic on port 25 ?
If this applies, have you set the NAT properly to the Exchange Hub transport ?
Can you try to TELNET your MX Address on port 25 from Outside your network ?
After much firther investigation and some arguments with my ISP, Comcast, i found out that they are blocking port 25. starting to transistion everyone. sorry for the inconvienence.
now that i found that i wsa being blocked from my ISP on port 25 i changes my send and receive connects to port 587, comcast recomended. i can send now but still not receive. any suggestions?
Well, third party will always send to port 25..
That your ISP is blocking outside traffic on port 25, can be, but I can't believe they are also blocking incoming traffic on the port 25.
That your ISP is blocking outside traffic on port 25, can be, but I can't believe they are also blocking incoming traffic on the port 25.
On your receive connector we have to enable the check box for anonymous user that would be on the permission Groups tab.
Also is there any blockage of the port at your end.
Also is there any blockage of the port at your end.
i have allowed anonymous on the receive connecter and allowed port 587 through on the firewall and still no go.
Third party still won't send to port 587. It's your internal thinggy.
All the SMTP "external" will send to your port 25.
If I understood properly, your ISP requested you to relay your outgoing throug its systems over the port 587 so you cna send your mails.
If the incoming mails are coming directly to your publci address (the one that will be provided by MX query for your domain), they wil come on the port 25.
All the SMTP "external" will send to your port 25.
If I understood properly, your ISP requested you to relay your outgoing throug its systems over the port 587 so you cna send your mails.
If the incoming mails are coming directly to your publci address (the one that will be provided by MX query for your domain), they wil come on the port 25.
I had thought that also, but i am not able to telnet to my Exchange server on port 25. Firewall is setup correctly.
from inside the network is works fine. all of this had been workign fine for months and then all of a sudden it stopped on Friday without any changes made to the firewall. I even changed out firewalls with the same result.
Have you made a password change to yoru Admin account as it also has a reference to the info on your firewalls at times. Was there any other changes made to your internal network during the time when this problem accoured?
I do not see anything in the logs of the firewall but i have opened a ticket with support for it to verify that i am have them configured correctly.
Fortinet verified that when i telnet to the MX record on port 25 it is not getting to the firewall. So it is an ISP issue.
Featured Post
Managing Active Directory can get complicated. Often, the native tools for managing AD are just not up to the task. The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
On September 18, Experts Exchange launched the first installment of the Help Bell, a new feature for Premium Members, Team Accounts, and Qualified Experts. The Help Bell will serve as an additional tool to help teams increase question visibility.
As much as Microsoft wants to kill off PST file support, just as they tried to do with public folders, there are still times when it is useful or downright necessary to export Exchange mailboxes to PST files.
Thankfully, it is still possible to e…
In this video we show how to create an Accepted Domain in Exchange 2013. We show this process by using the Exchange Admin Center.
Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center.
Navigate to the Mail Flow >> Ac…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
Suggested Courses
Course of the Month8 days, 17 hours left to enroll
604 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.