Company web and Exchange only work internally
Suddenly, the company web cannot be accessed from outside the network and we can only receive emails internally. We can send out emails to external contacts, but cannot receive mail from them.
The companyweb can be accessed from within the network.
Here is our setup.
Microsoft Small Business Server 2003
Our ISP is Time Warner, Road Runner.
Our account is setup as DHCP.
The server has two nic cards, one for broadband is connected to Time Warner modem, the other to the network switch.
The server is using a software from Dynamic DNS that updates their host file with the new IP whenever it is changed. I have verified that it is up to date. I pinged the domain and receive a response from the IP currently assigned.
I have verified that the websites in IIS are running.
Not sure where to start troubleshooting.
The companyweb can be accessed from within the network.
Here is our setup.
Microsoft Small Business Server 2003
Our ISP is Time Warner, Road Runner.
Our account is setup as DHCP.
The server has two nic cards, one for broadband is connected to Time Warner modem, the other to the network switch.
The server is using a software from Dynamic DNS that updates their host file with the new IP whenever it is changed. I have verified that it is up to date. I pinged the domain and receive a response from the IP currently assigned.
I have verified that the websites in IIS are running.
Not sure where to start troubleshooting.
you'll click on "proceed" then "all service ports" or you can select one port individually "user specified custom port probe"
ASKER
I received message connect failed. How do I verify if I used the correct owa address?
are you testing inside your network or out? Inside try this https://servername/exchange outside you'll try https://mail.domain.com/exchange
test your dns by clicking here, post the results.
test your dns by clicking here, post the results.
here are some things you can try
- on the server run iisreset from a command prompt to reset IIS
- run ipconfig /flushdns on the server and workstation you're testing from
- on the workstation run ipconfig /registerdns
- on the server run iisreset from a command prompt to reset IIS
- run ipconfig /flushdns on the server and workstation you're testing from
- on the workstation run ipconfig /registerdns
ASKER
i was testing outside. I ran the test you suggested. Here are some results.
Your MX records that were reported by your nameservers are:
5 garzapena.com 97.77.164.208
[These are all the MX records that I found. If there are some non common MX records at your nameservers you should see them below. ]
Different MX records at nameservers Good. Looks like all your nameservers have the same set of MX records. This tests to see if there are any MX records not reported by all your nameservers and also MX records that have the same hostname but different IPs
MX name validity Good. I did not detect any invalid hostnames for your MX records.
MX IPs are public OK. All of your MX records appear to use public IPs.
MX CNAME Check OK. No problems here.
MX A request returns CNAME OK. No CNAMEs returned for A records lookups.
MX is not IP OK. All of your MX records are host names.
Number of MX records OK. Looks like you only have one MX record at your nameservers. You should be careful about what you are doing since you have a single point of failure that can lead to mail being lost if the server is down for a long time.
Mismatched MX A OK. I did not detect differing IPs for your MX records.
Duplicate MX A records OK. I have not found duplicate IP(s) for your MX records. This is a good thing.
Reverse MX A records (PTR) Your reverse (PTR) record:
208.164.77.97.in-addr.arpa
You have reverse (PTR) records for all your IPs, that is a good thing.
WWW WWW A Record Your www.garzapena.com A record is:
www.garzapena.com -> garzapena.com -> [ 97.77.164.208 ]
[Looks like you have CNAME's]
IPs are public OK. All of your WWW IPs appear to be public IPs.
WWW CNAME OK. You do have a CNAME record for www.garzapena.com.Your CNAME entry also returns the A record for the CNAME entry, which is good.
Your MX records that were reported by your nameservers are:
5 garzapena.com 97.77.164.208
[These are all the MX records that I found. If there are some non common MX records at your nameservers you should see them below. ]
Different MX records at nameservers Good. Looks like all your nameservers have the same set of MX records. This tests to see if there are any MX records not reported by all your nameservers and also MX records that have the same hostname but different IPs
MX name validity Good. I did not detect any invalid hostnames for your MX records.
MX IPs are public OK. All of your MX records appear to use public IPs.
MX CNAME Check OK. No problems here.
MX A request returns CNAME OK. No CNAMEs returned for A records lookups.
MX is not IP OK. All of your MX records are host names.
Number of MX records OK. Looks like you only have one MX record at your nameservers. You should be careful about what you are doing since you have a single point of failure that can lead to mail being lost if the server is down for a long time.
Mismatched MX A OK. I did not detect differing IPs for your MX records.
Duplicate MX A records OK. I have not found duplicate IP(s) for your MX records. This is a good thing.
Reverse MX A records (PTR) Your reverse (PTR) record:
208.164.77.97.in-addr.arpa
You have reverse (PTR) records for all your IPs, that is a good thing.
WWW WWW A Record Your www.garzapena.com A record is:
www.garzapena.com -> garzapena.com -> [ 97.77.164.208 ]
[Looks like you have CNAME's]
IPs are public OK. All of your WWW IPs appear to be public IPs.
WWW CNAME OK. You do have a CNAME record for www.garzapena.com.Your CNAME entry also returns the A record for the CNAME entry, which is good.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The problem was with Time Warners modem. Somehow the settings reverted to original installation. The firewall and nat was enabled. I had them set it up as bridged and all was back to normal.
open a command prompt and type:
telnet mail.domain.com 25 (use your OWA address) and see if you get a response.