I am trying to connect to newegg.com and I keep getting timed out. Generally I would just assume this to be a problem with the modem/router, but I reset them and the problem persists.
I then decided to run a ping and I get a 'destination net unreachable error'. I ran a tracert to show you guys here. I am just curious as to whether the problem is something I can remedy or is out of my control.
It is probabally important to note that this is intermittent. Sometimes the site will work just fine (I have not had the opportunity to run a tracert during these times) and sometimes it times out.
Windows XP Professiona on a Dell Latitude D600.
[code:1:091b2c0deb]Tracing route to www.newegg.com [204.14.213.185]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 8 ms 6 ms 7 ms 74.128.18.233
4 13 ms 11 ms 16 ms 74.128.16.89
5 13 ms 24 ms 18 ms 74.128.8.97
6 25 ms 26 ms 23 ms so-7-1-0.gar2.Atlanta1.Level3.net [4.78.214.17]
7 25 ms 22 ms 46 ms uunet-level3-oc48.Atlanta1.Level3.net [4.68.127.178]
8 22 ms 24 ms 26 ms 0.so-2-2-0.XL2.ATL4.ALTER.NET [152.63.86.174]
9 48 ms 47 ms 57 ms 0.so-3-0-0.XL2.NYC1.ALTER.NET [152.63.29.113]
10 46 ms 59 ms 48 ms POS7-0.GW12.NYC1.ALTER.NET [152.63.29.197]
11 55 ms 72 ms 52 ms fibernet-gw.customer.alter.net [157.130.24.82]
12 204-13-14-36.ftgxip.net [204.13.14.36] reports: Destination net unreachable.
Trace complete.
[/code:1:091b2c0deb]
Edit: I was just able to run a tracert on one of the successful periods (connection works) and I still get the same tracert more or less.
I get a similar problem at the end of the tracert, however, my browser connection to newegg is fast & stable.
[code:1:71921cc967]
7 25 ms 26 ms 25 ms so5-2-0-622M.ar3.NYC1.gblx.net [67.17.104.246]
8 25 ms 27 ms 28 ms 192.205.33.53
9 28 ms 31 ms 27 ms tbr1-p010401.n54ny.ip.att.net [12.123.3.57]
10 27 ms 26 ms 25 ms ar2-p30.n54ny.ip.att.net [12.123.0.65]
11 28 ms 26 ms 26 ms 12.118.94.42
12 204-13-14-36.ftgxip.net [204.13.14.36] reports: Destination net unreachable.
Trace complete.
[/code:1:71921cc967]
I don't get a timeout at the beginning -- perhaps that indicates your problem, an intermitten one at an early hop. Perhaps checking with your ISP will help.
Greetings TomsHardware Forum Members and Loyal Newegg Patrons!
Thanks guys and gals for bringing this matter to our attention. First off, we’d like to apologize for any confusion or inconvenience to anyone out there who has experienced the issues described.
Our IT Department has been working around the clock to investigate the issues described.
Here's the latest: We've just made a few small adjustments to our server as of yesterday (Thurs 7/13). If you want to help out IT department out, let us know if you are still experiencing the same problems as mentioned in this thread. We'll pass on any information you guys provide us with to our IT department for fine-tuning. Thanks for your help!
[code:1:0a9098653c]Tracing route to newegg.com [216.52.208.187]
over a maximum of 30 hops:
1 10 ms 11 ms 7 ms 10.106.32.1
2 11 ms 9 ms 9 ms ge0-2-lbrtnysau-ubr1.hvc.rr.com [24.164.160.186]
3 9 ms 9 ms 11 ms ge0-2-lbrtnysau-ubr2.hvc.rr.com [24.164.160.190]
4 11 ms 11 ms 11 ms ge4-2.lbrtnynwb-rtr1.hvc.rr.com [24.164.160.70]
5 14 ms 14 ms 13 ms pos6-1-nycmnyrdc-rtr1.nyc.rr.com [24.164.160.42]
6 14 ms 18 ms 15 ms tenge-0-0-0.nwrknjmd-rtr.nyc.rr.com [24.29.119.9
4]
7 15 ms 28 ms 15 ms 4.79.188.37
8 15 ms 13 ms 27 ms ae-2-56.bbr2.Newark1.Level3.net [4.68.99.161]
9 83 ms 82 ms 82 ms as-0-0.bbr1.LosAngeles1.Level3.net [64.159.1.157
]
10 93 ms 90 ms 92 ms ae-12-55.car2.LosAngeles1.Level3.net [4.68.102.1
41]
11 94 ms 92 ms 93 ms INTERNAP-NE.car2.Level3.net [4.71.36.78]
12 93 ms 92 ms 95 ms border1.po2-bbnet2.ext1a.lax.pnap.net [216.52.25
5.95]
13 abs-4.border1.ext1a.lax.pnap.net [64.94.111.114] reports: Destination net
unreachable.
Greetings TomsHardware Forum Members and Loyal Newegg Patrons!
Thanks guys and gals for bringing this matter to our attention. First off, we’d like to apologize for any confusion or inconvenience to anyone out there who has experienced the issues described.
Our IT Department has been working around the clock to investigate the issues described.
Here's the latest: We've just made a few small adjustments to our server as of yesterday (Thurs 7/13). If you want to help out IT department out, let us know if you are still experiencing the same problems as mentioned in this thread. We'll pass on any information you guys provide us with to our IT department for fine-tuning. Thanks for your help!
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Administrator>ping www.newegg.com
Pinging www.newegg.com [204.14.213.185] with 32 bytes of data:
Reply from 204.14.213.185: bytes=32 time=60ms TTL=246
Reply from 204.14.213.185: bytes=32 time=60ms TTL=246
Reply from 204.14.213.185: bytes=32 time=55ms TTL=246
Reply from 204.14.213.185: bytes=32 time=64ms TTL=246
Ping statistics for 204.14.213.185:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 55ms, Maximum = 64ms, Average = 59ms
C:\Documents and Settings\Administrator>ping www.google.com
Pinging www.l.google.com [209.85.225.104] with 32 bytes of data:
Reply from 209.85.225.104: bytes=32 time=55ms TTL=244
Reply from 209.85.225.104: bytes=32 time=58ms TTL=244
Reply from 209.85.225.104: bytes=32 time=70ms TTL=244
Reply from 209.85.225.104: bytes=32 time=60ms TTL=244
Ping statistics for 209.85.225.104:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 55ms, Maximum = 70ms, Average = 60ms
C:\Documents and Settings\Administrator>tracert newegg.com
Tracing route to newegg.com [216.52.208.187]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 26 ms 23 ms 6 ms 10.22.128.1
3 29 ms 23 ms 26 ms dal-edge-14.inet.qwest.net [65.127.84.157]
4 13 ms 20 ms 14 ms dap-brdr-03.inet.qwest.net [67.14.2.85]
5 17 ms 23 ms 18 ms 63.146.27.126
6 34 ms 25 ms 24 ms 0.ge-1-1-0.XL3.DFW7.ALTER.NET [152.63.96.46]
7 49 ms 51 ms 56 ms 0.so-7-0-0.XL3.LAX15.ALTER.NET [152.63.112.53]
8 61 ms 59 ms 69 ms internapGIGE-gw.customer.alter.net [157.130.236.
110]
9 63 ms 58 ms 51 ms border2.po1-4g-bbnet1.ext1a.lax.pnap.net [216.52
.255.32]
10 * * * Request timed out.
11 * abs-6.ext1a.lax.pnap.net [216.52.220.234] reports: Destination ne
t unreachable.
Trace complete.
C:\Documents and Settings\Administrator>tracert newegg.com
Tracing route to newegg.com [216.52.208.187]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 8 ms 8 ms 10.22.128.1
3 12 ms 15 ms 17 ms dal-edge-14.inet.qwest.net [65.127.84.157]
4 13 ms 11 ms 12 ms dap-brdr-03.inet.qwest.net [67.14.2.85]
5 23 ms 29 ms 29 ms 63.146.27.126
6 18 ms 11 ms 12 ms 0.ge-1-1-0.XL3.DFW7.ALTER.NET [152.63.96.46]
7 52 ms 58 ms 54 ms 0.so-7-0-0.XL3.LAX15.ALTER.NET [152.63.112.53]
8 54 ms 56 ms 84 ms internapGIGE-gw.customer.alter.net [157.130.236.
110]
9 53 ms 50 ms 58 ms border2.po1-4g-bbnet1.ext1a.lax.pnap.net [216.52
.255.32]
10 * * * Request timed out.
11 abs-6.ext1a.lax.pnap.net [216.52.220.234] reports: Destination net unreach
able.
Trace complete.
C:\Documents and Settings\Administrator>
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Administrator>ping 216.52.220.234
Pinging 216.52.220.234 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 216.52.220.234: Destination net unreachable.
Request timed out.
Ping statistics for 216.52.220.234:
Packets: Sent = 4, Received = 1, Lost = 3 (75% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms