Solved

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

Posted on 2014-10-17
9
69 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
NAS Cloud Backup Strategies

This article explains backup scenarios when using network storage. We review the so-called “3-2-1 strategy” and summarize the methods you can use to send NAS data to the cloud

 

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

Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
MS Outlook is a world-class email client application that is mainly used for e-communication globally.  In this article, we will discuss the basic idea about MS Outlook, its advanced features, and types of MS Outlook File formats.
In this video we show how to create an email address policy 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…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…

776 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