quackagator
Senior member
- Jul 1, 2002
- 913
- 22
- 81
Originally posted by: Jeff7181
Originally posted by: Proletariat
Hahahaha. Comcast, you rock dudes.Originally posted by: SethK28
Originally posted by: aplefka
Can anyone get through to 1-888-COMCAST? I'm gonna try calling the local number that goes to it.
You wont, they pulled the line. Even if you get thru past the busy signal and navigate thru the menu it will auotmatically disconnect you
Do you blame them? They obviously know there's a problem. Answering 150,000 phone calls from people saying, "tha intarweb is broke, you suck" won't help them fix it.
Originally posted by: aplefka
Originally posted by: Jeff7181
Originally posted by: Proletariat
Hahahaha. Comcast, you rock dudes.Originally posted by: SethK28
Originally posted by: aplefka
Can anyone get through to 1-888-COMCAST? I'm gonna try calling the local number that goes to it.
You wont, they pulled the line. Even if you get thru past the busy signal and navigate thru the menu it will auotmatically disconnect you
Do you blame them? They obviously know there's a problem. Answering 150,000 phone calls from people saying, "tha intarweb is broke, you suck" won't help them fix it.
After how my service has been over the past month, yes. They know there is an overloaded node and they're doing nothing about it. It's been months since it got overloaded and they're just now trying to split it. My ping always goes way up during peak hours and the only reason I have Comcast is to play games. If I have high ping I might as well quit gaming and buy dialup because it's cheaper.
So yeah, I do blame them. Based on their track record of knowing about problems but not fixing them, they should be damn ready to hear it from all corners of the country if they're not going to fix the problem. Most normal home users won't know how to change the DNS Servers, so the least they could do is have a tutorial on how to do it on the phone.
By the way, changing them to 4.2.2.1 and 4.2.2.2 worked for me.
Originally posted by: Jeff7181
Originally posted by: aplefka
Originally posted by: Jeff7181
Originally posted by: Proletariat
Hahahaha. Comcast, you rock dudes.Originally posted by: SethK28
Originally posted by: aplefka
Can anyone get through to 1-888-COMCAST? I'm gonna try calling the local number that goes to it.
You wont, they pulled the line. Even if you get thru past the busy signal and navigate thru the menu it will auotmatically disconnect you
Do you blame them? They obviously know there's a problem. Answering 150,000 phone calls from people saying, "tha intarweb is broke, you suck" won't help them fix it.
After how my service has been over the past month, yes. They know there is an overloaded node and they're doing nothing about it. It's been months since it got overloaded and they're just now trying to split it. My ping always goes way up during peak hours and the only reason I have Comcast is to play games. If I have high ping I might as well quit gaming and buy dialup because it's cheaper.
So yeah, I do blame them. Based on their track record of knowing about problems but not fixing them, they should be damn ready to hear it from all corners of the country if they're not going to fix the problem. Most normal home users won't know how to change the DNS Servers, so the least they could do is have a tutorial on how to do it on the phone.
By the way, changing them to 4.2.2.1 and 4.2.2.2 worked for me.
Is DSL available in your area? If it is, you might contact them and ask for a free month to try it out.
Originally posted by: sharkeeper
No problems around the baltimore/dc area. I use them as a relay and the gateway is up 100%...
Why use their crappy DNS anyways? I never understood this. If you have an active directory domain you must have a working dns server so...
Originally posted by: Jeff7181
Originally posted by: sharkeeper
No problems around the baltimore/dc area. I use them as a relay and the gateway is up 100%...
Why use their crappy DNS anyways? I never understood this. If you have an active directory domain you must have a working dns server so...
What makes their DNS crappy? I mean, other than these few hours of downtime. How is Comcast's DNS inferior to other ones?
Originally posted by: aplefka
Originally posted by: Jeff7181
Originally posted by: sharkeeper
No problems around the baltimore/dc area. I use them as a relay and the gateway is up 100%...
Why use their crappy DNS anyways? I never understood this. If you have an active directory domain you must have a working dns server so...
What makes their DNS crappy? I mean, other than these few hours of downtime. How is Comcast's DNS inferior to other ones?
Do you work for Comcast? Seriously, you've defended them in all the posts that I've seen and you're even the person who started this thread. Make up your mind, and stop sucking them off. Comcast isn't as great as you think it is. Just because you have good experiences with them doesn't mean all of us do.
Originally posted by: aplefka
Originally posted by: Jeff7181
Originally posted by: sharkeeper
No problems around the baltimore/dc area. I use them as a relay and the gateway is up 100%...
Why use their crappy DNS anyways? I never understood this. If you have an active directory domain you must have a working dns server so...
What makes their DNS crappy? I mean, other than these few hours of downtime. How is Comcast's DNS inferior to other ones?
Do you work for Comcast? Seriously, you've defended them in all the posts that I've seen and you're even the person who started this thread. Make up your mind, and stop sucking them off. Comcast isn't as great as you think it is. Just because you have good experiences with them doesn't mean all of us do.
Originally posted by: Ameesh
Seattle is fuxored too, i am on the east side
Originally posted by: Blastomyces
It seems to me like I can browse faster with the 4.2.2.1 than the standard DNS, but thats just my perception I cant cant confirm it.