IIS SMTP server not sending. Mail stuck in Queue

From: hfard (hfard.17q121_at_mail.webservertalk.com)
Date: 06/12/04

  • Next message: Jeff Cochran: "Re: IIS SMTP server not sending. Mail stuck in Queue"
    Date: Fri, 11 Jun 2004 22:41:07 -0500
    
    

    I just setup a W2K server with these setup, Domain controller, AD,
    MS-DNS, IIS 5, SMTP (IIS, no other email server software), SP4,
    connected to the Internet via a second NIC on DSL and WinPoet as
    Internet connection software (static IP). Since it will be an internal
    server, I have the last part on the domain as ".local". Also I am not
    using its DNS for external use, so under
    DNS/server/Forward-Lookup-Zones/ I have removed the "." entry to allow
    Forwarder, and setup my ISP's DNS IPs on the Forwarder tab. For all
    NICs, I have setup machine's internal IP (10.10.1.1) as DNS address,
    and not any of ISP's DNS, assuming it will use the forwarder
    information to find external DNS.

    I am trying to use the SMTP component of IIS5 for outgoing messages
    only (no Smart Host). For the "Default SMTP Server", I have allowed
    Relay from all my NICs IPs. I have not setup any client yet, but when
    from the server itself I Telnet to Port 25 to Test SMTP Communication
    (MS KnowledgeBase (Q153119) my messages get stuck in the Queue folder.
    Also, I get the following message in the System Event Log: "Event-ID:
    4000 from smtpsvc, Message delivery to the remote domain 'yahoo.com'
    failed for the following reason: The remote server did not respond to a
    connection attempt".

    DSL is functional because browser works fine. I also used Nslookup to
    see if that works. The interesting part is that if I use
    non-interactive nslookup (C:>nslookup -q=MX yahoo.com), it uses my ISP
    DNS and reports tons of Yahoo's MX records. But when I use interactive
    nslookup, and at nslookup prompt type "ls -t MX yahoo.com", it does not
    work and I get the following:
    [ns3.mindspring.com]
    *** Can't list domain yahoo.com: BAD ERROR VALUE

    I guess if I can get this interactive nslookup to work, it might solve
    the problem of stuck outgoing messages. I have a feeling that I am
    missing a configuration feature that causes the SMTP not to see the
    outside world, but I don't know what.

    Any help is greatly appreciated.

    --
    hfard
    ------------------------------------------------------------------------
    Posted via http://www.webservertalk.com
    ------------------------------------------------------------------------
    View this thread: http://www.webservertalk.com/message259747.html
     
    

  • Next message: Jeff Cochran: "Re: IIS SMTP server not sending. Mail stuck in Queue"

    Relevant Pages

    • Re: Urgent! New router and big disaster
      ... The SBS DNS server, running on ... its IP it means that your problem is now DNS. ... forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
      (microsoft.public.windows.server.sbs)
    • Re: How to configure for Two different IP subnets
      ... Active Directory will go haywire in a setup like that. ... AD integrates with the local DNS, so you cannot use the DNS at your ISP ... With Server 2003 Standard ... for its internal interface (ie the VPN endpoint). ...
      (microsoft.public.windows.server.networking)
    • Re: Cannot connect to RWW from home PC
      ... DNS stuff says your mail server is responding with reply that is not MS ... When we setup this new SBS2003 setup we installed without ISA as it does ... not seeing any problems anywhere regards internet or email - we also run ...
      (microsoft.public.windows.server.sbs)
    • Re: Non-domain connection problem
      ... For some reason the DNS is persistent. ... connect new PC to the internet from the non-domain network: ... In server 2000 gpoedit.msc showed them but in SBS it is different. ...
      (microsoft.public.windows.server.sbs)
    • Re: resolve incorrect IP from RRA server.
      ... dynamic address, 10.5.101.123 from DHCP server. ... This is because the addtional DNS records that get registered cause major problems with AD functionality, especially the additional IPs registered by RRAS. ... However, if you choose to keep RRAS on the DC, then you have to force DNS to only register the internal static interface, and no others. ... If it is the internet gateway, it is recommended to purchase an inexpensive, or cable/DLS router, or even better, a Cisco or similar firewall to perform the task, which if it is compromised by an internet attacker remotely, can further compromise the rest of the internal network. ...
      (microsoft.public.windows.server.dns)