Re: 45 days STUCK LIKE CHUCK. DNS / Mx record cant recieve emails

When you have the laptop connected to the SBS external NIC, can you ping
that NIC's IP from the laptop?

Is this SBS Premium, and if so, in ISA, is the "SBS SMTP Server Access Rule"
enabled? If not, r-click the rule and enable it, remembering to also click
the Apply button at the top of the screen.


"Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23V9URYCgGHA.4304@xxxxxxxxxxxxxxxxxxxxxxx
OK, you've pretty much ruled out Exchange configuration. I'm guessing
that if you configured it with the CEICW you don't have some bizarre issue
like Exchange not listening on the Internet NIC.

What I would do at this point is to configure your laptop or a spare
machine with an IP in the same range as your external NIC. Pop out the
cable from the Comcast router and plug it into that machine, and do the
telnet test again. If you get the same 220 response you got from within
the LAN, that'll confirm 100% that the problem is on the Comcast side.


"DKS" <DKS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0200A221-8FBA-42C4-9A3C-A26979B0254A@xxxxxxxxxxxxxxxx
Dave,

220 newhomes2day.com Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830
ready
at Thu, 25 May 2006 12:17:38 -0500

2 Nics Cards internal / externally..

Yes router is connected directly into the internet nic / other nic of
course
is conted to a netgear 16 port FES




"Dave Nickason [SBS MVP]" wrote:

What firewall is running on the server? That should have been
configured by
the CEICW unless it's a 3rd party program.

You can test the connection from within the LAN, but if you have two
NICs,
you'll be testing the internal interface while SMTP is blocked at the
external interface. It's still blocked, by the way. If you ran the
CEICW,
I'm thinking that leaves the NAT device blocking port 25.

To test from within your network, on an XP desktop, open a command
prompt
and type:

telnet <enter>
set localecho <enter>
open x.x.x.x 25 <enter> replacing the x's with your SBS internal IP

You should get a response starting with "220 mail.newhomes2day.com" plus
some other information.

From an external XP machine, you'd do the same thing but substituting
the
public IP. All the telnet stuff is described in detail in the KB I
posted
in the original thread.

Please describe your network configuration. One NIC or two? Do you
have
the LAN side of the Comcast router plugged directly into the Internet
NIC of
your SBS?


"DKS" <DKS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:5D488CF7-4824-4107-A899-86F9502DCA44@xxxxxxxxxxxxxxxx
D,
#1 nat device on the comcast router,#2 re-ran CEICE

test now on dnsreport / logging in to comcast router about nat..

firewall on server how would i test to make sure port 25 is open from
internal network

"Dave Nickason [SBS MVP]" wrote:

Something is blocking connection attempts at your server. Do you
have an
external firewall or NAT device that needs port 25 opened inbound?
If
you're absolutely sure it's not an external device that's blocking
the
connection attempt, re-run the CEICW. For any page not relating to
the
immediate topic, just click the "don't change" option.

This doesn't relate to your internal domain name, which can be
anything.
Exchange is separate from that.

See my previous post on testing your server from an external PC using
telnet. You may not have to do this since you can see what's
happening
right in dnsreport, but that's the actual way one would test smtp
connectivity. But telnet to port 25 is the correct way of
troubleshooting
smtp connectivity.

FYI regarding your DNS, yesterday in the other thread when Cris Hanna
said
he saw one thing, and kj said he saw another, I saw both. First what
Cris
saw, then what kj saw. It looks to be fixed now, but your server is
still
rejecting connection attempts. See the text below, which I'm pasting
in
directly from a dnsreport.com check of newhomes2day.com that I just
ran.

ERROR: I could not complete a connection to any of your mailservers!

newhomes2day.com: The mailserver terminated the connection before the
transaction was complete (state 1). This is not RFC compliant, and
therefore
either due to an error, or it may be the result of a
non-RFC-compliant
mailserver or non-RFC-compliant anti-spam program.








"DKS" <DKS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:01D4E53E-92DB-4A7A-A732-864E3CCF2389@xxxxxxxxxxxxxxxx
We recently switched from a regular t-1 to Comcast cable. It has
been
about
45 days since the switch and we still cant receive email. We can
send
but
not
receive. Stuck need to fix fast.



Check List

. Ports 25 an 110 are open to receive mail on Comcast router
. Firewall is disabled on Comcast router and SBS firewall is up
. Checked Anti-virus ports are open to receive mail
. Ran Internet and Email repair about a dozen times still no change
. I'm running SBS 2003 with exchange
. Checked domain to make sure it was pointed to server
. Reverse DNS is correct / ran http://www.dnsstuff.com/mx correct
mail.newhomes2day.com. MX IN 7200 mail.newhomes2day.com.
[Preference =
10]

*running SBS 2003 exchange Standard
*Have a private Ip address and router address
*mail.sss.com is pointed to private static Ip
*can send email within network with no problems node1-node2


DNS is wacky records are wrong i think any idea's.. need to get
back up
fast..46 1/2 days way to long...










.