Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 220
  • Last Modified:

Exchange 2000 recieve problem

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
scotthrobinson
Asked:
scotthrobinson
  • 2
  • 2
  • 2
1 Solution
 
eecarlCommented:
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
 
geoffrynCommented:
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
 
eecarlCommented:
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
Veeam Disaster Recovery in Microsoft Azure

Veeam PN for Microsoft Azure is a FREE solution designed to simplify and automate the setup of a DR site in Microsoft Azure using lightweight software-defined networking. It reduces the complexity of VPN deployments and is designed for businesses of ALL sizes.

 
scotthrobinsonAuthor Commented:
It actually did start working after i remade the dns zone following geoffryn's advise. thank you for your help though
0
 
scotthrobinsonAuthor Commented:
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
 
geoffrynCommented:
Cool beans.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 2
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now