I really really hate ATT

[PoPPeR]

I had a Cal-League matchup schedule for tonight, and 10 minutes before the match starts I'm experiencing pings of 300-400. Everyone else on the server is pinging 20-40's. I get off really quick, try to fix it, nothing works, so I go on ATT's website to ask for some tests to be run. I do a tracert to yahoo, google, and ucberkeley (i'm in walnut creek, 30 minutes north of berkeley) and i'm experiencing 300ms responses to them. I got freakin 180 on dialup.

I talk to one person, they have me run a tracert in dos to yahoo, then make me paste all 15 lines one at a time so she can "examine" them. The pings are all about 100ms until it reaches me, then springs to 330ms. She transfers me to some technical support person (who the hell was she if she wasn't tech support) and he takes about 10 minutes to run some bullcrap tests "within the att network" that shows me pinging 130ms. Which I guess is stable enough for them to blow me off. I ask him what the hell is the problem then, why is my friend, who lives 10 minutes away from me and uses Astound, pinging 30 to a server that I'm pinging 300 to. He says well i show you pinging 130 so uh yeah your cable is fine. I tell him I'm experiencing the same horrible ping to over 10 westcoast servers. He tells me, well I can't escalate this issue because I show you pinging under the acceptable range. I understand that, but as a tech support person you haven't helped me in the least bit. I'm still experiencing crappy service and I want something done about it. I'm not paying 50$ a month for 180-300ms pings. I got that on dialup. Astound isn't in my area, so I have a lack of choices.

I understand my account means jack to ATT. They couldn't care less about me, and i'm under contract right now. The guy was in the middle of talking to me and I pretty much said okay, fine, whatever, and left the chat. I've completely missed my Cal-League meeting, and they wont send a tech out (well, for 50$ they will) and they wont give me a new modem unless something is defective with the old one, which of course costs 50$ right there to examine it.

If my service continues to be like this, I'm going to raise hell with them. Call them up, ask for a supervisor, anything. Sorry for this rant but i've heard some bad things about ATT and never really experienced them until recently.

 

[Angrymarshmello]

Originally posted by: PoPPeR
I had a Cal-League matchup schedule for tonight, and 10 minutes before the match starts I'm experiencing pings of 300-400. Everyone else on the server is pinging 20-40's. I get off really quick, try to fix it, nothing works, so I go on ATT's website to ask for some tests to be run. I do a tracert to yahoo, google, and ucberkeley (i'm in walnut creek, 30 minutes north of berkeley) and i'm experiencing 300ms responses to them. I got freakin 180 on dialup.

I talk to one person, they have me run a tracert in dos to yahoo, then make me paste all 15 lines one at a time so she can "examine" them. The pings are all about 100ms until it reaches me, then springs to 330ms. She transfers me to some technical support person (who the hell was she if she wasn't tech support) and he takes about 10 minutes to run some bullcrap tests "within the att network" that shows me pinging 130ms. Which I guess is stable enough for them to blow me off. I ask him what the hell is the problem then, why is my friend, who lives 10 minutes away from me and uses Astound, pinging 30 to a server that I'm pinging 300 to. He says well i show you pinging 130 so uh yeah your cable is fine. I tell him I'm experiencing the same horrible ping to over 10 westcoast servers. He tells me, well I can't escalate this issue because I show you pinging under the acceptable range. I understand that, but as a tech support person you haven't helped me in the least bit. I'm still experiencing crappy service and I want something done about it. I'm not paying 50$ a month for 180-300ms pings. I got that on dialup. Astound isn't in my area, so I have a lack of choices.

I understand my account means jack to ATT. They couldn't care less about me, and i'm under contract right now. The guy was in the middle of talking to me and I pretty much said okay, fine, whatever, and left the chat. I've completely missed my Cal-League meeting, and they wont send a tech out (well, for 50$ they will) and they wont give me a new modem unless something is defective with the old one, which of course costs 50$ right there to examine it.

If my service continues to be like this, I'm going to raise hell with them. Call them up, ask for a supervisor, anything. Sorry for this rant but i've heard some bad things about ATT and never really experienced them until recently.

Course they don't care about you - they just care about your money. And um, you need to get a life or something if you have nothing better to do than b1tch at their tech support about pings in a CyberAthlete League.

 

[NikPreviousAcct]

Originally posted by: PoPPeR
[insert lots of bullshit here]

I hate customers like you.

1) you don't seem to know how a traceroute works - a traceroute starts with you and ends up at the server you choose. The first hop in a traceroute IS YOU. The second is your gateway, and the end of the ATTBI network.
2) the initial tech you were talking to, tier1, is Customer Service, not tech support. That's why they're fvcking idiots. Maybe you should apply; you sound fully qualified for the job.
3) the end of the ATTBI network is your gateway. Beyond that is att.net, sprint.net, uunet, etc. Quit bitching about ATTBI if ATTBI isn't the problem

