Hey yo:

As many of you know, what used to be AT&T@Home (in MI) has become 
Comcast Cable, which recently did some merger thing with the 
Excite people, resulting in everybody having to do a bunch of 
settings and system changes to keep their cable (modem) access.  

My question is about the "comcast support software" the company 
had everybody install.  Not only was it annoying to run another 
flippin' TSR just to have access, but as soon as I installed the 
software my Firewall (Tiny) got *flooded* with outgoing TCP 
requests.  There were two kinds--one from the Comcast Support 
Software I'd installed, and another one from a program I didn't 
recognize, the name of which didn't make sense but had the 
word "Customer" in it.  Denying the "customer" one didn't seem to 
interrupt my access (except for flooding my logs), but denying the 
Comcast Support one did--and the attempts were nearly constant.  I 
called these people (for the umteenth time; they also disabled 
remote mail access and screwed up my email addy when they did the 
merger, so we'd been fighting anyway) and they blew me off.  I 
told them they had to tell me what those connections were, and 
they quite frankly said no, they didn't (is that true?).  A week 
later when I got notice in the mail that the price of my "service" 
was going up, I cancelled it; but I have friends still using it, 
and they want to know if there's a way to find out if Comcast is 
collecting information from their computer or about their net 
use.  I told them to whois the IP that it was trying to connect to 
(my logs got purged so I don't have it anymore), and they tell me 
that all they can find out is that it belongs to Comcast.

Any of you ladies and gentlemen affected by this, or have more 
information, I'd love to hear it.  Also, if anybody is digging 
into this problem and would like help, I'll volunteer.

Peace & Privacy,
Sara T. 

________________________________________________________________
Get your own evilemail.com address at http://www.evilemail.com


 
                   

Reply via email to