Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

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

Cannot receive outside mail in Exchange 2000

About a week ago, my Exchange server stopped receiving mail from outside addresses. I can send / receive within my own network and I am able send to outside addresses. OWA works fine from work and home as well. However, when I try to email work from an outside address I get a Delay and Failure Notifications. So to make a long story short, we're not getting anything more than interoffice e-mail here.

Using www.dnsreport.com, it tells me:

"ERROR: I could not connect to any of your mailservers! Connection closed before I received all my data (state 1)."

Any ideas?
0
gatchaboy
Asked:
gatchaboy
  • 5
  • 3
1 Solution
 
JasonBighamCommented:
Are your external MX records correct? Can you telnet to your external ip via port 25? Is your router forwarding your external mx Ip properly?

Sounds like something in your external network was changed...
0
 
gatchaboyAuthor Commented:
MX lookup shows that the record points to the external IP of my mail server. When at the office I can telnet to the internal IP on port 25 but NOT the external IP. Furthermore, when I run a check delivery test the results come back as 'host did not respond'.

I'm assuming that the router has to be giving out the proper IP as I'm able to log into OWA and check mail from home using the domain name. What's the best way to check if my router is forwarding my external MX IP properly?
0
 
gatchaboyAuthor Commented:
I was able to telnet to port 25 of the external IP today but it immediately closes the connection, it doesn't even get to prompt me for a username/password.
0
Concerto Cloud for Software Providers & ISVs

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.

 
JasonBighamCommented:
Sounds to me like the firewall/router is blocking it or ONLY allowing connections from your ISP's IP address.
0
 
gatchaboyAuthor Commented:
Ok, spoke to my ISP today. They ran a couple of e-mail addresses through http://centralops.net 's email validator. It passed through level 2 but at level 3 it gave a 'could not verify recipient' error. The MX record looked fine and it actually connects to my SMTP server but closes right away. They suggested that it looks to be a problem on my mail server and not the router.
0
 
gatchaboyAuthor Commented:
The latest development is that I went and reinstalled Exchange. Now I can telnet to port 25 of the external IP of the mail server from inside the building (which I couldn't do before) and run some commands.

Once I'm outside the building the connection closes right away upon telnet to port 25. When I telnet directly to the mail server (not specifying a port), I get a 'No connection could be made because the target machine actively refused it' message, again a new development. Hmmmm.
0
 
gatchaboyAuthor Commented:
More reference: the delivery status notifications I get when I email from an outside address.

4.4.2
Connection has dropped between servers.

4.4.7
The message in the queue has expired. The sending server tried to relay or deliver the message but the action was not completed before the message expiration time occurred.


<added by PashaMod>

Solution:

I was able to answer the question myself by deleting my settings in Server > Protocol > SMTP > Virtual SMTP Server > Properties > Access and clearing the settings in 'Connection Control'. Thanks!
0
 
PashaModCommented:
Question closed and points refunded
PashaMod
CS Moderator
0
 
JasonBighamCommented:
Seems to me there are 2000 other questions that should be closed before one like this... hardly a week old, and not even a business week.
0

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

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