Whether you have a friend 10 minutes away or fvcking next door with a perfect connection doesn't mean jack sh|t. If you have a connection problem, the ping to your default gateway is the only test that ATTBI will accept as a proper test for high ping times (over 200ms) or packetloss (even 1 lost packet is a problem)

And what's with this "but as a tech support person you haven't helped me in the least bit" bullsh|t? They're ATTBI techs, not Mr. Fixit. They'll troubleshoot the ATTBI network. If your connection on ATTBI looks fine (first hop in any traceroute or a continuous ping to default gateway shows no problems), then IT'S NOT THEIR JOB TO FIX IT. What is it with expectant wankers like you who think that just because tech support is free gives them the right to call about everything and their goddamn broken blender? Jesus Christ.

Think of it this way. ATTBI is like your driveway. ATT.NET is like the street that you live on. Sprint.net is like the highway between cities. If there's a problem on the highway between cities, are you going to call your driveway and bust their balls? Of course you will. All idiots who don't think things through or take the time to understand what they're explained do.

:|

Oh, and if you're considering even questioning this, I'm a senior Tier2 ATTBI tech. I have more authority, knowledge, and experience in this than God.

 

[PoPPeR]

so as someone who works for ATT... since i'm experiencing bad service, your solution to my problem is?

 

[Mill]

Sometimes I wonder if "God' is sitting back laughing at Nik and his anger problems. BTW, post a full tracert PoPPeR so we can see if this problem is ATT or another ISP that handles traffic to your server.

 

[PoPPeR]

you call me an idiot, sorry that I don't work for ATT, know exactly how the internet works, or understand why someone who lives 10 minutes from me gets lower pings. Its called a paying customer. I went to school to specialize in another profession, not to study giant broadband networks. That's your job. I, as a paying customer, have the right to demand that you do your job, seeing how your taking my money. If i'm not satisfied with the service, what do you want me to do? I asked once, nothing improved, asked twice, nothing improved. okay, so its not your fault. Its my fault i'm getting bad service?

 

[PoPPeR]

1 vlan206.inr-203-eva.Berkeley.EDU (128.32.206.1) 0.633 ms 0.486 ms 0.450 ms
2 vlan210.inr-202-doecev.Berkeley.EDU (128.32.255.9) 0.586 ms 0.435 ms 0.555 ms
3 gigE6-0-0.inr-new-666-doecev.Berkeley.EDU (128.32.0.249) 0.850 ms 0.496 ms 0.534 ms
4 qsv-juniper--ucb-gw.calren2.net (128.32.0.70) 2.271 ms 2.485 ms 2.321 ms
5 POS1-0.hsipaccess1.SanJose1.Level3.net (209.247.159.109) 2.524 ms 2.473 ms 2.783 ms
6 ae0-53.gar1.SanJose1.level3.net (64.159.2.76) 3.450 ms 3.029 ms 3.026 ms
7 so-6-0-0.edge1.SanJose1.level3.net (209.244.3.138) 3.307 ms 3.553 ms 3.324 ms
8 att-level3-oc48.SanJose1.Level3.net (209.0.227.30) 4.437 ms 4.732 ms 4.762 ms
9 tbr1-p012201.sffca.ip.att.net (12.123.13.189) 5.197 ms 4.981 ms 5.191 ms
10 gbr2-p10.sffca.ip.att.net (12.122.11.70) 4.483 ms 4.597 ms 4.544 ms
11 gar1-p370.sffca.ip.att.net (12.123.13.61) 4.501 ms 4.559 ms 4.497 ms
12 12.244.72.205 (12.244.72.205) 22.384 ms 22.640 ms 22.052 ms
13 12.244.67.13 (12.244.67.13) 23.134 ms 22.906 ms 22.962 ms
14 12.244.67.9 (12.244.67.9) 15.000 ms 14.966 ms 14.855 ms
15 12.244.67.5 (12.244.67.5) 15.214 ms 14.805 ms 14.428 ms
16 12.244.67.66 (12.244.67.66) 14.930 ms 15.345 ms 15.680 ms
17 12.244.67.70 (12.244.67.70) 16.379 ms 15.785 ms 15.958 ms
18 12.244.98.229 (12.244.98.229) 24.405 ms 24.324 ms 24.534 ms
19 12-235-203-148.client.attbi.com (12.235.203.148) 450.916 ms 131.361 ms 89.914 ms

 

