RE: DCOM patch + Exchange

• Previous message: Lee Evans: "RE: DCOM patch + Exchange"
• Maybe in reply to: Tim Mektrakarn: "DCOM patch + Exchange"
• Next in thread: Chris Gianelloni: "RE: DCOM patch + Exchange"
• Reply: Chris Gianelloni: "RE: DCOM patch + Exchange"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

To: wolf31o2@charter.net, dacruz@star-1.com
Date: Wed, 20 Aug 2003 10:36:23 -0400

If I understand correctly this was an issue of exchange client (outlook)
outside your network not being able to access the server after the patch.
here let me refresh your memory

*(*Anyone experience any problems with the DCOM patch and the ability for
external users to connect to a patched exchange server? Internal users have
no problems.*(*
 
Tim

Now my answer is the ISP is blocking it and not because of the patch and
this in the microsoft web site will back me up
http://support.microsoft.com/default.aspx?scid=kb;en-us;810710

Except they refered to another ISP but it does not matter what isp you have
they can block it especially now.

}Exchange works quite well without access to port 135, thank
}you.
uhm
"MAPI clients such as Outlook, require access to port 135 to connect to
Exchange 2000 Server".

I think is more than clear, it also applies for exch 5.5

Hope it helps

By the way you don't have to expose port 135 for everyone in order for this
to work

}-----Original Message-----
}From: Chris Gianelloni [mailto:wolf31o2@charter.net]
}Sent: Tuesday, August 19, 2003 3:12 PM
}To: dacruz@star-1.com
}Cc: steven.mccauley@au.faulding.com; focus-ms@securityfocus.com
}Subject: RE: DCOM patch + Exchange
}
}
}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.
}

---------------------------------------------------------------------------
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
---------------------------------------------------------------------------

• Previous message: Lee Evans: "RE: DCOM patch + Exchange"
• Maybe in reply to: Tim Mektrakarn: "DCOM patch + Exchange"
• Next in thread: Chris Gianelloni: "RE: DCOM patch + Exchange"
• Reply: Chris Gianelloni: "RE: DCOM patch + Exchange"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]