Re: Comcast blocks Exchange - any way around this?

From: Javier Gomez [SBS MVP] (javier_gomez_at_remove.this.engineer.com)
Date: 06/02/04 

Date: Wed, 2 Jun 2004 07:11:26 -0400

Yes... that part is true. They do block ports 135-139... but this are for
Outlook connecting directly to the Exchange server (I have never implemented
this way). Now in SBS2k3 (Exchange2k3) we have RPC over HTTP so it works
using the standard http/https ports (80/443).

However, if your problem has to do with sending mail... then it is an
outgoing connection and there are no ports that need to be open (for this
specific item). I recommend that you use their mailservers
(smtp.comcast.net) as your smarthost and not use DNS. I find them pretty
reliable and using DNS can have some repercusions (specially if you are on a
dynamic IP).

My $0.02, 

-- 
Javier [SBS MVP]
<< SBS ROCKS !!! >>
"Tzu Do Nim" <someone@somedomain.com> wrote in message
news:%23bAV$vFSEHA.1312@TK2MSFTNGP12.phx.gbl...
> My bad. I ran into problems sending e-mail, checked their site for the
> settings & saw this FAQ so I quit trying. I'm not sure what I had wrong
but
> I'll try again later to see if I can get it working.  The router between
the
> cable modem & my server may not have 135 & 445 open. Which others should I
> open up?
>
> It was MSBlast & their FAQ said it was temporary. Here's the quote...
>
>       "Why can't I get my Microsoft Exchange E-mail?
>
>       To help protect our customers from the effects of the recent MSBlast
> worm, Comcast has temporarily shut down access to ports 135 and 445. These
> are the ports that the MSBlast worm uses to propagate itself - in addition
> to being the ports that Microsoft Exchange servers use by default. Comcast
> continues to take precautionary steps to stem the affects of this worm on
> our network and protect our customers. We will continue to monitor the
> situation as it evolves. This does not affect your @Comcast.net E-mail."
>
>
>
>
> "Javier Gomez [SBS MVP]" <javier_gomez@remove.this.engineer.com> wrote in
> message news:uuBLOz4REHA.3708@TK2MSFTNGP10.phx.gbl...
> > Are you sure? I also my home SBS box using Comcast and they don't block
> SMTP
> > inbound nor outbound... at least not yet. Plus the Slammer worm was a
SQL
> > thingy... port 1434 (if I recall correctly). Nothing to do with SMTP or
> > Exchange. How are you testing this?
> >
> > In any event... what Frank is stating is one way to go. Another would be
> to
> > use the POP3 connector or switch to a business-class account.
> >
> > -- 
> > Javier [SBS MVP]
> >
> > << SBS ROCKS !!! >>
> >
> >
> > "Frank McCallister" <anonymous@discussions.microsoft.com> wrote in
message
> > news:u6NkZW4REHA.916@TK2MSFTNGP12.phx.gbl...
> > > Hi
> > >
> > > When you say Comcast blocks Exchange do you mean they block port 25?
If
> so
> > > you can get mailhop outbound from dyndns.org and send on port 2525.
> > > Bellsouth blocks 25 and I am using mailhop outbound with no problems.
> > >
> > > Frank McCallister
> > > COMPUMAC
> > > "Tzu Do Nim" <someone@somedomain.com> wrote in message
> > > news:eD$ne#3REHA.3840@TK2MSFTNGP09.phx.gbl...
> > > > I downloaded SBS2003 from the MSDN subscriber downloads for use at
> home
> > > (so
> > > > I'll have the same setup as at the office). Unfortunately, Comcast,
my
> > > cable
> > > > ISP says it blocks Exchange due to the problems they had with the
> > Slammer
> > > > worm. Is there any way I could get my home network set to use
Exchange
> > > > anyway? Can I make Outlook 2003 send like its not connected to
> Exchange
> > &
> > > > still have Exchange deliver my mail via the POP3 connector? Its just
> my
> > > home
> > > > network so I don't really need to use Exchange to its full potential
> > > > but...since its there...
> > > >
> > > > TIA
> > > > Steve
> > > >
> > > >
> > >
> > >
> >
> >
>
>
>

Relevant Pages
Quantcast