[KK]

Originally posted by: PoPPeR
so as someone who works for ATT... since i'm experiencing bad service, your solution to my problem is?

First off, I believe the company's name is Comcast now. Also customer support is pretty much all contracted out so they don't care.

KK

 

[NikPreviousAcct]

Originally posted by: PoPPeR
so as someone who works for ATT... since i'm experiencing bad service, your solution to my problem is?

Learn how things work before you go foolishly pointing fingers and getting pissed. I've seen enough people exactly like you and been yelled at enough by people exactly like you for things that aren't the fault of nor fall under control of ATTBI, and I'm sick of it.

If you run a continuous ping to your gateway and see more than 200ms in the Ping Statistic's "average time in milliseconds" or see one single packet lost, then ATTBI can do something about it - because that would be an ATTBI problem. Anything else is beyond our scope and control. If you run a traceroute and the trace times out on one line, look at the server names before and after the timeout. They will be the ones responsible for the high ping times. If you find no time-outs, no packetloss, and nothing wrong in the traceroute, consider doing some general maintenance like reinstalling drivers for your NIC, reinstalling Client for MS Networks or TCP/IP. If those don't work, depending on the operating system, I would suggest either changing slots that the NIC is physically installed to or replacing it. If you've done that or don't wish to, the only option you have to do is contact those who are actually responsible for the problem, or simply wait for it to clear up if there is no clear issue.

 

[NikPreviousAcct]

Originally posted by: PoPPeR
you call me an idiot, sorry that I don't work for ATT, know exactly how the internet works, or understand why someone who lives 10 minutes from me gets lower pings. Its called a paying customer. I went to school to specialize in another profession, not to study giant broadband networks. That's your job. I, as a paying customer, have the right to demand that you do your job, seeing how your taking my money. If i'm not satisfied with the service, what do you want me to do? I asked once, nothing improved, asked twice, nothing improved. okay, so its not your fault. Its my fault i'm getting bad service?

If you don't know how the internet works, why don't you simply listen to one who does? Or to the people who provide your internet service? You call up ATTBI and bitch at them. They tell you that it's not their problem, and prove it to you. Then you basically say that you know better than they do by refusing to believe that it's anyone's but ATTBI's problem.

Then you say that you don't know much about the internet.

Do you ever take your car into the shop and tell the ASE Certified mechanic that he's wrong?

 

[NikPreviousAcct]

Originally posted by: KK

Originally posted by: PoPPeR
so as someone who works for ATT... since i'm experiencing bad service, your solution to my problem is?

First off, I believe the company's name is Comcast now. Also customer support is pretty much all contracted out so they don't care.

KK

Wrong. ATTBI customers will still be ATTBI customers and won't be "moved over" to Comcast. All customers joining will be Comcast customers using ATTBI equipment.

 

[NikPreviousAcct]

