Solved

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

Posted on 2014-10-17
9
74 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 7

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 7

Expert Comment

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

Learn about Edgartown's quest to ensure the safety and security of the entire town's employee and citizen data. Read the case study!

 

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
 
LVL 7

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 7

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

Is Your AD Toolbox Looking More Like a Toybox?

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

Suggested Solutions

This article aims to explain the working of CircularLogArchiver. This tool was designed to solve the buildup of log file in cases where systems do not support circular logging or where circular logging is not enabled
The new Gmail Phishing Scam going around is surprising even the savviest of users with its sophisticated techniques.
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…
Nobody understands Phishing better than an anti-spam company. That’s why we are providing Phishing Awareness Training to our customers. According to a report by Verizon, only 3% of targeted users report malicious emails to management. With compan…

726 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