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?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Hypercat (Deb)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

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
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
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

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
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.