Originally posted by: PoPPeR
1 vlan206.inr-203-eva.Berkeley.EDU (128.32.206.1) 0.633 ms 0.486 ms 0.450 ms
2 vlan210.inr-202-doecev.Berkeley.EDU (128.32.255.9) 0.586 ms 0.435 ms 0.555 ms
3 gigE6-0-0.inr-new-666-doecev.Berkeley.EDU (128.32.0.249) 0.850 ms 0.496 ms 0.534 ms
4 qsv-juniper--ucb-gw.calren2.net (128.32.0.70) 2.271 ms 2.485 ms 2.321 ms
5 POS1-0.hsipaccess1.SanJose1.Level3.net (209.247.159.109) 2.524 ms 2.473 ms 2.783 ms
6 ae0-53.gar1.SanJose1.level3.net (64.159.2.76) 3.450 ms 3.029 ms 3.026 ms
7 so-6-0-0.edge1.SanJose1.level3.net (209.244.3.138) 3.307 ms 3.553 ms 3.324 ms
8 att-level3-oc48.SanJose1.Level3.net (209.0.227.30) 4.437 ms 4.732 ms 4.762 ms
9 tbr1-p012201.sffca.ip.att.net (12.123.13.189) 5.197 ms 4.981 ms 5.191 ms
10 gbr2-p10.sffca.ip.att.net (12.122.11.70) 4.483 ms 4.597 ms 4.544 ms
11 gar1-p370.sffca.ip.att.net (12.123.13.61) 4.501 ms 4.559 ms 4.497 ms
12 12.244.72.205 (12.244.72.205) 22.384 ms 22.640 ms 22.052 ms
13 12.244.67.13 (12.244.67.13) 23.134 ms 22.906 ms 22.962 ms
14 12.244.67.9 (12.244.67.9) 15.000 ms 14.966 ms 14.855 ms
15 12.244.67.5 (12.244.67.5) 15.214 ms 14.805 ms 14.428 ms
16 12.244.67.66 (12.244.67.66) 14.930 ms 15.345 ms 15.680 ms
17 12.244.67.70 (12.244.67.70) 16.379 ms 15.785 ms 15.958 ms
18 12.244.98.229 (12.244.98.229) 24.405 ms 24.324 ms 24.534 ms
19 12-235-203-148.client.attbi.com (12.235.203.148) 450.916 ms 131.361 ms 89.914 ms

So... everything on the network is fine until it gets to your NIC and you blame ATTBI.

nice.

Reinstall NIC drivers
reinstall Client for MS Networks and TCP/IP
change NIC slots on the mo/bo or replace the NIC

 

[PoPPeR]

simply wait for it to clear up... that's something i've been hearing for 2 weeks. I get 50ms in the morning, 100 in the afternoon, then it skyrockets to 400ms. I dont' even care what your opinion is of me anymore. So I don't understand how a tracert works, your co-workers told me to do a tracert, i gave them the results, they said well it looks fine, yet i still experience crappy service to just about every internet portal out there. I don't have a right to be pissed at you. I'm pissed at the service your company is providing, and they are paying you to deal with people like me about the problems i'm experiencing. Obviously there is a problem. Whether or not you attempt to help me fix it is your decision. You don't want my business, fine. Not a big loss to you, big loss to me. ATT wins again. Broadbandreports have a generally bad report for ATT service in my direct area. I now see that's true. You think I give a rats ass if a Tier2 Senior ATTBi Tech with more authority then God doesn't like me? I didn't order this service so I could call tech support and have a pleasant conversation with you

 

[PoPPeR]

Originally posted by: ffmcobalt

Originally posted by: PoPPeR
you call me an idiot, sorry that I don't work for ATT, know exactly how the internet works, or understand why someone who lives 10 minutes from me gets lower pings. Its called a paying customer. I went to school to specialize in another profession, not to study giant broadband networks. That's your job. I, as a paying customer, have the right to demand that you do your job, seeing how your taking my money. If i'm not satisfied with the service, what do you want me to do? I asked once, nothing improved, asked twice, nothing improved. okay, so its not your fault. Its my fault i'm getting bad service?

If you don't know how the internet works, why don't you simply listen to one who does? Or to the people who provide your internet service? You call up ATTBI and bitch at them. They tell you that it's not their problem, and prove it to you. Then you basically say that you know better than they do by refusing to believe that it's anyone's but ATTBI's problem.

Then you say that you don't know much about the internet.

Do you ever take your car into the shop and tell the ASE Certified mechanic that he's wrong?

No, but at least they'd tell me or advise me further. I kept asking you guys what to do, you told me apparently it wasn't located inside the ATT network. Wow, thanks

 

[PoPPeR]

Originally posted by: ffmcobalt

