Re: Can't connect to Mailserver

Tech-Archive recommends: Fix windows errors by optimizing your registry

I'll do that, thanks.
Didn't know I could call them. Have been using email and their response is
pretty quick - and good.

Mike
"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:uIfd6dt7GHA.3452@xxxxxxxxxxxxxxxxxxxxxxx
In news:OQt$WXt7GHA.728@xxxxxxxxxxxxxxxxxxxx,
Mike Webb <Mike_Webb@xxxxxxxxxxxxxxxxx> typed:
Sorry, I didn't try to PING mail.whoopingcrane.org. I DID go to
dnsreport.com and dnsstuff.com and ran some tests. They detected the
IP and showed me it came from the ISP. The Mail Test for
mail.whoopingcrane.org failed yesterday; it couldn't "find" it, but
did find the backup MX servers (mx2.mailhop.org. from dyndns.org).
Just ran a Mail Test as I type this and it was able to detect and
connect to mail.whoopingcrane.org.

Yep.


I wonder if it might have been a DNS issue. The ISP changed our IP
early yesterday (or was it Wednesday?), so maybe it took awhile for
the change to propagate around the DNS servers.

That doesn't sound likely. It would apply if you'd changed something in
your domain's zone files on the dyndns server (& hadn't first lowered the
TTL), but a simple change in IP is instantaneous. I think the client
hadn't updated the dyndns server. Next time this happens (if it does),
don't change anything - look at the dyndns update client and compare what
it has in it, to what you see at www.whatismyip.com (or whatever you like
for that test).....and log into your dyndns.com account and see what they
have listed there.

You can also call their tech support, you know - you have a paid account
with them. They're quite good, in my experience.

Mike

"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:%23Y4ZOOt7GHA.4996@xxxxxxxxxxxxxxxxxxxxxxx
In news:utXdtjs7GHA.4708@xxxxxxxxxxxxxxxxxxxx,
Mike Webb <Mike_Webb@xxxxxxxxxxxxxxxxx> typed:
Just got in to work and found a bunch of emails when I opened
Outlook. It seems they started flowing in about 7 PM CDT yesterday.
Haven't had a chance yet to dig into the server and find out why.
I'm glad it's working, but it worries me not knowing why it's back
up with no changes by me after 4 PM CDT.

I'm wondering whether your update client hadn't done its work
properly. Did you compare the IP reported by www.whatismyip.com to
what you got when you tried to ping mail.whoopingcrane.org, when
this was *not* working?

Mike

"Maxibo" <totallyanon@xxxxxxxxx> wrote in message
news:O$GAsXp7GHA.2364@xxxxxxxxxxxxxxxxxxxxxxx
Hi Mike... are things working now ?

Email got returned at 01.53 so indicates email collection and
telnet IP on port 25 responds with your exchange server.




"Maxibo" <totallyanon@xxxxxxxxx> wrote in message
news:%23jYxmMk7GHA.3396@xxxxxxxxxxxxxxxxxxxxxxx
Are you sure your ports are open ?

1. When I telnet to port 25 I should get a response from your
exchange server (assuming not pop3)... this fails

2. Scanned your Ip... (sorry but trying to help...lol) it doesn't
show any ports open, not even 3389, how did previous help TS
in...lol 3. I sent a test email to your ip to generate an NDR
from your exchange (confirm IP of server) an hour ago, no
response as yet.. Goto www.grc.com and choose shields up and test
individual ports,
25, 443, 444, 4125 and 3389. Assuming opened ports for RWW, SMTP
and TS. "Mike Webb" <Mike_Webb@xxxxxxxxxxxxxxxxx> wrote in message
news:%23Pu10hj7GHA.2288@xxxxxxxxxxxxxxxxxxxxxxx
Yes. Those ports and more forwarded to 192.168.1.10, and all
Enabled. As further info, here are the settings from my Status
page: WAN
Connection Type Dynamic IP
WAN IP 70.41.130.208
Subnet Mask 255.255.252.0
Gateway 70.41.128.1
DNS 63.170.76.3
Secondary DNS 63.170.76.2

LAN
IP Address 192.168.1.1
Subnet Mask 255.255.255.0
DHCP Server Disabled
Firewall Enabled



"Maxibo" <totallyanon@xxxxxxxxx> wrote in message
news:u2VNvXj7GHA.4276@xxxxxxxxxxxxxxxxxxxxxxx
Hi Mike

Are the correct ports open in the router ?

25
3389
443
444
4125


"Mike Webb" <Mike_Webb@xxxxxxxxxxxxxxxxx> wrote in message
news:e1xTf1i7GHA.4304@xxxxxxxxxxxxxxxxxxxxxxx
I should add some more info to aid you (or anyone) in figuring
this out).

