Should be easy!! Troubleshoot external access to Exchange Webmail down

I recently performed some maintenance on an Exchange server (moved the log directory to a more ample hard drive) (and replaced our network switch with one with a Gbit port for our server).

Now we can't access our webmail through
though this used to work before. We have DirecPC satellite internet hookup.

when I went to from a machine on the lan it gave me a diff IP than the one given by mail.nat.....  but I don't think that the IP addy changed because that would just be too much coincidence that it happened at the same time as my changes.
The webmail IS available inside the LAN.

I am able to telnet in port 25 to mail....  and also open a connection on port 80 to mail.... but I can't get a browser to pull anything up from that addy

Any Ideas?
Who is Participating?
MarakushConnect With a Mentor Commented:
Oh sorry... yea kinda got off subject.

Have you checked inbound port 80.


Okay here is what I found so far.

Doing a nslookup on your domain name the mail server's MX record is - IP address

> set query=all
Address:   internet address =
        primary name server =
        responsible mail addr =
        serial  = 2004111600
        refresh = 10800 (3 hours)
        retry   = 3600 (1 hour)
        expire  = 604800 (7 days)
        default TTL = 7200 (2 hours)   nameserver =   nameserver =   MX preference = 10, mail exchanger = MAIL.nationalevents      internet address =

Doing a ping to - dead

Doing a tracert - dead at

14    14 ms    22 ms    22 ms []


Tracing route to []
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms
  2     4 ms     4 ms     4 ms []
  3     4 ms     4 ms     4 ms []
  4     4 ms     4 ms     4 ms []
  5     4 ms     4 ms     4 ms
  6     5 ms     5 ms     5 ms []
  7     *        *        *     Request timed out.
  8     6 ms     5 ms     5 ms []
  9    10 ms    10 ms    32 ms [
 10    15 ms    14 ms    10 ms []

 11    12 ms    11 ms    12 ms []
 12   150 ms    14 ms    16 ms []
 13    24 ms    29 ms    17 ms []
 14    14 ms    22 ms    22 ms []
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.

This is the responce I get when I try a test from

Trying to connect to all mailservers: -  [Successful connect: Got a good response [250 2.1.5 ]]

You email server is listed on 4 spam databases and blacklists.

FIVETENSRC       LISTED (       Reports CNAME of
TXT= "miscellaneous address blocks that have sent spam here"       86400 seconds       0 ms

DSBLALL       LISTED (       TXT= ""       2048 seconds       0 ms

DSBL       LISTED (       TXT= ""       2048 seconds       0 ms

DNSBLNETAUT1       LISTED (       TXT= ""       2048 seconds       0 ms

As for a reverse DNS record - which might cause problems because your reverse DNS record is not listed as you.

Location: United States [City: Germantown, Maryland]

The  reverse DNS entry for an IP is found by reversing the IP, adding it to "", and looking up the PTR record.
So, the reverse DNS entry for is found by looking up the PTR record for
All DNS requests start by asking the root servers, and they let us know what to do next.
See How Reverse DNS Lookups Work for more information.

How I am searching:
Asking for PTR record: says to go to (zone:
Asking for PTR record: [] says to go to (zone:
Asking for PTR record:  Reports [from]

Answer: PTR record: [TTL 86400s] [A=]

So okay there are a few problems... But the big thing is I was able to get a reply from


acesover2000Author Commented:
thanks for the info on the black list that is something I neglected to check.. However  I think you got a little side tracked.. My mail server is performing it's SMTP/POP/EXCHANGE duties properly it's just webmail that's down.  

BTW for some reason many cheaper ISP's  (DSL/Sat/Cable) -- you can't tracert to the IP
acesover2000Author Commented:
well marakush  I'll give you the points because you were the only one to answer and basically made me feel smart by doing everything (almost) I did to troubleshoot the problem

My final blockade was not being able to recover our router's password, so I eventually just reset the PW and rebuilt the LAN IP setup.  Oh well.. it works again (but I have no idea why it failed because I couldn't have changed anything in the router in the first place... Damn Satellite internet was an interesting learning experience)

congrats  that's an easy 500.. don't spend them all in one place!


oh BTW the the external IP differing from the GW addy given by our ISP is common practice with Satellite WHICH as I JUST FOUND OUT causes the extremely unfortunate side affect of becoming blacklisted on certain lists

As far as Reverse DNS goes.. most cheapo providers don't allow reverse DNS which is also (synonym of happy).

Corrections Comments?

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.