Routers-who is right at Comcast?
- Thread starter duke1702
- Start date
I think Comcast's fine print said (at least when I signed up for comcast) I was not to install a router on my home service connection and if Comcast found a router on the connection, my service would be terminated. I do not know about all that now, but I use a Netgear firewall router for security and would not use a cable connection without a firewall router (even Microsoft recommends such for a cable or DSL connection). I also turn off the computer each night so when I log back on the next day I will have a different address assigned (I do not want a static IP address as this at least makes me a moving target). You should do what you want to do about asking Comcast about the router, but it may be better to not ask them that question. When you call for Comcast tech support, the tech will generally ask if you have a router and often have you do a computer shut down procedure that will tell them if you have a router on the line (however there is a way to prevent them from telling there is a router on the line during this procedure). I do not think most Comcast tech support people will report a customer for having a router. I bet they use a router on their own home connection and could not care less about a customer using a router. However, if I tell the Comcast tech that I have a router on the connection, he may have been told he has to report that fact. So, I think it is better to lie in this case and not put the tech on the spot.
I called tech when I got Comcast service because I couldn't get data (turned out to be my wiring error)l. All he did was ask if I had a router and when I said yes he had me disconnect it. Once service started on one computer he said I just need to hook the router back up, but didn't say anything about it being against the rules.
I have read through my Comcast "Subscriber Agreement" and could not find the words router or firewall used anywhere within the agreement. However, I did find in one paragraph within the agreement under "Prohibited Uses of the Service" that says the customer is not to set up the service "as an end-point on a non-Comcast Local Area Network". But in another paragraph, Comcast recommends not to use more than a single computer and not to enable file or print sharing. The paragraph also says if a customer chooses to use more than a single computer or enable file or print sharing, that customer does so at their own risk.
To me these words all seems a bit contradictory, but I guess that depends on what an "as an end-point on a non-Comcast Local Area Network" means?
To me these words all seems a bit contradictory, but I guess that depends on what an "as an end-point on a non-Comcast Local Area Network" means?
If this is true, it is a great reason to terminate your comcast service ASAP. Windows machines, even Win2K Server and Win2003 Server are highly susceptible to a variety of internet attacks, including worms and viruses. The first line of defense is a good hardware NAT'ing firewall/router. I even keep my Macintosh and Linux machines behind a firewall unless they absolutely have to be internet-facing.
Full disclosure: I sell internet bandwidth to people running large servers and small ISPs, and have been involved with a startup ISP.
I've also got a comcast cable modem at home, and would never dream of connecting to it without my firewall between it and my PC.
Although there are techniques that could be theoretically used to detect NAT and even estimate the number of machines behind a NAT, it isn't really worth Comcast's time to do so. Instead they will just bully you into paying more if you tell them other the phone you are using multiple computers. Fight back, don't give in!
Comcast's language is truely bizarre. Their suggestion that you not use the comcast service as an end-point on a non-comcast local area network suggests that it is perfectly valid to resell your cable modem service to your neighbors, by WiFi, for example. In that case the Neighbor would be the end-point, and you would just be another link in the network. The big ISPs have been up in arms against WiFi sharing, so it seems like Comcast's lawyers seriously fumbled this one!
They are right to discourage Windows File and Print sharing -- after all, you don't want the kid across the street to send offensive pictures to your printer (it has happened before) or store them on your hard drive. Enabling Windows file sharing can also flood the local network with "broadcast" packets, effectively stealing bandwidth from you and your neighbors with no real gain for anyone. At my site, it looks like Comcast actually filters out Windows File sharing anyway. If you need to get around this, a VPN works nicely.
The final comment hits the nail on the head -- tech support is costly and the ISP doesn't want to get stuck in an obligation to debug your great custom network setup. There is a whole sub-industry of IT professionals dedicated to solving just those problems (with Very Large fees attached).