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



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...


.



Relevant Pages

  • RE: VBscript Error on SBS2k3
    ... DHCP Server turned of SonicWALL with VPN Pass through request for IP to ... the problem should be caused by the 4125 port. ... > | Accessories and Communications and Remote Desktop Connection? ... > | 2.In Internet Explorer on the workstation you are connecting from, ...
    (microsoft.public.windows.server.sbs)
  • Re: More on Remote Desktop
    ... Chances are good, though, that he's already got VPN capabilities on his ... firewall to do it for $100. ... > server at home...or purchase additional/new hardware... ... >> my firewall makes the PPPoE connection to my ADSL ISP. ...
    (microsoft.public.windowsxp.network_web)
  • Re: interfaces lo:1 lo:2 lo:3? (for remote ssh tunnels)
    ... That's the problem tunneling (port forwarding) solves. ... >>can't get past the client firewall. ... > I don't understand why the server would be making the ... server initiates another connection to the client -- in this ...
    (Debian-User)
  • Re: More on Remote Desktop
    ... on your firewall to the world, you will almost certainly get hacked. ... between your clients and server on your own LAN. ... your laptop into that LAN server has got to be making these two public IP's ... PPPoE connection to my ADSL ISP. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Can not access Web and FTP sites from Internet
    ... your IP Configuration on the Server is correctly. ... Connecting To 12.208.215.87...Could not open connection to the host, ... 1> From the result, we can see the telnet failed, which means the router ... does not forward Port 443 to SBS Server. ...
    (microsoft.public.windows.server.sbs)

Loading