Re: Exchange Server 2003 Outgoing SMTP Queue

From: ADSC Support (support_at_adsceng.com)
Date: 11/12/04 

Date: Thu, 11 Nov 2004 17:15:03 -0800

>-----Original Message-----
>Hi,
>
>It sounds like you've covered things pretty well and I
hate to give a "is
>the monitor plugged in" type response, but I'd perform
that 'telnet to port
>25' test from the Exchange server itself instead of from
the firewall. It
>sounds as if the firewall may be preventing the
communication outside?
>
>The error you're seeing is received when the remote
server isn't able to be
>reached at all. If it's able to contact that server and
then the connection
>times out or is dropped for some reason, you'll see an
error message of,
>"connection dropped by remote host." Of course, a DNS
resolution problem
>would result in an error message of, "Cannot bind to
server in DNS," or
>somesuch.
>
>Does increased MSExchangeTransport logging reveal
anything telling if you
>crank it up a bit? (properties of the server in
Exchange System Manager)
>
>-Josh
>
>
>"ADSC Support" <support@adsceng.com> wrote in message
>news:185701c4c742$81d16810$a501280a@phx.gbl...
>> Problem with new SBS2003 Installation - Exchange Server
>> 2003 Outgoing SMTP Queue
>>
>> Description of Problem:
>>
>> Outgoing SMTP Internet Email is stuck in queue with
>> status of retry - NDR after time out - message "the
>> remote server did not respond to a connection attempt"
>> Incoming SMTP Internet Email received normally
>> Using DNS for mail delivery - if forward to host -
queue
>> clears
>> DNS name resolution from the command prompt or IE to
>> external domains resolve with no problem
>>
>> A query from the firewall produces the following
results-
>> the same is true from a filtered domain subnet external
>> to the firewall to the live IP address at the router.
>>
>> firewall:~# telnet 192.168.16.2 25
>> Trying 192.168.16.2...
>> Connected to 192.168.16.2.
>> Escape character is '^]'.
>> 220 Domain.com Microsoft ESMTP MAIL Service, Version:
>> 6.0.3790.211 ready at Tue, 9 Nov 2004 19:17:04 -0800
>> EHLO
>> 250-Domain.com Hello [192.168.16.1]
>> 250-TURN
>> 250-SIZE
>> 250-ETRN
>> 250-PIPELINING
>> 250-DSN
>> 250-ENHANCEDSTATUSCODES
>> 250-8bitmime
>> 250-BINARYMIME
>> 250-CHUNKING
>> 250-VRFY
>> 250-X-EXPS GSSAPI NTLM LOGIN
>> 250-X-EXPS=LOGIN
>> 250-AUTH GSSAPI NTLM LOGIN
>> 250-AUTH=LOGIN
>> 250-X-LINK2STATE
>> 250-XEXCH50
>> 250 OK
>>
>> - the only difference with this installation and the
last
>> 12 since 06/2004 is the application of Current Hot
Fixes
>> and Exchange 2003 SP1 plus Hot Fixes prior to
installation
>>
>> All Installation procedures are documented and followed
>> consistently with no exceptions - no errors during
>> installation documented
>>
>> I am under the gun on this one, since the problem was
>> not discovered until the system went live. I will
>> appreciate any help. I have compared the settings of
the
>> other installations with this one and the only
difference
>> I find is not with the configuration, but the version
of
>> files. I have looked at Exch 2000 KB with no luck.
>>
>>
>
>
>.
>Thank you for your response. Since I submitted this
message I have contacted the ISP and convinced them to
ley me relay to their host until I get this problem
fixed. So the mail cleared the queue and was delivered
normally. The client doesn't know the difference at this
point, but of course I still need to fix it in order to
maintain "best practice" configurations.
I followed your directions and performed the telnet from
the server with the same response. I turned on maximum
logging for the Transport and reconfigured for DNS use.
I will monitor it and see what comes up. I knew Exchange
5.5 fairly well and I find that navigating the multitude
of features in 2003 a little difficult, but I've got my
books out and like with all problems, am learning more
than I might desire about the internal workings of the
software.
Thanks again for your help.

Relevant Pages

  • Re: Trend Micro Client Server for SMB
    ... scope options that the SBS DHCP server has configured by default, ... Stateful firewall connected to the internet connection. ... I just did a basic installation. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cant connect to NASA sites.
    ... Firefox can't find the server at hubblesite.org. ... Logic tells me it's either the HOSTS file or the firewall. ... Problem predates the installation of this file, ...
    (microsoft.public.windowsxp.general)
  • Re: MX failure - going to A record
    ... My firewall may also be responsible. ... Here's the response from Earthlink. ... the mail server which attempted to deliver mail to the earthlink.net e-mail ...
    (comp.mail.sendmail)
  • Re: MX failure - going to A record
    ... My firewall may also be responsible. ... Here's the response from Earthlink. ... the mail server which attempted to deliver mail to the earthlink.net e-mail ...
    (comp.mail.sendmail)
  • Re: Trend Micro Client Server for SMB
    ... Stateful firewall connected to the internet connection. ... DNS is set up on the SBS2003 server. ... > So far as Trend CSM is concerned - the Trend firewall can cause some issues. ... >>I just recently completed installation of Trend Micro Client Server for SMB ...
    (microsoft.public.windows.server.sbs)