From: Chris Gianelloni (wolf31o2charter.net)
Date: Wed Aug 20 2003 - 10:28:36 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Actually, I was concerned with the fact that many people were saying
that the patch stopped clients from accessing their Exchange servers. I
could care less about having an Exchange server directly accessible to
the Internet in any way. Clients need to VPN to get to my server, so I
don't expose ANY ports (other than the VPN) to the Internet.

On Wed, 2003-08-20 at 10:36, dacruzstar-1.com wrote:
> 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:wolf31o2charter.net]
> }Sent: Tuesday, August 19, 2003 3:12 PM
> }To: dacruzstar-1.com
> }Cc: steven.mccauleyau.faulding.com; focus-mssecurityfocus.com
> }Subject: RE: DCOM patch + Exchange
> }
> }
> }On Tue, 2003-08-19 at 13:28, dacruzstar-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.
> }

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQA/Q5OkkT4lNIS36YERAuYHAKCfKKgL3lYifQtqFssPJm4EB7GRKACdEN3U
FInbEJ6jBvxfIiYEeHpZ+1A=
=OWf1
-----END PGP SIGNATURE-----

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]