Quote:
Originally Posted by Mezmonk
I have Cox as well.. Houston / Conroe Area.
You mentioned above a lot of firewall info, how about your router? If you have one. As a network engineer trainer I tell my students to follow the points of error.. NIC card, Network Cable, Router/Firewall, Cable to Cable Modem etc... Might wanna try to go to www.dslreports.com and test your connection they have many tools there.
|
luckily i have a friend who is about to graduate with a degree in netowrking security

he is my mentor for everything internet related.
to answer your question, my router is the next thing i am checking. i have 2 NICs i have tried both and the problem recurrs with both NICS. Network cable is definetly a possibility but i have ruled it out because our entire netowkr experiences intermittent connectivity but it is hard to test since i am the only one that does anything that requires a constant D/L, U/L stream. modem... god i only hope its not the modem... i dont want to have to replace it... but when i plug my computer ito the modem directly i wil find out if its my router and i will find out if its my modem or my ISP. as for my connection... here is a pathping log i performed for arenanets information....
Tracing route to 206-127-148-36.plaync.com [206.127.148.36]
over a maximum of 30 hops:
0 trent [***.***.*.*]
1 * * ***.***.*.*
2 10.248.144.1
3 68.1.200.245
4 * dllsdsrc02-pos0701.rd.dl.cox.net [68.1.206.21]
5 so-3-3-0-0.gar2.Dallas1.Level3.net [4.78.234.5]
6 ae-1-52.bbr2.Dallas1.Level3.net [4.68.122.33]
7 ae-0-0.bbr1.LosAngeles1.Level3.net [64.159.1.125]
8 ge-2-1-56.car3.LosAngeles1.Level3.net [4.68.102.165]
9 * * *
Computing statistics for 225 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 trent [***.***.*.*]
0/ 100 = 0% |
1 8ms 0/ 100 = 0% 0/ 100 = 0% ***.***.*.*
0/ 100 = 0% |
2 17ms 0/ 100 = 0% 0/ 100 = 0% 10.248.144.1
0/ 100 = 0% |
3 19ms 0/ 100 = 0% 0/ 100 = 0% 68.1.200.245
0/ 100 = 0% |
4 30ms 0/ 100 = 0% 0/ 100 = 0% dllsdsrc02-pos0701.rd.dl.cox.net [
68.1.206.21]
0/ 100 = 0% |
5 36ms 0/ 100 = 0% 0/ 100 = 0% so-3-3-0-0.gar2.Dallas1.Level3.net
[4.78.234.5]
0/ 100 = 0% |
6 32ms 0/ 100 = 0% 0/ 100 = 0% ae-1-52.bbr2.Dallas1.Level3.net [4
.68.122.33]
0/ 100 = 0% |
7 61ms 0/ 100 = 0% 0/ 100 = 0% ae-0-0.bbr1.LosAngeles1.Level3.net
[64.159.1.125]
0/ 100 = 0% |
8 65ms 0/ 100 = 0% 0/ 100 = 0% ge-2-1-56.car3.LosAngeles1.Level3.
net [4.68.102.165]
100/ 100 =100% |
9 --- 100/ 100 =100% 0/ 100 = 0% trent [0.0.0.0]
Trace complete.
if you can read that up there^^^ you will see my connection ran perfect... low ping and everything... but the only variable was i ran that test at 3 am CST. here is another log i ran at 4 pm cst the next day or the day after that...
Tracing route to 206-127-148-36.plaync.com [206.127.148.36]
over a maximum of 30 hops:
0 trent [***.***.*.*]
1 ***.***.*.*
2 10.248.144.1
3 68.1.200.245
4 dllsdsrc02-pos0701.rd.dl.cox.net [68.1.206.21]
5 so-3-3-0-0.gar2.Dallas1.Level3.net [4.78.234.5]
6 ae-1-54.bbr2.Dallas1.Level3.net [4.68.122.97]
7 ae-0-0.bbr1.LosAngeles1.Level3.net [64.159.1.125]
8 ge-1-1-53.car3.LosAngeles1.Level3.net [4.68.102.69]
9 * * *
Computing statistics for 225 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 trent [***.***.*.*]
3/ 100 = 3% |
1 7ms 3/ 100 = 3% 0/ 100 = 0% ***.***.*.*
2/ 100 = 2% |
2 17ms 5/ 100 = 5% 0/ 100 = 0% 10.248.144.1
0/ 100 = 0% |
3 18ms 5/ 100 = 5% 0/ 100 = 0% 68.1.200.245
0/ 100 = 0% |
4 31ms 6/ 100 = 6% 1/ 100 = 1% dllsdsrc02-pos0701.rd.dl.cox.net [
68.1.206.21]
0/ 100 = 0% |
5 32ms 6/ 100 = 6% 1/ 100 = 1% so-3-3-0-0.gar2.Dallas1.Level3.net
[4.78.234.5]
0/ 100 = 0% |
6 32ms 6/ 100 = 6% 1/ 100 = 1% ae-1-54.bbr2.Dallas1.Level3.net [4
.68.122.97]
0/ 100 = 0% |
7 68ms 5/ 100 = 5% 0/ 100 = 0% ae-0-0.bbr1.LosAngeles1.Level3.net
[64.159.1.125]
0/ 100 = 0% |
8 68ms 5/ 100 = 5% 0/ 100 = 0% ge-1-1-53.car3.LosAngeles1.Level3.
net [4.68.102.69]
95/ 100 = 95% |
9 --- 100/ 100 =100% 0/ 100 = 0% trent [0.0.0.0]
Trace complete.
^^^ not such perfect results... one of the reasons im am completely counting out my computer/cable/firewall/virus protection as the problem is because as far as i can tell it affects our entire network, which as Mezmonk said, would leave my router, modem, or ISP as the culprit... another reason i am so quick to blame Cox is that they do not have a good track record in our area. Lots of outages, problems with customer service, overall seemingly incompetent people running the business here...
my condolences to everyone else who experiences this problem that keeps them from enjoying this fine game.