Is this my problem or Time Warner's?

Phishie · Nov 15, 2007

So over the past few days I've been having really crappy connection issues. My connection can be described as intermittent. Here is a message I've sent to Time Warner.

I want your opinion on what you think the problem is. Extra points to anybody who can directly help me solve this problem.

I've been having intermittent connectivity issues over the past three days. I have a high understanding of computers and networking but I can't solve this problem. Windows is reporting that my Local Area Network has limited or no connectivity. I've done everything. One click solutions. I've simplified the problem by removing my router and directly connecting my computer to the modem. I replaced the ethernet patch cable. Released/Renewed IP addresses. Etc...

Here is some data that may help in this investigation.

Windows IP Configuration

Host Name . . . . . . . . . . . . : Phishie
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : dc.rr.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : dc.rr.com
Description . . . . . . . . . . . : Generic Marvell Yukon 88E8056 based
Ethernet Controller
Physical Address. . . . . . . . . : 00-19-21-E5-48-7A
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 75.85.205.30
Subnet Mask . . . . . . . . . . . : 255.255.248.0
Default Gateway . . . . . . . . . : 75.85.200.1
DHCP Server . . . . . . . . . . . : 10.52.32.1
DNS Servers . . . . . . . . . . . : 66.75.164.90
66.75.164.89
Lease Obtained. . . . . . . . . . : Thursday, November 15, 2007 7:37:42
AM
Lease Expires . . . . . . . . . . : Friday, November 16, 2007 7:37:42 AM

The following traces were done on 11/15/07 around 1PM:

Tracing route to forums.majorgeeks.com [74.86.201.210]
over a maximum of 30 hops:

1 6 ms 6 ms 13 ms 10.52.32.1
2 * 6 ms * GIG0-3.INDICA1-UBR3.dc.rr.com [66.74.96.105]
3 * 16 ms 27 ms cpe-66-74-96-177.dc.rr.com [66.74.96.177]
4 11 ms * 15 ms cpe-66-74-96-110.dc.rr.com [66.74.96.110]
5 * * * Request timed out.
6 * 26 ms 28 ms SRP4-0-0.PLDSCA1-RTR1.dc.rr.com [66.74.96.10]
7 14 ms 14 ms * te-4-1.car1.Tustin1.Level3.net [4.71.104.157]
8 14 ms 14 ms 18 ms ae-11-11.car2.Tustin1.Level3.net [4.69.132.222]

9 51 ms 53 ms 55 ms ae-4-4.ebr1.Dallas1.Level3.net [4.69.132.226]
10 * 46 ms 53 ms ae-1-55.edge3.Dallas1.Level3.net [4.68.122.146]

11 67 ms 60 ms 51 ms te7-2.cer01.dal01.dallas-border.com [4.71.198.18
]
12 * * 53 ms po55.fcr03.dal01.dallas-datacenter.com [66.228.1
18.182]
13 60 ms 53 ms 53 ms majorgeeks.com [74.86.201.210]

Trace complete.

Tracing route to www.l.google.com [74.125.19.104]
over a maximum of 30 hops:

1 7 ms 7 ms 13 ms 10.52.32.1
2 11 ms 16 ms * GIG0-3.INDICA1-UBR3.dc.rr.com [66.74.96.105]
3 23 ms * * cpe-66-74-96-177.dc.rr.com [66.74.96.177]
4 10 ms 8 ms 20 ms cpe-66-74-96-110.dc.rr.com [66.74.96.110]
5 * 20 ms * cpe-66-74-96-62.dc.rr.com [66.74.96.62]
6 22 ms * 16 ms SRP4-0-0.PLDSCA1-RTR1.dc.rr.com [66.74.96.10]
7 * 13 ms 13 ms ae-5-0.cr0.lax30.tbone.rr.com [66.109.6.64]
8 88 ms 115 ms * ae-5-0.cr0.dca20.tbone.rr.com [66.109.6.3]
9 84 ms 97 ms 81 ms ae-1-0.pr0.dca10.tbone.rr.com [66.109.6.165]
10 81 ms * 83 ms 66.109.9.66
11 82 ms * 85 ms 216.239.48.110
12 * 109 ms * 209.85.130.17
13 102 ms 81 ms 84 ms 209.85.130.12
14 * 86 ms 93 ms 209.85.248.221
15 94 ms 85 ms * 64.233.174.80
16 * 95 ms 96 ms 209.85.251.94
17 84 ms 84 ms * cf-in-f104.google.com [74.125.19.104]
18 85 ms 90 ms * cf-in-f104.google.com [74.125.19.104]
19 95 ms 83 ms * cf-in-f104.google.com [74.125.19.104]
20 * 85 ms * cf-in-f104.google.com [74.125.19.104]
21 84 ms 83 ms * cf-in-f104.google.com [74.125.19.104]
22 86 ms 85 ms 85 ms cf-in-f104.google.com [74.125.19.104]

Trace complete.

The following trace was done on 11/14/07 around 4PM through a router

Tracing route to us.logon.worldofwarcraft.com [12.129.224.113] over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 192.168.1.1
2 14 ms 6 ms * 10.52.32.1
3 7 ms 7 ms 7 ms GIG0-3.INDICA1-UBR3.dc.rr.com [66.74.96.105]
4 * 14 ms * cpe-66-74-96-177.dc.rr.com [66.74.96.177]
5 8 ms * 11 ms cpe-66-74-96-110.dc.rr.com [66.74.96.110]
6 6 ms 7 ms 15 ms cpe-66-74-96-62.dc.rr.com [66.74.96.62]
7 22 ms 15 ms * SRP4-0-0.PLDSCA1-RTR1.dc.rr.com [66.74.96.10]
8 15 ms 16 ms 22 ms te-4-1.car1.Tustin1.Level3.net [4.71.104.157]
9 * 29 ms 17 ms ae-3-3.ebr1.LosAngeles1.Level3.net [4.69.132.218
]
10 51 ms 57 ms 30 ms ae-11-53.car1.LosAngeles1.Level3.net [4.68.102.7
6]
11 18 ms 14 ms 13 ms 192.205.33.229
12 29 ms 16 ms 14 ms 12.127.3.210
13 14 ms * 17 ms 12.127.3.185
14 19 ms * 20 ms 12.122.255.74
15 * 38 ms 20 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.12
9.193.246]
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
Click to expand...

Any help or suggestions is appreciated. Also, if you have comments on my tracert, please post. I have a pretty good understanding of tracert data but I am not completely sure about it.

Thanks!

Phishie · Nov 16, 2007

Wow please delete this, after a simple disk cleanup and restart the symptoms seem to have completely disappeared... =/

Log in or Sign up

Is this my problem or Time Warner's?

Phishie Private E-2

Phishie Private E-2