Exchange 2003 only recieving some incoming messages.

Hi Experts!

Now that I have my exchange server correcting sending and receiving mail from other SMTP domains, I am having another problem.  I have the following MX records:

0     @    exchange.vs-us.com                 TTL 3600
10   @    smtp.secureserver.net               TTL 3600
20   @    mailstore1.secureserver.net      TTL 3600

Some of my user's mail is going to my exchange server, which is priority 0.  The rest is going to the "backup" server hosted by GoDaddy.  I cannot figure out why, and the split seems to be pretty arbitrary.

Any help would be appreciated.
climberboyAsked:
Who is Participating?
 
Hypercat (Deb)Connect With a Mentor Commented:
I think you might be having some router problems.  I tried a trace route to your IP - 216.60.35.249 and it started timing out at an SWbell server - 216-60-35-193.ded.swbell.net.  I also tried to Telnet to port 25 on your email server - exchange.vs-us.com - and got no response.
0
 
climberboyAuthor Commented:
I just found out that the SMTP Virtual Server wasn't running, so I started that and now it works fine.

Along the lines of routing, when I do diagnostics on vs-us.com from mxtoolbox.com, the primary server says that reverse DNS is not configured properly.  Any idea how to fix that?  I'll bet that will cause problems too.

Thanks,

Eric.
0
 
Hypercat (Deb)Commented:
It might cause problems with some outgoing messages, since ISP's like AT&T and AOL routinely check the RDNS and reject email that doesn't comply.  The reason you're getting that response is that your reverse DNS record is currently pointing to 216-60-35-249.ded.swbell.net. It should be pointing to your own email host name - exchange.us-vs.com.  You need to go to wherever the external DNS zone is (godaddy, I guess) and remove that PTR record and add on that points to the correct host name.
0
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.

 
climberboyAuthor Commented:
Reverse DNS is correct... The gateway IP address (216.60.35.194) is what shows when sending through Exchange, and there is a PTR record there for mail.vs-us.com.  We should be in good shape.

I'll post again if I still need more help with the split destinations issue.
0
 
climberboyAuthor Commented:
Hypercat,

Thanks again.  Everything Kosher... had both IPs on the DNS entry.

Have a great day!
0
 
Hypercat (Deb)Commented:
You, too...No more Exchange problems allowed for you this week - you've had your quota ;-)
0
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.

All Courses

From novice to tech pro — start learning today.