Originally posted by: PoPPeR
1 vlan206.inr-203-eva.Berkeley.EDU (128.32.206.1) 0.633 ms 0.486 ms 0.450 ms
2 vlan210.inr-202-doecev.Berkeley.EDU (128.32.255.9) 0.586 ms 0.435 ms 0.555 ms
3 gigE6-0-0.inr-new-666-doecev.Berkeley.EDU (128.32.0.249) 0.850 ms 0.496 ms 0.534 ms
4 qsv-juniper--ucb-gw.calren2.net (128.32.0.70) 2.271 ms 2.485 ms 2.321 ms
5 POS1-0.hsipaccess1.SanJose1.Level3.net (209.247.159.109) 2.524 ms 2.473 ms 2.783 ms
6 ae0-53.gar1.SanJose1.level3.net (64.159.2.76) 3.450 ms 3.029 ms 3.026 ms
7 so-6-0-0.edge1.SanJose1.level3.net (209.244.3.138) 3.307 ms 3.553 ms 3.324 ms
8 att-level3-oc48.SanJose1.Level3.net (209.0.227.30) 4.437 ms 4.732 ms 4.762 ms
9 tbr1-p012201.sffca.ip.att.net (12.123.13.189) 5.197 ms 4.981 ms 5.191 ms
10 gbr2-p10.sffca.ip.att.net (12.122.11.70) 4.483 ms 4.597 ms 4.544 ms
11 gar1-p370.sffca.ip.att.net (12.123.13.61) 4.501 ms 4.559 ms 4.497 ms
12 12.244.72.205 (12.244.72.205) 22.384 ms 22.640 ms 22.052 ms
13 12.244.67.13 (12.244.67.13) 23.134 ms 22.906 ms 22.962 ms
14 12.244.67.9 (12.244.67.9) 15.000 ms 14.966 ms 14.855 ms
15 12.244.67.5 (12.244.67.5) 15.214 ms 14.805 ms 14.428 ms
16 12.244.67.66 (12.244.67.66) 14.930 ms 15.345 ms 15.680 ms
17 12.244.67.70 (12.244.67.70) 16.379 ms 15.785 ms 15.958 ms
18 12.244.98.229 (12.244.98.229) 24.405 ms 24.324 ms 24.534 ms
19 12-235-203-148.client.attbi.com (12.235.203.148) 450.916 ms 131.361 ms 89.914 ms

So... everything on the network is fine until it gets to your NIC and you blame ATTBI.

nice.

Reinstall NIC drivers
reinstall Client for MS Networks and TCP/IP
change NIC slots on the mo/bo or replace the NIC

I would have considered that when the problems first started if they were continuous. Why does this problem only happen at night. Why did the Tier2 tech person not advise me like this?

 

[KK]

Originally posted by: ffmcobalt

Originally posted by: PoPPeR
you call me an idiot, sorry that I don't work for ATT, know exactly how the internet works, or understand why someone who lives 10 minutes from me gets lower pings. Its called a paying customer. I went to school to specialize in another profession, not to study giant broadband networks. That's your job. I, as a paying customer, have the right to demand that you do your job, seeing how your taking my money. If i'm not satisfied with the service, what do you want me to do? I asked once, nothing improved, asked twice, nothing improved. okay, so its not your fault. Its my fault i'm getting bad service?

If you don't know how the internet works, why don't you simply listen to one who does? Or to the people who provide your internet service? You call up ATTBI and bitch at them. They tell you that it's not their problem, and prove it to you. Then you basically say that you know better than they do by refusing to believe that it's anyone's but ATTBI's problem.

Then you say that you don't know much about the internet.

Do you ever take your car into the shop and tell the ASE Certified mechanic that he's wrong?

Do you ever think that people will lie to you to just make you go away? Do you ever want a second opinion on your ASE Certified mechanic? Do you always believe what the Best Buy employee will tell you? Also, you said it before, you have to perform on your job. How do you get evaluated, by how long you are on the phone with the customers. You were bitching because you were going to get shltcanned because you took the time to work the problems your customers had, either that or you got a serious stuttering problem. anywho, don't you think some of your co workers who wanna impress management while cut corners?

KK

 

[Mill]

Instead of being a dickwad Nik why don't you try to help by getting him to post the tracert like I did and the we can explain to him that the problem is his computer or NIC which is obvious because the LAG is occuring on the final step which is his computer.

If you don't want to help him then don't. Why do you have to be a snarling ass everytime someone doesn't understand things? I could baffle you with things you wouldn't understand or wouldn't know how to deal with but I wouldn't browbeat you over it.

