icey
Team oPg
Full Member
Posts: 154
|
 |
« on: September 20, 2007, 11:07:56 PM » |
|
I've never had issues with comcast getting to our opg public server or the hd-gaming private...but apparently that has changed...
here is a beauty of a tracert (from the cable modem out) to the hd-gaming vent...
C:\Documents and Settings\Eric>tracert cowboy.hidef-voice.com
Tracing route to cowboy.hidef-voice.com [66.128.62.218]
over a maximum of 30 hops:
1 * * * Request timed out.
2 7 ms * 9 ms ge-2-2-ur01.arvada.co.denver.comcast.net [68.86.
105.161]
3 4294965019 ms * 4294965019 ms te-9-1-ur02.arvada.co.denver.comcast
.net [68.86.103.126]
4 4294965018 ms 4294965018 ms 4294965018 ms te-8-2-ar01.aurora.co.denver.c
omcast.net [68.86.103.41]
5 4294965019 ms 4294965019 ms 4294965020 ms 68.86.128.53
6 4294965020 ms 4294965021 ms 4294965019 ms 12.116.159.5
7 4294965039 ms 4294965039 ms 4294965042 ms tbr2.dvmco.ip.att.net [12.122.
86.254]
8 4294965457 ms 4294965448 ms 4294965453 ms tbr2.dlstx.ip.att.net [12.122.
12.125]
9 28 ms 4294965040 ms 4294965039 ms 12.122.100.69
10 * * * Request timed out.
11 393 ms 4294965410 ms 4294965411 ms border3.tge3-1-bbnet1.ext1.dal.pnap.
net [216.52.191.22]
12 28 ms 4294965040 ms 4294965041 ms globalcon-9.border3.ext1.dal.pnap.ne
t [63.251.32.102]
13 439 ms 435 ms 4294965475 ms 66.128.62.218
SWEET...
here's the opg server (pub)
C:\Documents and Settings\Eric>tracert 72.5.102.48
Tracing route to c-72-5-102-48.internap-denver.nuclearfallout.net [72.5.102.48]
over a maximum of 30 hops:
1 * * * Request timed out.
2 9 ms 4294965018 ms * ge-2-2-ur01.arvada.co.denver.comcast.net [
68.86.105.161]
3 7 ms 2293 ms * te-9-1-ur02.arvada.co.denver.comcast.net [68.86.
103.126]
4 2294 ms 7 ms 9 ms te-8-2-ar01.aurora.co.denver.comcast.net [68.86.
103.41]
5 4294965426 ms 4294965430 ms 423 ms GE-6-2-ur02.arvada.co.denver.comcast
.net [68.86.104.42]
6 4294965019 ms 8 ms 10 ms 12.124.157.53
7 4294965399 ms 380 ms 383 ms br2.dvmco.ip.att.net [12.127.4.158]
8 4294965022 ms 9 ms 2296 ms tbr2.dvmco.ip.att.net [12.122.1.38]
9 416 ms 437 ms 451 ms gar2.dvmco.ip.att.net [12.123.207.165]
10 468 ms 445 ms 429 ms 12.124.158.126
11 8 ms 9 ms 10 ms border9.ge3-1-bbnet1.den.pnap.net [216.52.40.14]
12 440 ms 434 ms 2712 ms c-72-5-102-48.internap-denver.nuclearfallout.net
[72.5.102.48]
Trace complete.
OPG Private (hd-gaming)
C:\Documents and Settings\Eric>tracert 72.5.2.34
Tracing route to 72.5.2.34 over a maximum of 30 hops
1 * * * Request timed out.
2 8 ms 4294965020 ms * ge-2-2-ur01.arvada.co.denver.comcast.net [
68.86.105.161]
3 * 4294965020 ms * te-9-1-ur02.arvada.co.denver.comcast.net [
68.86.103.126]
4 4294965026 ms 8 ms 9 ms te-8-2-ar01.aurora.co.denver.comcast.net [
68.86.103.41]
5 8 ms 4294965018 ms 4294965025 ms 68.86.103.170
6 11 ms 13 ms 4294965025 ms 12.116.159.5
7 4294965409 ms 4294965406 ms 4294965399 ms tbr1.dvmco.ip.att.net [12.122.
86.250]
8 4294965054 ms 36 ms 4294965053 ms tbr2.sffca.ip.att.net [12.122.12.133
]
9 41 ms 4294965046 ms 4294965049 ms gbr2.sffca.ip.att.net [12.122.11.86]
10 4294965397 ms 4294965398 ms 4294965421 ms gar1.sffca.ip.att.net [12.123.
213.69]
11 * * * Request timed out.
12 4294965048 ms 4294965048 ms 4294965047 ms border2.pc-2-bbnet2.sfo002.pna
p.net [63.251.63.82]
13 37 ms 4294965053 ms 38 ms 72.5.2.34
Trace complete.
So , apparently the routers at & the similar are POSs....gg!
ge-2-2-ur01.arvada.co.denver.comcast.net [68.86.105.161]
|
|
|
|
|
Logged
|
|
|
|
Fuzzeh_Panda
Ass pirate.
TF2 Admins
Hero Member
Posts: 711
There's no fuzzier than Fuzzeh.
|
|
« Reply #1 on: September 20, 2007, 11:27:10 PM » |
|
That bests my tracert. Call them, and yell loudly. I called (not Comcast, but whoever makes my interwebs), and it was fixed magically over a series of weeks! Well worth the effort to not have 500+ ping...
|
|
|
|
|
Logged
|
|
|
|
|
Jakestaby
Guest
|
|
« Reply #2 on: September 20, 2007, 11:35:51 PM » |
|
Do you live in Utah? Let me know. I had a similar problem a couple years ago and called probably 80 times and had over 15 techs come to my place. Finally a guy I know gave me the name of one of the upper level techs. I called him (he works nights thankfully) and he verified the problem. It was fixed within a week.
|
|
|
|
|
Logged
|
|
|
|
icey
Team oPg
Full Member
Posts: 154
|
|
« Reply #3 on: September 21, 2007, 12:38:49 PM » |
|
It actually appears to be fixed again. gg comcast. I can't complain too much as that is the 1st time I've had an issue with them in 2 yrs so apparently its all good and I think they fixed the crap ass router somewhere in my routes  |
|
|
|
|
Logged
|
|
|
|
DoWork
oPg Server Admins
Sr. Member
Posts: 439
|
 |
