I have seen this many times. The following is a list of potential culprits:
OUTBOUND SMTP PROBLEM
1 - Your ISP is blocking outbound SMTP. Many ISP's block outbound SMTP unless you use their SMTP server to send. Contact the ISP and determine what the outbound SMTP IP address should be. If this is the case, you will have to configure the SMTP Virtual Server or the SMTP Connector (if it exists) to use this IP address as the smarthost.
2 - You do not have a reverse PTR record for the IP address that Exchange will be delivering on. To resolve this, from the Exchange Server, go to:
http://www.ipchicken.com
Once you have determined your external IP address, go to:
http://www.dnsstuff.com
scroll towards the bottom of the page and enter the IP address in the Reverse DNS lookup. If there is no reverse DNS lookup for the IP address, most ISP's will simply block the SMTP connection. To resolve this, you will have to contact your ISP and ask them to create a Reverse PTR record.
3 - As previously mentioned, your router and/or firewall is configured to not allow outbound SMTP (not likely).
The easiest way to test SMTP functionality on the Exchange server is to open up a command prompt on the server and type in the following:
telnet localhost 25
If you receive a response, then, SMTP is functioning properly on the server. If you do not, the SMTP service is not working. This could be because the service is disabled or because some internal process (like a software based firewall or antivirus software) is blocking the SMTP process.
Check the router and ensure that port 25 is open inbound and outbound.
Another thing to keep in mind is that the Microsoft Exchange Server (by default) log SMTP errors. To do so, turn on SMTP logging on the SMTP Virtual Server and then review the log files.
INBOUND SMTP PROBLEM
Finally, your inbound problem is most likely related to missing MX records for the domain in question. To check you MX records, go to:
http://www.dnsstuff.com
When there, scroll towards the bottom and enter the domain name (yourdomain.com) in the DNS Lookup test, change the record type to MX, then click Lookup. Are the MX records there? You should have a A record and MX record for the domain.
Good luck!
2007-05-04 03:24:46
·
answer #1
·
answered by mcse2nv 2
·
0⤊
0⤋
You have several potential issues.
First, you may not have run the wizard correctly. The fix is to run the wizard again, paying careful attention, and making sure you've done everything right.
Second, you may have a firewall issue. The wizard will configure your windows firewall just fine, but it will not configure any third-party firewalls. If you have some type of third party antivirus/security suite, make sure it's allowing the proper ports (25 and 110 for e-mail).
Third, you may have a router issue. Your router must be configured to allow traffic on these same ports. Additionally, the ports on the router must be forwarded to the IP address of your server. Make sure the port forwarding feature on your router is pointing ports 25 and 110 to your server's internal IP address.
Fourth, you may not have put your MX records into the internet's DNS records. You pretty much have to have a static public IP address to run Exchange externally. Make sure your internet DNS host has an MX record for your domain pointing to your public IP address. (check by going to www.dnsstuff.com and search for the MX records for your domain. You should find your IP address listed as the lowest (or only) MX record. If it isn't, you've got to make that MX record public.
2007-05-02 08:40:16
·
answer #2
·
answered by antirion 5
·
0⤊
0⤋
It kind of sounds like you haven't run the "Configure E-Mail and Internet Connection Wizard" properly or at all. You may also have a firewall that needs to be configured to allow that traffic in/out. Are you using the Premium version with ISA? I strongly encourage you to use the built in Wizards to do all your administrative setup and tasks. The official MS Administrator Guide for SBS 2003 R2 is a terrific resource for basic SBS installation and configuration.
2007-05-01 20:25:24
·
answer #3
·
answered by veijones 1
·
0⤊
0⤋
Is your router setup to pass the ports to the outside world to and from the server.
Most of the time when I see this the internet router is not set to pass all the ports needed to the server. With SBS this would include ports
21ftp,25 smtp,53dns,80http,110pop,443ssl at the least.
It does exactly what you describe.
2007-05-01 23:30:57
·
answer #4
·
answered by Tracy L 7
·
0⤊
0⤋
It's commonly used as character names in video games. I've had a Jezebel or two on WoW or SWTOR :P
2016-03-18 22:20:17
·
answer #5
·
answered by Anonymous
·
0⤊
0⤋
is ur internet working ?
check the internet connection, DNS servers and also is ur domain name still valid or its expired.
more info wanted abt this ( what is the error ur getting )
2007-05-01 19:59:06
·
answer #6
·
answered by Ganesh 5
·
0⤊
0⤋