External NIC is at 192.168.1.10; router is at 192.168.1.1,
internal NIC is at 192.168.16.2.
External NIC is connected to the router, router to the
satellite modem, internal NIC to a switch/hub.
SMTP Virtual Server IP set to "All Unassigned". Access
Authentication set to all 3 main checkboxes checked. Relay
restrictions allowed only for 192.168.16.2, 127.0.0.1, and
192.168.1.10. FQDN set to whoopingcrane.org. Smart Host to
outbound.mailhop.org. (Got this service from dyndns.org so
emails won't look like it comes from a spammer.) Outbouind
security set to Anonymous. SMTP Connector forwards all email
through outbound.mailhop.org,
wqith Default SMTP Virtual Server as the local bridgehead. On
the Advanced tab > Outbound Security, I have it set to Basic
and have my login and passwword for dyndns.org in the user
section. TLS is also checked. (All per the instructions at
dyndns.org.) In Global Settings > Message Delivery > General >
Add, the IP
listed is 192.168.16.2

Mike

"Lanwench [MVP - Exchange]"
<lanwench@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
wrote in message
news:%23c60Yni7GHA.3280@xxxxxxxxxxxxxxxxxxxxxxx
In news:uOiDrVi7GHA.2384@xxxxxxxxxxxxxxxxxxxx,
Mike Webb <Mike_Webb@xxxxxxxxxxxxxxxxx> typed:
Running SBS 2003 Premium, Exchange, ISA 2004, WSUS, 2 NIC's
and a router. DDNS provided by dyndns.org. Dynamic IP
provided by ISP. =============================
My ISP changed IP's on us - again - and now we aren't getting
inbound
email. I ran a test on dnsreport.com and got the following:

mail.whoopingcrane.org. - xx.xx.xxx.xxx [Could not
connect: Could not receive data: Winsock error #10054.]
mx2.mailhop.org. - xx.xxx.xx.xx [Successful connect: Got a
good response [250 Accepted]] (took 3.485 seconds)
mx2.mailhop.org. - xxx.xx.xxx.xx [Successful connect: Got
a good response [250 Accepted]] (took 3.734 seconds)
mx2.mailhop.org. - xxx.xx.xxx.xx [Successful connect: Got
a good response [250 Accepted]] (took 7.922 seconds)
mx2.mailhop.org. - xxx.xx.xxx.xx [Successful connect: Got
a good response [250 Accepted]] (took 3.234 seconds)
mx2.mailhop.org. - xxx.xx.xxx.xx [Successful connect: Got
a good response [250 Accepted]] (took 7.532 seconds)
mx2.mailhop.org. - xx.xxx.xx.xx [Successful connect: Got a
good response [250 Accepted]] (took 11.93 seconds)I've run
CEICW a couple of times - no change. Verified settings in
ESM, all good. What am I
missing?

This has nothing to do with your internal network - don't
rerun the CEICW for something like this. What did you change
therein? You do have a router, which should be handling the
public side of things.... How is mail.whoopingcrane.org being
updated
with the correct
public IP? I can see that Dyndns is authoritative for your
whoopingcrane.org domain, but how are you updating it - the
dyndns client? Another client? Don't do this in your
router/firewall's 'dynamic DNS' settings - use client software
that runs as a Windows service on your SBS box.

Currently, mail.whoopingcrane.org is pointing at
70.41.130.208, and your Exchange server isn't answering
telnet requests on port 25. Something is, but it isn't Exchange..
If that isn't
your current public IP, as listed at www.whatismyip.com,
that's the problem right there - it isn't being updated
properly.





.

Relevant Pages

  • Re: Cant connect to Mailserver
    ... domain's zone files on the dyndns server, ... When I telnet to port 25 I should get a response from your ... Are the correct ports open in the router? ...
    (microsoft.public.windows.server.sbs)
  • Re: Cant connect to Mailserver
    ... chance yet to dig into the server and find out why. ... When I telnet to port 25 I should get a response from your exchange ... Are the correct ports open in the router? ...
    (microsoft.public.windows.server.sbs)
  • Re: Cant connect to Mailserver
    ... port 25 responds with your exchange server. ... When I telnet to port 25 I should get a response from your exchange ...
    (microsoft.public.windows.server.sbs)
  • Re: Cant connect to Mailserver
    ... domain's zone files on the dyndns server, ... I'm presuming it's a simple port forward from WAN to LAN on ... When I telnet to port 25 I should get a response from your ... Are the correct ports open in the router? ...
    (microsoft.public.windows.server.sbs)
  • Re: Cant connect to Mailserver
    ... domain's zone files on the dyndns server, ... presuming it's a simple port forward from WAN to LAN on port ... When I telnet to port 25 I should get a response from your ... Are the correct ports open in the router? ...
    (microsoft.public.windows.server.sbs)