Exchange problems

[amdskip]

I'm to the point I'm willing to hire someone to figure this out.

Server 2003 with Exchange 2003, internal mail works, using Outlook Web Access, 3 inboxes, the ports appear to be open, static external IP address.

What steps do I need to take to narrow down the problem?

 

[Allanv]

So external mail doesn't work? inbound / outbound or both?

Are the SMTP connectors setup and corectly?

Any routers or firewalls in the way? if so are the ports open and pointing to the exchange server?
Is the MX record updated and pointing to the external ip address?

 

[amdskip]

I should have clarified more, sorry about that. If I'm logged into OWA I can send email both internally and externally just fine. It is all outside mail to internal that does not work.

I am not sure about the SMTP connectors. This setup used to work and I'm not sure if something was changed with the SMTP connectors.

There is a Firebox X55e but port 80 and 443 are open according to this port scanning program I used. Unfortunately I am not onsite and cannot login to the Firebox nor do I have the login information. If I was onsite I would probably try temporarily hooking up a router and setting up the ports temporarily to see if it changed anything.

I'm not sure if other ports need to be open.

MX records are setup as such:

mail.domain.com to external IP

CNAME: servername points to IP as does www and ftp

OWA is accessed via this URL

servername.domain.com/exchange

 

[Allanv]

So are ports 25 and 110 open?

 

[amdskip]

IP is responding on port 25 (smtp)
IP isn't responding on port 110 (pop3).

 

[dphantom]

Does your MX record resolve to the correct IP? Firebox allowing inbound SMTP to the Exchange servers IP address?

 

[amdskip]

I just used one of the online tools and got this:

10 mail.domain.com 0.0.0.0 3600
10/16/2008 11:01:43 AM Central Standard Time

DNS Host: Unknown

 

[dphantom]

Originally posted by: amdskip
I just used one of the online tools and got this:

10 mail.domain.com 0.0.0.0 3600
10/16/2008 11:01:43 AM Central Standard Time

DNS Host: Unknown

There's your problem.

 

[amdskip]

I just assigned mail to CNAME, maybe this will fix things.

Ok, mx record now says this:

10 mail.domain.com IP address 3600

New messages do not appear in the inbox yet though however. How long should I wait before I assume there is still an issue?

 

[amdskip]

It works it work it works, all fixed

AT comes through for me again, you guys are great!

 

[dphantom]

Standard response from an ISP would be 72 hours, but as you saw email can begin flowing sooner. Be aware that it does take time to propogate your MX record so some domains may not be able to send to you until their DNS is updated.

BTW, any reason why you are using CNAME records? They will work, just curious.

 

[amdskip]

I guess the honest answer is I don't know. Exchange is all new to me and I have no formal training so if something would be better educate me please.

 

[dphantom]

Well, below is the best short explanation I can find.

"You should always use A records instead of CNAME records if possible. They are faster and more efficient (albeit marginally - a CNAME requires two DNS queries, an A record requires one).

A CNAME, or an Alias (it is the only record that can serve as an alias), comes in handy if you are mixing domains, ie. if the forums.companyname.com subdomain is meant to go to www.companynameforum.com, you might use a CNAME. Personally, I would prefer a redirect in that case, but it's an example of where a CNAME might be used (and an A record can't be).

You can read more about CNAMEs in this very useful DNS overview, 'Oversimplified DNS' - www.rscott.org/dns/cname.html."

I only use A records in both internal and external DNS for Exchange. Have never had a need for a CNAME.

PM me if you want to chat more.