Damn dude get off the computer and go screw your girlfriend or jack off. I seriously think you need help? Are you drunk? Check out AA. Really get some help.

Edit- Why couldn't it be a problem with his Cable Modem?

 

[KK]

Originally posted by: ffmcobalt

Originally posted by: KK

Originally posted by: PoPPeR
so as someone who works for ATT... since i'm experiencing bad service, your solution to my problem is?

First off, I believe the company's name is Comcast now. Also customer support is pretty much all contracted out so they don't care.

KK

Wrong. ATTBI customers will still be ATTBI customers and won't be "moved over" to Comcast. All customers joining will be Comcast customers using ATTBI equipment.

But ATTBI is comcast, AT&T has no cable anymore. Am I right in thinking this.

KK

 

[ScottyB]

Wow, mine looks bad.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Scotty>tracert

Usage: tracert [-d] [-h maximum_hops] [-j host-list] [-w timeout] target_name

Options:
-d Do not resolve addresses to hostnames.
-h maximum_hops Maximum number of hops to search for target.
-j host-list Loose source route along host-list.
-w timeout Wait timeout milliseconds for each reply.

C:\Documents and Settings\Scotty>tracert yahoo.com

Tracing route to yahoo.com [66.218.71.198]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 205 ms 175 ms 172 ms adsl-65-42-243-254.dsl.lgnnmi.ameritech.net [65.
42.243.254]
3 112 ms 52 ms 35 ms dist1-vlan60.lgtpmi.ameritech.net [65.42.245.242
]
4 26 ms 15 ms 28 ms bb1-fa2-0-0.lgtpmi.ameritech.net [65.42.245.115]

5 59 ms 52 ms 106 ms sl-gw4-roa-3-0-ts11.sprintlink.net [160.81.230.1
93]
6 338 ms 467 ms 279 ms sl-bb22-roa-2-1.sprintlink.net [144.232.17.205]

7 27 ms 51 ms 60 ms sl-bb22-chi-6-1.sprintlink.net [144.232.8.81]
8 50 ms 47 ms 69 ms 144.232.8.186
9 127 ms 153 ms 183 ms so-4-0-0.mp1.chicago1.level3.net [209.247.10.161
]
10 324 ms 256 ms 277 ms so-3-0-0.mp1.sanjose1.level3.net [64.159.1.129]

11 267 ms 83 ms 122 ms gige9-1.ipcolo3.sanjose1.level3.net [64.159.2.73
]
12 101 ms 93 ms 118 ms unknown.level3.net [64.152.69.30]
13 91 ms 139 ms 114 ms w1.rc.vip.scd.yahoo.com [66.218.71.198]

Trace complete.

 

[virtuamike]

Originally posted by: PoPPeR
1 vlan206.inr-203-eva.Berkeley.EDU (128.32.206.1) 0.633 ms 0.486 ms 0.450 ms
2 vlan210.inr-202-doecev.Berkeley.EDU (128.32.255.9) 0.586 ms 0.435 ms 0.555 ms
3 gigE6-0-0.inr-new-666-doecev.Berkeley.EDU (128.32.0.249) 0.850 ms 0.496 ms 0.534 ms
4 qsv-juniper--ucb-gw.calren2.net (128.32.0.70) 2.271 ms 2.485 ms 2.321 ms
5 POS1-0.hsipaccess1.SanJose1.Level3.net (209.247.159.109) 2.524 ms 2.473 ms 2.783 ms
6 ae0-53.gar1.SanJose1.level3.net (64.159.2.76) 3.450 ms 3.029 ms 3.026 ms
7 so-6-0-0.edge1.SanJose1.level3.net (209.244.3.138) 3.307 ms 3.553 ms 3.324 ms
8 att-level3-oc48.SanJose1.Level3.net (209.0.227.30) 4.437 ms 4.732 ms 4.762 ms
9 tbr1-p012201.sffca.ip.att.net (12.123.13.189) 5.197 ms 4.981 ms 5.191 ms
10 gbr2-p10.sffca.ip.att.net (12.122.11.70) 4.483 ms 4.597 ms 4.544 ms
11 gar1-p370.sffca.ip.att.net (12.123.13.61) 4.501 ms 4.559 ms 4.497 ms
12 12.244.72.205 (12.244.72.205) 22.384 ms 22.640 ms 22.052 ms
13 12.244.67.13 (12.244.67.13) 23.134 ms 22.906 ms 22.962 ms
14 12.244.67.9 (12.244.67.9) 15.000 ms 14.966 ms 14.855 ms
15 12.244.67.5 (12.244.67.5) 15.214 ms 14.805 ms 14.428 ms
16 12.244.67.66 (12.244.67.66) 14.930 ms 15.345 ms 15.680 ms
17 12.244.67.70 (12.244.67.70) 16.379 ms 15.785 ms 15.958 ms
18 12.244.98.229 (12.244.98.229) 24.405 ms 24.324 ms 24.534 ms
19 12-235-203-148.client.attbi.com (12.235.203.148) 450.916 ms 131.361 ms 89.914 ms

