Re: Exchange incoming email issue



If you get a blank screen when you telnet on port 25 something is not right.
The response should look something like this:

220 domain.com Microsoft ESMTP MAIL Service, Version: 6.0.3790.1830 ready at
S
un, 30 Sep 2007 14:46:16 +0200

Your ISP is probably routing port 25 to some other system.
To work around this sign up with www.rollernet.us or http://www.dyndns.com.
They can route your mail to another port.
This will need an MX-record change.....



Scott" <someone@xxxxxxxxxxxxx> wrote in message
news:OmM42U0AIHA.4584@xxxxxxxxxxxxxxxxxxxxxxx
Hi all,
Got a bit of an urgent problem here that I'm hoping someone can help
with. I built an SBS 2003 R2 server a couple of weeks ago, mainly so my
client could use Exchange.

I configured the usual settings (I've done at least ten of these now),
tested tht it wasn't a relay etc. and added port forward rules on their
router/firewall for SMTP and OWA (80 and 443)

I tested the receipt of Email using telnet from an external location (my
office) which worked fine. Feeling fairly confident, I migrated their
.pst's into the mail store, and contacted the ISP that hosts their DNS and
asked them to update the MX record.

That was a bit of a nightmare(and a whole other stroy), but after a week
(!!!) of mucking around with them, they finally got an MX and A record
right for my client.

I then sent several test emails from several domains to the Exchange
server, without issue.

A couple of days later, I got a call from them saying they haven't been
receiving email. They can send and reveive email internally, and they can
send emails out to external locations, but they can't receive from
external sources.

I straight away did a telnet test on port 25, which goes to a blank DOS
screen for a minute, then returns to a prompt with no further info.

Since then, I have:
Checked the event logs, and 'cleaned up' any further error events that
were occuring (Such as 2014 and 2016, which looked to be related, but
according to MS can be safely ignored if they only occur at startup.

It now looks to me that port 25 is being blocked 'somewhere'.

If I change the port the SMTP virtual server uses from 25 to anything
else, I can then telnet into the Exchange server from my office (ie.
externally) no problems.

I have re-created the firewalls rules, replaced the firewall/router with a
different model, removed any extraneous software from the server that
might ahve been causing issue (eg spybot was on there - installed by
someone else) but no joy.

The server has Norton Corp AV, but this doesn't have any firewall type
component that I'm aware of. (And I disabled it to test the theory
anyway.)

I reckon it might be the ISP that is supplying the ADSL connection to my
client that is blocking port 25, but I rang them and they say 'no'.

I'm at my wits end with this one, and I am going to have to pull the
server out and go back to pop mailboxes at the ISP if I can't figure it
out ASAP. Any help or ideas would be hugely appreciated.

Cheers!
Scott



.



Relevant Pages

  • Re: SMTP Server for outgoing only behind a home router
    ... They cliam to ONLY block port 80 to keep me from ... you will get a 220 greeting line from the remote SMTP server: ... So AOL.COM methods stops legitimate roaming users from using ESMTP AUTH to ... So look to see of your ISP supports ESMTP AUTH for dynamic IP users and/or ...
    (microsoft.public.inetserver.iis.smtp_nntp)
  • Re: IIS and SBS 2003
    ... I have a new sbs2003 install and if I telnet to localhost ... port 80, and type hhh and hit enter it returns a HTTP/1.1 400 Bad ... "broken" sbs server, it connects but then dumps me. ... If I http to localhost, companyweb or anything I get Cannot Find ...
    (microsoft.public.windows.server.sbs)
  • Re: Suggestion for a lexical (login mode via TCPIP)
    ... Not sure of it is the right one to modify or to add another one, but it would be useful to be able to get information on whether the user us coming in via FTP, TELNET, etc. ... This would also allow a LOGIN.COM to check if someone is coming in through a secure/SSL port for instance. ... For the HP SSH server, it seems to be undefined. ... forget about the possibility of virtual terminals. ...
    (comp.os.vms)
  • Re: RDP access to SBS 2003 - HELP please
    ... Might I add that 'out of the box', when I first got the server it worked ... of it to the telnet prompt and quit. ... Try the remote desktop connection to see if it works. ... the effect that it can't connect to xxx.xxx.xxx.xxx port 23. ...
    (microsoft.public.windows.server.sbs)
  • Re: IP Blocker in SBS2003 exchange
    ... > What I was trying to explain in the telnet section was that I realise ... > the server is listening for connections on ports 110 and 25. ... > but he can connect to port 110. ... > well as another wireless broadband connection. ...
    (microsoft.public.windows.server.sbs)