Hi John, #1 - failure to ping the IP address usually means that the reverse lookup zone is missing the required entries for that domain. USWest should be able to help you there. #2 - Nslookup to your domain reveals: > set type=mx > webeans.com webeans.com MX preference = 20, mail exchanger = mail.webeans.com webeans.com MX preference = 10, mail exchanger = chili.webeans.com mail.webeans.com internet address = 63.224.44.83 chili.webeans.com internet address = 63.224.44.83 First, there's no gain to creating two MX records for the same IP address, and it may even cause confusion for some SMTP servers that expect to reverse-resolve source IPs to hostnames. Second, I tried to connect to your mail server, but got no response. You can get http://isatools.org/isainfo.zip and run the included script on your ISA server. The resulting file is very useful for troubleshooting ISA issues and sharing your ISA config with those who wish to help you (like us). Jim Harrison MCP(NT4, W2K), A+, Network+, PCG http://isaserver.org/pages/author_index.asp?aut=3 http://isatools.org Read the help / books / articles! ----- Original Message ----- From: "John Bean" <johnbean2000@xxxxxxxxx> To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx> Sent: Sunday, January 12, 2003 19:33 Subject: [isalist] Hello from a newbe and help configuring incoming email http://www.ISAserver.org Hello everyone, My name is John. I'm brand new to this list. On a recent support call to Microsoft help desk an ISA Server technition gave me two pieces of advice: buy Deb and Tom Shinder's Configuring ISA Server 2000 and get on this list. Having now done both I'm hoping to gain a working understanding of how to configure ISA Server. But, I'm just getting started. ** Aren't we all... ;-) I have a small test network set up very much like the one illustrated in Dr. Shinder's article "Designing an ISA Server Solution on a Simple Network Part 1: Configuring The Network Infrastructure." My network configuration has both an external domain name (webeans.com) and an internal domain name (webeans.lcl). I have confirmed that both the external and internal network domains comply with the model presented in this article. Using nslookup I am able to resolve all internal host names as well as the alias www. I am also able to resolve the IP addresses of all internal hosts via nslookup. (The LAT is configured with the IP address range of 192.168.1.0 through 192.168.1.15.) Using nslookup on my ISA server I am able to resolve the names www.webeans.com and mail.webeans.com to their network IP, but when I enter the IP address, nslookup *fails* to resolve to the names and instead delivers the following error message: "sttlpop1.sttl.uswest.net can't find 63.224.44.83". (sttlpop1.sttl.uswest.net is the dns server for my external network.) Currently I have my ISA Server configured according to Dr. Shinder's tutorial "Getting Started with ISA Server". I am please to say that client access to the internet worked just as the tutorial predicted. My next step was to successfully publish my web site by following the steps described in Dr. Shinder's article "A Web Site Using ISA Server Part 1: Preparing to Publish Your Site." Buoyed by the success of my first two steps I immediately took on the challange of publishing my mail server. All I needed was to be able to send and receive mail and enable OWA. Using Dr. Shinder's article "Publishing a Mail Server With ISA Server" I was successful in sending messages that originate from the internal network to my email addresse on yahoo.com. *BUT* that's as far as I have been able to get! I am quite unable to send an email message from yahoo.com to my internal email address. (A further note of explanation here: I have Exchange 2000 configured on the internal network where my email suffix is webeans.lcl. However I have added johnb@xxxxxxxxxxx to my internal mailbox and have internally sent to that address successfully.) The destination email address I am using to from yahoo.com is johnb@xxxxxxxxxxxx The error message on yahoo when the message bounces is: Message from yahoo.com. Unable to deliver message to the following address(es). <johnb@xxxxxxxxxxx>: 63.224.44.83 does not like recipient. Remote host said: 550 5.7.1 Unable to relay for johnb@xxxxxxxxxxx Giving up on 63.224.44.83. This error message appears very quickly after I attempt to send. I am also unable to access my email using OWA, but that is another incident that should probably wait until my inbound email can be succesfully configured. Suffice it to say that I can get the password validation screen up and correctly filled out, but it falls to actually present the OWA email page. Any help you can give me as to why I can't receive email is greatly appreciated. Thanks, John Bean ------------------------------------------------------ List Archives: http://www.webelists.com/cgi/lyris.pl?enter=isalist ISA Server Newsletter: http://www.isaserver.org/pages/newsletter.asp ISA Server FAQ: http://www.isaserver.org/pages/larticle.asp?type=FAQ ------------------------------------------------------ Exchange Server Resource Site: http://www.msexchange.org/ Windows Security Resource Site: http://www.windowsecurity.com/ Windows 2000/NT Fax Solutions: http://www.ntfaxfaq.com ------------------------------------------------------ You are currently subscribed to this ISAserver.org Discussion List as: jim@xxxxxxxxxxxx To unsubscribe send a blank email to $subst('Email.Unsub')