Solved

Exchange 2003 - email going to junk between servers on same domain

Posted on 2014-10-17
9
64 Views
Last Modified: 2014-10-20
I have 2 exchange servers on my domain (moving to new box). The email had been flowing great for weeks without issues. During the last couple days people on primary exchange - sending to people on the new exchange - email is going to junk. I tried to add domain safe in Outlook to no affect. I need to allow email between these exchange boxes not be spam. I am sure what has changed and why.

Any ideas?
0
Comment
Question by:allenkent
  • 5
  • 4
9 Comments
 
LVL 6

Expert Comment

by:Thomas Wheeler
ID: 40387622
Are these both Exchange 2003 servers? Do you have service pack 2 installed and IMF configured? Sounds like it could be an IMF issue.
0
 

Author Comment

by:allenkent
ID: 40392422
They are both 2003 servers. The issues was solved by rebooting our DNS server. Not sure why this would fix the issue but the moment the DNS was rebooted all mail started flowing correctly.
0
 
LVL 6

Expert Comment

by:Thomas Wheeler
ID: 40392722
that is strange. Well great glad you got it fixed.
0
 

Author Comment

by:allenkent
ID: 40393050
Ok - the issue is back again. I have not rebooted DNS yet.

2 Exchange 2003 servers. I have disabled IMF (did not fix issue). I do have SP2 installed. I have rebooted both Exchange servers. I will reboot DNS in a moment and see if that fixes again.
0
Do email signature updates give you a headache?

Constantly trying to correctly format email signatures? Spending all of your time at every user’s desk to make updates? Want high-quality HTML signatures on all devices, including on mobiles and Macs? Then, let Exclaimer solve all your email signature problems today!

 
LVL 6

Accepted Solution

by:
Thomas Wheeler earned 500 total points
ID: 40393053
on the exchange servers are both systems resolving via nslookup?
0
 

Author Comment

by:allenkent
ID: 40393070
Odd. Used the following:

NSLOOKUP Server1  (get nice results)

NSLOOKUP Server2 : (get message saying Non-Existent Domain)
0
 

Author Comment

by:allenkent
ID: 40393084
Got It!! The NSLOOKUP help point in the right direction. It looks like my new DNS (secondary) server is not function correctly. The Email Server #2 had the primary DSN as our dns new server address and the secondary dns as our working existing dns server.  I reversed them and all started working.
0
 
LVL 6

Expert Comment

by:Thomas Wheeler
ID: 40393088
ok good I figured it must of been a dns setting.
0
 

Author Closing Comment

by:allenkent
ID: 40393185
NSLOOKUP helped me realize the DNS was not set correctly on exchange server #2.
0

Featured Post

How to run any project with ease

Manage projects of all sizes how you want. Great for personal to-do lists, project milestones, team priorities and launch plans.
- Combine task lists, docs, spreadsheets, and chat in one
- View and edit from mobile/offline
- Cut down on emails

Join & Write a Comment

Resolve DNS query failed errors for Exchange
Marketers need statistics and metrics like everybody else needs oxygen. In this article we explain how to enable marketing campaign statistics for Microsoft Exchange mail.
Familiarize people with the process of utilizing SQL Server stored procedures from within Microsoft Access. Microsoft Access is a very powerful client/server development tool. One of the SQL Server objects that you can interact with from within Micr…
To show how to create a transport rule 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 >> Rules tab.:  To cr…

706 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

19 Experts available now in Live!

Get 1:1 Help Now