07-09-2006 01:47 AM
07-09-2006 07:30 AM
07-09-2006 04:42 PM
07-12-2006 11:31 AM - edited 07-12-2006 11:31 AM
Message Edited by edelbeb on 07-12-2006 11:33 AM
07-13-2006 02:09 PM
Every port has a known vulnerability, so therefore Comcast doesn't block every "vulnerable port." Every port you open up through your router increses your chances of an attack. However, it is often nessicary to do so. With networks, you have to learn how to balence security and accessibility.
And if Comcast blocks all ports subject to known vulnerabilities at it's end, then shouldn't any open port that you can forward to a particular PC should be reasonably safe?
07-13-2006 02:18 PM
07-13-2006 03:40 PM - edited 07-13-2006 03:40 PM
Sorry if anyone felt I was implying that Comcast DID block all vulnerable ports. I was just pointing out the fallacy in the tech's reasoning that, because Comcast took care of blocking at their end, the customer would not need to block or forward ports.
Anyway, after I did some thinking (a task I save for rare occasions), I realized that I may have been a bit harsh on the Comcast tech. If someone signs up for Comcast HNS, Comcast is responsible for maintaining that person's home network. For troubleshooting purposes, if all HNS router are configured in a way that works with Comcast, Comcast can rule out a misconfigured router as the cause of a problem. If an HNS user changed the settings of the router, the Comcast tech needs to check all settings and then rule out the changes settings as the cause. Checking those settings would require more time and a more expensive, more experienced, and better trained tech, thus increasing Comcast's cost.
Message Edited by edelbeb on 07-13-2006 03:41 PM
©2011 Comcast | Investor Relations | Press Room | Corporate Blog | Privacy Statement | Visitor Agreement | Comcast.com Feedback | Site Map