Here We Go Again - SMTP and Comcast Portal
Boris
came back sometime this morning,
See:
<BuidnQAG7-ucAAna...@comcast.com>
but the problem is now back tonight, and again on all my machines.
I called Comcast, explained, and was asked if I could reach the internet.
Sheesh. The tech said he'd write up the magical ticket, and actually
said it would be fixed real quick. But, we were either disconnected, or
he then hung up.
I called back. This tech wrote up a ticket and gave me the number. The
problem seems to happen every night, sometimes beginning early in the
evening, sometimes later. This tech asked if I wanted a service call for
them to come out and check my modem. Since I can all over the internet,
except for Comcast, and I can receive email, but can't send, I don't see
the need to check the modem. Besides, things work in the daytime, which
is when they'd be here.
I don't mind the Comcast Portal going down, but this is the time of day
that I answer my emails, especially to my kids away at school.
DrFeelgoodWA
<Boris> wrote in message
news:Xns9A2CCE712133...@216.196.97.136...
The simplest solution would be to sign up for a third party e-mail
service such as GMail.
How close are you to a college or large group of kids? Have you tried
running speed test during the hours you are having these problems?
BTW check out some of the FIOS forums. They all seem to have a large
number of similar complaints and it could be years before they even
offer service in your area.
Boris
news:n62dndfewdT07Aja...@comcast.com:
Hi,
There are no large uninversities with dorms nearby. Speed tests right
now show mid 3MB down, and 1.5MB up.
some1
If you can reach using this, it indicates there is a DNS problem which is a
Comcast problem if you have done nothing to change the Windows default
settings for DNS.
<Boris> wrote in message
news:Xns9A2CCE712133...@216.196.97.136...
DrFeelgoodWA
"some1" <xdci...@REMOVEsneakemail.com> wrote in message
news:fn3tro$6sb$1...@registered.motzarella.org...
> When you have the problem, load http://76.96.54.12/a/ into your
> address bar. If you can reach using this, it indicates there is a
> DNS problem which is a Comcast problem if you have done nothing to
> change the Windows default settings for DNS.
or try http://204.127.195.15
Unk
Similar problem with e-maill. After several hours of searching, I foud that Comcast is
using port 587 for smtp.comcast.net mine was set as port 25. It worked fine for years....
I found the settings in the FAQ's for setting up Outlook Express
Give it a try.
http://www.comcast.net/help/faq/index.jsp?faq=EmailOutlook_Express17739
Thomas T. Veldhouse
>
> Similar problem with e-maill. After several hours of searching, I foud that Comcast is
> using port 587 for smtp.comcast.net mine was set as port 25. It worked fine for years....
>
Yes, they are going to authenticated SMTP. Apparently rolling it out on a
regional basis, but at least, in some cases, have applied it based on SMTP
traffic "from" a cable modem address ... even if the outgoing SMTP traffic is
TO smtp.comcast.net
> I found the settings in the FAQ's for setting up Outlook Express
> Give it a try.
>
> http://www.comcast.net/help/faq/index.jsp?faq=EmailOutlook_Express17739
>
But that doesn't explain your lack of ability to get to their portal site does
it?
--
Thomas T. Veldhouse
Wishing without work is like fishing without bait.
-- Frank Tyger
Rick Merrill
> When you have the problem, load http://76.96.54.12/a/ into your address bar.
> If you can reach using this, it indicates there is a DNS problem which is a
> Comcast problem if you have done nothing to change the Windows default
> settings for DNS.
To be certain, shouldn't he also do
>ipconfig /flushdns
?
some1
"Rick Merrill" <rick0....@NOSPAM.gmail.com> wrote in message
news:kPydneJeveTmrAva...@comcast.com...
I don't think so. If you have the phone number, you don't need the name.
Steve Baker
wrote:
>> Similar problem with e-maill. After several hours of searching, I foud that Comcast is
>> using port 587 for smtp.comcast.net mine was set as port 25. It worked fine for years....
THe most likely reason for port 25 being blocked is that you have a
spambot running. You should look into that.
>Yes, they are going to authenticated SMTP. Apparently rolling it out on a
>regional basis,
There is absolutely no evidence to support that. And, there is no
such thing as a regional SMTP server.
>but at least, in some cases, have applied it based on SMTP
>traffic "from" a cable modem address ... even if the outgoing SMTP traffic is
>TO smtp.comcast.net
So what, that is a spammer MO. You were running a SMTP server which
was accessible from outside of Comcast, which is prohibited by the
AUP. And yet you regularly whine as though Comcast has done something
awful to you. You're just making yourself look foolish.
--
Steve Baker
Boris
> When you have the problem, loadhttp://76.96.54.12/a/into your address bar.
> If you can reach using this, it indicates there is a DNS problem which is a
> Comcast problem if you have done nothing to change the Windows default
> settings for DNS.
>
> <Boris> wrote in message
>
> news:Xns9A2CCE712133...@216.196.97.136...
>
> > Success was short lived. My smtp and ability to get towww.comcast.net
> > came back sometime this morning,
>
> > See:
>
> > but the problem is now back tonight, and again on all my machines.
>
> > I called Comcast, explained, and was asked if I could reach the internet.
> > Sheesh. The tech said he'd write up the magical ticket, and actually
> > said it would be fixed real quick. But, we were either disconnected, or
> > he then hung up.
>
> > I called back. This tech wrote up a ticket and gave me the number. The
> > problem seems to happen every night, sometimes beginning early in the
> > evening, sometimes later. This tech asked if I wanted a service call for
> > them to come out and check my modem. Since I can all over the internet,
> > except for Comcast, and I can receive email, but can't send, I don't see
> > the need to check the modem. Besides, things work in the daytime, which
> > is when they'd be here.
>
> > I don't mind the Comcast Portal going down, but this is the time of day
> > that I answer my emails, especially to my kids away at school.
Why didn't I think of that? I'm at work now, but will try when it
goes out again tonight.
Boris
True.
By the way, this morning at 6 am, the smtp and Comcast portal problem
was gone. It'll probably be back tonight.
I've always used smtp 25 with success, for years. When this problem
started, Comcast told me that they have no idea why I was still using
25, and that was my problem. So, I tried port 587, with no luck. If
25 doesn't work, 587 doesn't either. If 25 works, 587 does, too.
some1
"Boris" <boris-b...@excite.com> wrote in message
news:c17b778b-8eb6-4ad1...@c4g2000hsg.googlegroups.com...
> On Jan 21, 9:10 pm, "some1" <xdci29...@REMOVEsneakemail.com> wrote:
>> When you have the problem, loadhttp://76.96.54.12/a/into your address
>> bar.
>> If you can reach using this, it indicates there is a DNS problem which is
>> a
>> Comcast problem if you have done nothing to change the Windows default
>> settings for DNS.
>
> goes out again tonight.
Let us know what happens please.
Boris
> "Boris" <boris-badeno...@excite.com> wrote in message
>
> news:c17b778b-8eb6-4ad1...@c4g2000hsg.googlegroups.com...
>
> > On Jan 21, 9:10 pm, "some1" <xdci29...@REMOVEsneakemail.com> wrote:
> >> bar.
> >> If you can reach using this, it indicates there is a DNS problem which is
> >> a
> >> Comcast problem if you have done nothing to change the Windows default
> >> settings for DNS.
>
> > Why didn't I think of that? I'm at work now, but will try when it
> > goes out again tonight.
>
> Let us know what happens please.
Of course.
DrFeelgoodWA
"Steve Baker" <bak...@comcast.net> wrote in message
news:fn5dn...@news3.newsguy.com...
> On 22 Jan 2008 14:50:33 GMT, "Thomas T. Veldhouse"
> <vel...@yahoo.com>
> wrote:
>
>>> Similar problem with e-maill. After several hours of searching, I
>>> foud that Comcast is
>>> using port 587 for smtp.comcast.net mine was set as port 25. It
>>> worked fine for years....
>
> THe most likely reason for port 25 being blocked is that you have a
> spambot running. You should look into that.
>
>>Yes, they are going to authenticated SMTP. Apparently rolling it
>>out on a
>>regional basis,
>
> There is absolutely no evidence to support that. And, there is no
> such thing as a regional SMTP server.
Bullshit!!!!!!!!!!!!!!!
Do you think Comcast runs the e-mail for their millions of customers
on a single mail server located at their headquarters?
Go find a rabbit hutch and eat some smarter pills Steve, your
ignorance is showing
Steve Baker
<xdci...@REMOVEsneakemail.com> wrote:
>If you have the phone number, you don't need the name.
That's not quite true. Http://76.96.54.12/a/ isn't the same thing as
http://www4.comcast.net/a/. There is a "Host: " line in the HTTP
request, and "Host: 76.96.54.12" could lead to a totally different
site than "Host: www4.comcast.net". That's how one server with one IP
address can host thousands of different web sites.
--
Steve Baker
Steve Baker
<drfeel...@comcast.net> wrote:
>> There is absolutely no evidence to support that. And, there is no
>> such thing as a regional SMTP server.
>
>
>
>Bullshit!!!!!!!!!!!!!!!
>
>Do you think Comcast runs the e-mail for their millions of customers
>on a single mail server located at their headquarters?
Do you think that question is relevant, Scrotum Sniffer? There is
one IP address for smtp.comcast.net. Connecting to that IP address
"connects through" to one of many SMTP servers. Whichever one you
happen to get is independent of where you happen to be located. Those
servers are reachable from all over the planet, you know. Here are two
examples of the servers reached from MA. One in PA, one in CA. Pretty
"regional", eh?
OMTA11.westchester.pa.mail.comcast.net
OMTA02.emeryville.ca.mail.comcast.net
>Go find a rabbit hutch and eat some smarter pills Steve, your
>ignorance is showing
Braap, braap, braap... force 10 irony event detected. Braap...
--
Steve Baker
some1
LOL, perhaps a call forwarding analogy would fit in this instance. You
decide.
>
> --
> Steve Baker
Boris
news:fn5f77$vsv$1...@registered.motzarella.org:
> I'be been home for a while, and smtp was working fine. Getting to the
Comcast portal was slow, but do-able.
At (exactly) 7:30 pm, I can no longer get to the portal.
76.96.54.12/a/ yields website found, waiting for reply, and opening
page....but nothing ever opens.
204.121.195.15 yields same, that is, opening page, opening page but
nothing ever opens.
In both cases, the green progress bar has eventually moved completely
from left to right, and remains there.
SMTP is still working fine. I'll test both portal and smtp a few times
tonight.
Boris
216.196.97.136:
> "some1" <xdci...@REMOVEsneakemail.com> wrote in
> news:fn5f77$vsv$1...@registered.motzarella.org:
>
>>
>> "Boris" <boris-b...@excite.com> wrote in message
>> news:c17b778b-8eb6-4ad1-8848-e9deee87b653
@c4g2000hsg.googlegroups.com..
>> .
>>> On Jan 21, 9:10 pm, "some1" <xdci29...@REMOVEsneakemail.com> wrote:
>>>> When you have the problem, loadhttp://76.96.54.12/a/into your
>>>> address bar.
>>>> If you can reach using this, it indicates there is a DNS problem
>>>> which is a
>>>> Comcast problem if you have done nothing to change the Windows
>>>> default settings for DNS.
>>>
>>> Why didn't I think of that? I'm at work now, but will try when it
>>> goes out again tonight.
>>
>> Let us know what happens please.
>>
>> I'be been home for a while, and smtp was working fine. Getting to the
> Comcast portal was slow, but do-able.
>
> At (exactly) 7:30 pm, I can no longer get to the portal.
>
> 76.96.54.12/a/ yields website found, waiting for reply, and opening
> page....but nothing ever opens.
>
> 204.121.195.15 yields same, that is, opening page, opening page but
> nothing ever opens.
>
> In both cases, the green progress bar has eventually moved completely
> from left to right, and remains there.
>
> SMTP is still working fine. I'll test both portal and smtp a few times
> tonight.
>
>
I called Comcast to report the portal problem (smtp still good). Just
got off the phone. Competent tech didn't make me go though all the
script activities. I told him what IPs I've been using, and he asked me
to try 216.148.227.202. Still no luck.
He said he just arrived and heard about a system wide problem on his way
in, and went to check to see the details. Yes, he said they had been
receiving many calls about same thing, and it's in pockets nationwide,
and at all times of the day. He updated my ticket from yesterday, and
told me he was told it should be fixed by the end of the week.
some1
<Boris> wrote in message
news:Xns9A2DCF5FECEE...@216.196.97.136...
I thought for sure it was going to be DNS. For the recored, right now I can
get to comcast.net. I don't go there much and I haven't noticed any
particular problems with my connection recently. It would be interesting to
know what the problem is but at this point it appears one guess would be as
good as another. Good luck.
Boris
news:fn6hsi$1tb$1...@registered.motzarella.org:
And it's now 11:22 pm, about four hours after the portal went down, and
it's still down. But, my smtp is still working fine. I don't care about
the portal, just my smtp server.
Boris
news:Xns9A2DEDFE642A...@216.196.97.136:
big snip
>>
>> I thought for sure it was going to be DNS. For the recored, right
>> now I can get to comcast.net. I don't go there much and I haven't
>> noticed any particular problems with my connection recently. It
>> would be interesting to know what the problem is but at this point it
>> appears one guess would be as good as another. Good luck.
>>
>>
> And it's now 11:22 pm, about four hours after the portal went down,
> and it's still down. But, my smtp is still working fine. I don't
> care about the portal, just my smtp server.
>
>
>
> It's 6:26 am, and the portal came back sometime between 11:22 pm last
night and now. SMTP is fine.
some1
<Boris> wrote in message
news:Xns9A2E41D3AD5D...@216.196.97.136...
I see in your other thread that you want to get to your web mail and that's
why you're going to the portal. If that's the case, try this link. It
works for me. It redirects to a secure login. It may or may not work for
you when the portal is down. It's worth a try.
http://www.comcast.net/qry/goto?app=mail