RE: DCOM patch + Exchange

From: Lee Evans (lee_at_vital.co.uk)
Date: 08/19/03

  • Next message: dacruz_at_star-1.com: "RE: DCOM patch + Exchange" 
    To: <dacruz@star-1.com>, <wolf31o2@charter.net>
Date: Tue, 19 Aug 2003 21:50:07 +0100

    }> We have the same issue. Our Exchange server is configured
    }to Dial out
    }> an pick up mail every half an hour. It still dials out but can no
    }> longer retrieve E-mail and External users cannot even
    }initiate a telnet
    }> session on port 25 to the server

    Steven - I think these are likely to be different issues. Other people
    are reporting a problem with users connecting to the exchange services,
    which uses port 135 during the connection between exchange and the
    client machine. Your problems with the exchange server itself unable to
    connect to remote services to collect mail (either SMTP or POP I would
    assume) and with incoming SMTP connections are not likely related,
    certainly not if the issue is indeed upstream ACLS on port 135. Do your
    event logs not give a clue as to the problem when it tries to collect
    mail?

    >, am having the same
    > problem since some genius at my isp decided to fight the worm
    > by blocking the port enterprise wide

    Good for them - there is no reason you should have port 135 open to
    external access. If you can submit one I will be happy to eat my
    proverbial hat. Otherwise I suggest you re-examine your network &
    service topology & stop blaming somebody for taking a reasonable measure
    to help prevent traffic & service disruptions that may well have caused
    you further problems.

    Regards
    Lee 

    -- 
Lee Evans
---------------------------------------------------------------------------
KaVaDo provides the first and only integrated Web application scanner and 
firewall security suite that prevent Web applications attacks, the most 
common form of online exploitation. Download a FREE whitepaper on Security Policy Automation for Web Applications. 
http://www.securityfocus.com/sponsor/KaVaDo_focus-ms_030818 
---------------------------------------------------------------------------
  • Next message: dacruz_at_star-1.com: "RE: DCOM patch + Exchange"

    Relevant Pages

    • Re: Problems with exchange2000
      ... Telnet to Port 25 to Test SMTP Communication ... > I just installed an exchange server, followed all the procedures, ... > higher than the items that i see In microsoft outlook or in OWA ... > but in total items in mailboxes is 9 (i suppose all the tests that i ...
      (microsoft.public.exchange.setup)
    • Re: Exchange + Entourage
      ... But the main problem remains the LDAP related 3268 port. ... And yes I believe if OWA works fine then Entourage ... >> I'd like the Exchange server to be accessible over the Internet, ... >> client is in US and the server is in Europe. ...
      (microsoft.public.exchange.admin)
    • Re: Exchange + Entourage
      ... But the main problem remains the LDAP related 3268 port. ... And yes I believe if OWA works fine then Entourage ... >> I'd like the Exchange server to be accessible over the Internet, ... >> client is in US and the server is in Europe. ...
      (microsoft.public.mac.office.entourage)
    • Re: Exchange + Entourage
      ... But the main problem remains the LDAP related 3268 port. ... And yes I believe if OWA works fine then Entourage ... >> I'd like the Exchange server to be accessible over the Internet, ... >> client is in US and the server is in Europe. ...
      (microsoft.public.exchange.clients)
    • Re: Exchange + Entourage
      ... But the main problem remains the LDAP related 3268 port. ... And yes I believe if OWA works fine then Entourage ... >> I'd like the Exchange server to be accessible over the Internet, ... >> client is in US and the server is in Europe. ...
      (microsoft.public.exchange.connectivity)