Unless I'm reading this wrong, the hop from gateway to client is getting horrible ping, in which case the gateway he's on is pinging terrible (am I correct in assuming #19 is his modem and not the actual PC?). Which would imply the block he's on is overloaded, typical cable nighttime lag. Personally, if I found a slow route between my DSL modem and the ISP gateway for my block, I'd sure as hell think I'd have a right to bitch.

** edit **

OK, this is just personal curiosity at this point. Why did changing slots on NIC improve his ping? To me it seems that just power cycling his PC (thus refreshing cable connection) had more to do with it than moving a NIC around. I dunno, my brain is fuzzy right now, not thinking too good. Yes, I figured out that #19 is NIC and not modem (dunno what I was thinking, like I said my brain is not working tonite).

 

[NikPreviousAcct]

This is the first time I've been on my computer since early this morning, and that was only to check a few things.

Instead of being a nice guy constantly to dickwads all the time, I'd like to, just once, lay into a customer on the phone who won't back down.

Anyway, is this post in a tech support forum? No. It's in Off Topic. Most people who post sh|t like this in here just come in to rant. Besides, when he asked what to do next, I told him.


PoPPeR, if you don't like the service, get another one -but don't blame ATTBI. It's not ATTBI's problem, and we've proven it. It's not our responsibility to tell you jack crap more than "our service looks fine" because we're not the USA of the internet. It's not our job to go around telling you what's wrong with your computer. If you come to us with a problem on your computer, that's not our problem to fix. If you come to us and we provide you a connection to the internet but the company (att.net) that we lease our bandwidth from has problems, that's not our problem either.

 

[PoPPeR]

Well I changed the PCI slot my ethernet card was in, my pings dropped to about 150 from 400. Thanks nik, maybe its time to teach your fellow co-workers how to do their job because they sure as hell don't know how to advise other then saying its not their problem

 

[NikPreviousAcct]

Originally posted by: KK

Originally posted by: ffmcobalt

Originally posted by: KK

Originally posted by: PoPPeR
so as someone who works for ATT... since i'm experiencing bad service, your solution to my problem is?

First off, I believe the company's name is Comcast now. Also customer support is pretty much all contracted out so they don't care.

KK

Wrong. ATTBI customers will still be ATTBI customers and won't be "moved over" to Comcast. All customers joining will be Comcast customers using ATTBI equipment.

But ATTBI is comcast, AT&T has no cable anymore. Am I right in thinking this.

KK

In a matter of speaking, yes. You cannot sign up for ATT Broadband Internet anymore. You can only sign up for Comcast High Speed Internet. But I, being a previous ATTBI customer, will always be an ATTBI customer and (from what I am told by the higher-ups or unless something changes) will never see the word "Comcast" on my bill. Which I am thankful for.

 

[NikPreviousAcct]

Originally posted by: PoPPeR
Well I changed the PCI slot my ethernet card was in, my pings dropped to about 150 from 400. Thanks nik, maybe its time to teach your fellow co-workers how to do their job because they sure as hell don't know how to advise other then saying its not their problem

I wish that were possible.

 

[Mill]

Originally posted by: ffmcobalt

Originally posted by: PoPPeR
Well I changed the PCI slot my ethernet card was in, my pings dropped to about 150 from 400. Thanks nik, maybe its time to teach your fellow co-workers how to do their job because they sure as hell don't know how to advise other then saying its not their problem

I wish that were possible.

See Nik all you had to do was be nice and ask him to post a tracert like I did and then work from there. No one is doubting your knowledge because I have seen you help a lot of people. Just try to work on the attitude a little.