Solved

Exchange 2000 recieve problem

Posted on 2002-04-21
6
213 Views
Last Modified: 2010-03-05
I have exchange server 2000 running on a internal private network linked to an outside real ip address through a router. I can send mail all day long just fine but i cannot recieve a thing. I have checked my mx records on my external dns server and my internal one and they are both fine, i can send and recieve all kinds of other traffic from that box as well, i am running a small ftp server on it as well, i have checked the ports on the firwall and it looks like it should be fine. any help would be appreciated.

ok more details on the situation. Running external network of rrcompconsult.com dns hosted by 2 external dns servers. then i have a netgear router acting as a firewall, but i have the dmz set up to point to the exchange server. I have a dns server set up internaly on the exchange server becuase it is also a dc. i have the mx records on the 2 external servers. i can send mail out of my network to anywhere but i cannot recieve anything from any host. i tested the system using my hotmail account and i did not recieve any error message back either. this one has really got me. any help would be appreciated.
0
Comment
Question by:scotthrobinson
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
  • 2
6 Comments
 

Expert Comment

by:eecarl
ID: 6960783
what is the registered external domain name and is it different from the internal name.

Check the error for none delivered mails i.e send a mail to the internal server from a hotmail account and look for non delivered error. If error says could not relay then you will need to create a Recipient Policy, you will find this in system manager second in the tree Recipient polices, just add a policy in which you external registered domain name is entered as an SMTP address.

Best regards

Carl
0
 
LVL 11

Accepted Solution

by:
geoffryn earned 200 total points
ID: 6961107
You MX record on the Internet side is wedged.  It looks like this on your primary DNS.


> rrcompconsult.com
Server:  ns1.ccrsportscollectables.com
Address:  66.121.216.157

rrcompconsult.com
        primary name server = ns1.ccrsportscollectables.com
        responsible mail addr = admin.ccrsportscollectables.com
        serial  = 25
        refresh = 900 (15 mins)
        retry   = 600 (10 mins)
        expire  = 86400 (1 day)
        default TTL = 3600 (1 hour)
>

It should look like this:

> bbhealthlaw.com
Server:  ns1.ccrsportscollectables.com
Address:  66.121.216.157

bbhealthlaw.com MX preference = 0, mail exchanger = ntpdc1.bbhealthlaw.com
bbhealthlaw.com nameserver = sol.earthlink.net
bbhealthlaw.com nameserver = luna.earthlink.net
ntpdc1.bbhealthlaw.com  internet address = 63.224.51.202
sol.earthlink.net       internet address = 207.69.188.192
luna.earthlink.net      internet address = 207.69.188.193
0
 

Expert Comment

by:eecarl
ID: 6961895
The NS lookup seems OK. It resolves the host ip and has an Mx record. The problem is the priority. Change this to 10,

Non-authoritative answer:
bbhealthlaw.com MX preference = 0, mail exchanger = ntpdc1.bbhealthlaw.com

ntpdc1.bbhealthlaw.com  internet address = 63.224.51.202

mx record points to this host. But your record has priority 0 change this to priority 10, if you have a second mail server and want it to have a lower priority give it 20, ect.

If you have problems after changing this to 10 then your problem is not the MX record.



Non-authoritative answer:
bbhealthlaw.com MX preference = 0, mail exchanger = ntpdc1.bbhealthlaw.com

ntpdc1.bbhealthlaw.com  internet address = 63.224.51.202
0
Instantly Create Instructional Tutorials

Contextual Guidance at the moment of need helps your employees adopt to new software or processes instantly. Boost knowledge retention and employee engagement step-by-step with one easy solution.

 

Author Comment

by:scotthrobinson
ID: 6961931
It actually did start working after i remade the dns zone following geoffryn's advise. thank you for your help though
0
 

Author Comment

by:scotthrobinson
ID: 6961934
Thank you very much this problem has been killing me for a couple of days. The dns zone looked fine from inside windows but after blowing the zone away and recreating it, the exchange server started pumping mail immediatly. Thank you for all your help.
Scott Robinson
R&R Computer Consulting
0
 
LVL 11

Expert Comment

by:geoffryn
ID: 6962946
Cool beans.
0

Featured Post

Optimizing Cloud Backup for Low Bandwidth

With cloud storage prices going down a growing number of SMBs start to use it for backup storage. Unfortunately, business data volume rarely fits the average Internet speed. This article provides an overview of main Internet speed challenges and reveals backup best practices.

Question has a verified solution.

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

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.
After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
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…
how to add IIS SMTP to handle application/Scanner relays into office 365.

728 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