RE: DCOM patch + Exchange

From: Chris Gianelloni (wolf31o2_at_charter.net)
Date: 08/19/03

  • Next message: Grewal, Jaideep: "RE: DCOM patch + Exchange" 
    To: dacruz@star-1.com
Date: 19 Aug 2003 15:12:08 -0400

    On Tue, 2003-08-19 at 13:28, dacruz@star-1.com wrote:
    > Exchange needs The RPC protocol to communicate which happens to be port 135
    > most likely your isp desided to block communications thru that port and that
    > is why exchange does not work for external users except vpn, am having the
    > same problem since some genius at my isp decided to fight the worm by
    > blocking the port enterprise wide and now guess who the virus is to me? My
    > isp they are causing me more problems than the virus itself , am
    > patch/firewalled/virus protected all the tools to combat the frigging worm,
    > but not my isp wants to take care of it for me really? By blocking the port?
    > Great!! Am so happy now for your info the isp am having the problem with is
    > SBC or charter communications in Madison and Chicago, my other isp's did not
    > think that way and am glad

    Exchange works quite well without access to port 135, thank you. In
    fact, having 135 exposed to the Internet is simply a bad idea to begin
    with. I am sure that is not the problem since I have *never* had 135
    exposed and never will.

  • Next message: Grewal, Jaideep: "RE: DCOM patch + Exchange"

    Relevant Pages

    • Re: Local domain name not resolving for SMTP
      ... Exchange uses port 25 by default but Outlook can use whatever port the ISP ... The old server is still in place for forwarding but does not have a DNS ...
      (microsoft.public.windows.server.sbs)
    • RE: DCOM patch + Exchange
      ... Exchange needs The RPC protocol to communicate which happens to be port 135 ... same problem since some genius at my isp decided to fight the worm by ... SBC or charter communications in Madison and Chicago, ...
      (Focus-Microsoft)
    • Re: How Does Exchange Receive Email?
      ... You should get a reply from your mail server internally. ... If you have a router, port 25 must be opened and forwarding to your ... > configured to collect from the exchange and also from their previous ISP ...
      (microsoft.public.windows.server.sbs)
    • RE: DCOM patch + Exchange
      ... If I understand correctly this was an issue of exchange client ... outside your network not being able to access the server after the patch. ... Except they refered to another ISP but it does not matter what isp you have ... require access to port 135 to connect to ...
      (Focus-Microsoft)
    • Re: Setting up MX records etc
      ... need to creat in exchange itself if anything, ... We currenty use POP3 via our ISP. ... > Ensure your external IP is routed to your firewall via your ISP. ... > Open port 25 on the firewall both in and out. ...
      (microsoft.public.exchange.admin)
    • Quantcast