« Reply #4 on: September 22, 2007, 02:42:25 PM » |
|
I have verizon fiber optics... I have never once had a problem. I had it for about 6 months and that thing moves... never lag. only down when they update it... but that takes 15 minutes.
|
|
|
|
|
Logged
|
|
|
|
|
b.ho
Guest
|
|
« Reply #5 on: September 22, 2007, 04:08:30 PM » |
|
as of this moment. my ping is horrible. dam comcast. i was getting 200+ latency and ping on the opg server.
|
|
|
|
|
Logged
|
|
|
|
|
Jakestaby
Guest
|
|
« Reply #6 on: September 23, 2007, 12:22:12 AM » |
|
I have verizon fiber optics... I have never once had a problem. I had it for about 6 months and that thing moves... never lag. only down when they update it... but that takes 15 minutes.
Where do you live? |
|
|
|
|
Logged
|
|
|
|
|
b.ho
Guest
|
|
« Reply #7 on: September 23, 2007, 01:28:18 AM » |
|
in sandy. near hillcrest.
|
|
|
|
|
Logged
|
|
|
|
|
Latro
Guest
|
|
« Reply #8 on: September 23, 2007, 06:47:25 AM » |
|
DoWork lives in Delaware. We East Coasters love our FIOS.
|
|
|
|
|
Logged
|
|
|
|
DoWork
oPg Server Admins
Sr. Member
Posts: 439
|
|
« Reply #9 on: September 23, 2007, 08:33:24 AM » |
|
yeah like latro said I live in delaware.
|
|
|
|
|
Logged
|
|
|
|
|
b.ho
Guest
|
|
« Reply #10 on: September 23, 2007, 10:26:46 AM » |
|
screw you guys!!!! gawsh.
|
|
|
|
|
Logged
|
|
|
|
|
