Re: Wierd results from tracert, what do u think

976 Views 4 Replies 2 Participants Last post by johnwill, May 31, 2008

maikumd

Discussion Starter · May 30, 2008 (Edited)

Re: Wierd results from tracert, what do u think

I have this same exact problem.

Router: Netgear WGR614v6
OS: xp pro service pack 3
ISP: Brighthouse

I'm beginning to think it's the router and I'm thinking about just buying the WRT54GL from Linksys. In the meantime I've tried disabling all firewalls portforwarding all the ports required by warcraft 3 and I'm still dropping from games. It's annoying so I'd like some help trying to figure it out :grin:

Here my ping and tracert to useast.battle.net

ping useast.battle.net

Pinging useast.battle.net [63.240.202.121] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 63.240.202.121:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

tracert useast.battle.net

Tracing route to useast.battle.net [63.240.202.121]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 9 ms 9 ms 9 ms 1-208.186-72.tampabay.res.rr.com [72.186.208.1]

3 15 ms 9 ms 12 ms gig12-0-0-2701.tampfledc-rtr1.tampflrdc.rr.com [
65.32.24.42]
4 12 ms 11 ms 9 ms ge2-2-0.tampfledc-rtr3.tampflrdc.rr.com [65.32.1
3.62]
5 14 ms 11 ms 9 ms te-3-1.car1.Tampa1.Level3.net [63.208.0.85]
6 10 ms 9 ms 9 ms ae-2-5.bar1.Tampa1.Level3.net [4.69.133.50]
7 40 ms 36 ms 35 ms ae-6-6.ebr2.Atlanta2.Level3.net [4.69.137.114]
8 29 ms 28 ms 28 ms ae-12-51.car2.Atlanta1.Level3.net [4.68.103.3]
9 37 ms 28 ms 29 ms 192.205.34.61
10 47 ms 48 ms 47 ms tbr2.attga.ip.att.net [12.122.96.70]
11 46 ms 47 ms 48 ms cr1.attga.ip.att.net [12.122.17.89]
12 47 ms 44 ms 44 ms cr2.wswdc.ip.att.net [12.122.1.174]
13 47 ms 47 ms 47 ms tbr1.wswdc.ip.att.net [12.122.16.54]
14 44 ms 47 ms 44 ms 12.123.8.33
15 57 ms 212 ms 213 ms 12-122-254-98.attens.net [12.122.254.98]
16 48 ms 47 ms 47 ms mdf001c7613r0003-gig-10-1.wdc1.attens.net [63.24
0.193.10]
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

I'll post the line quality test when it's done.

edit: http://www.dslreports.com/linequality/43a2589b75a2/2390159

See less See more

Save

Status: Not open for further replies.

1 - 5 of 5 Posts

johnwill

· #2 · May 30, 2008

Re: Wierd results from tracert, what do u think

Even though it appears you're having the same problem, please start a new thread when you have a new issue. It's very difficult to keep two problems straight and who's working on what in a single thread.

I've created a new thread for your issue here.

Note: You will need to post complete details of your configuration and your specific issue in this new thread for us to help you.

Thanks for your cooperation.

Save

johnwill

· #3 · May 30, 2008

Re: Wierd results from tracert, what do u think

Try your tests connected directly to the broadband modem, if it doesn't exhibit the issue, you've found the issue.

Save

maikumd

Discussion Starter · #4 · May 31, 2008

Re: Wierd results from tracert, what do u think

I plugged it into the modem and got the same results. Hmmm?

Save

johnwill

· #5 · May 31, 2008

Re: Wierd results from tracert, what do u think

FWIW, I get the same results.

C:\>ping useast.battle.net

Pinging useast.battle.net [63.240.202.120] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 63.240.202.120:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

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

C:\>useast.battle.net
'useast.battle.net' is not recognized as an internal or external command,
operable program or batch file.

C:\>tracert useast.battle.net

Tracing route to useast.battle.net [63.240.202.120]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms ZyXEL [192.168.0.1]
2 1 ms <1 ms <1 ms ActionTec [192.168.1.1]
3 6 ms 4 ms 4 ms L100.VFTTP-09.PHLAPA.verizon-gni.net [72.78.224.1]
4 5 ms 4 ms 4 ms G2-0-609.LCR-06.PHLAPA.verizon-gni.net [130.81.129.142]
5 3 ms 4 ms 4 ms 130.81.28.156
6 5 ms 4 ms 5 ms 0.so-6-0-0.XL2.PHL6.ALTER.NET [152.63.3.81]
7 9 ms 9 ms 9 ms 0.so-6-0-0.XL4.IAD8.ALTER.NET [152.63.0.130]
8 11 ms 9 ms 9 ms 0.ge-7-0-0.BR2.IAD8.ALTER.NET [152.63.41.157]
9 11 ms 9 ms 9 ms 192.205.35.37
10 13 ms 12 ms 12 ms tbr2.wswdc.ip.att.net [12.123.8.102]
11 9 ms 10 ms 9 ms 12.123.8.37
12 13 ms 12 ms 12 ms 12-122-254-98.attens.net [12.122.254.98]
13 11 ms 12 ms 12 ms mdf001c7613r0004-gig-12-1.wdc1.attens.net [63.240.193.14]
14 * * * Request timed out.
15 * * * Request timed out.
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.

See less See more

Save

1 - 5 of 5 Posts

Status: Not open for further replies.

Top Contributors this Month