Destination Net Unreachable

[eelozano]

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.

 

[Madwand]

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.

 

[blue68f100]

If your tranmission packes are to large you will get a time out. Try lowering your MTU to 1400. This is normally located in the wan advance section.

I hope this helps.

And DslReports has a tools section that may help you diag your problem.

It also be that the side is busy.

 

[Newegg_Support]

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!

 

[SniperSteve]

[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.

Trace complete.[/code:1:0a9098653c]

I also have this issue. See above.

 

[Trooper170]

Pinging www.newegg.com [216.52.208.185] with 32 bytes of data:
Reply from 216.52.220.234: Destination net unreachable.
Request timed out.
Request timed out.
Reply from 216.52.220.234: Destination net unreachable.

Ping statistics for 216.52.208.185:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),

Tracing route to www.newegg.com [216.52.208.185]
over a maximum of 30 hops:

15 79 ms 79 ms 79 ms ae1.cr2.lax112.us.above.net [64.125.31.234]
16 107 ms 86 ms 81 ms xe-1-0-1.er4.lax112.us.above.net [64.125.30.169]

17 87 ms 92 ms 94 ms 208.184.110.86.IPYX-072053-006-ZYO.above.net [20
8.184.110.86]
18 79 ms 79 ms 80 ms core1.po2-20g-bbnet2.lax012.pnap.net [216.52.255
.73]
19 78 ms 85 ms 88 ms border3.po2-20g-bbnet2.lax010.pnap.net [216.52.2
55.101]
20 abs-11.lax010.pnap.net [216.52.220.234] reports: Destination net unreachab
le.

Trace complete.

I have this issue as well. ping and tracert above.

 

[Kewlx25]

Talk about one heck of a thread necro.

Anyway, that error is when a router can't figure out where to send a packet. This can typically happen for certain IP addresses that may technically be public, but they're not being advertised for one reason or another.

This generally does not happen and should not be happening for a site. This is probably caused by a lost link and *should* fix itself in 5-10 minutes or misconfigured routing info.

I tired doing a ping and tracert, got the exact same issue, yet the website was working. When trying to use another tool to diagnose, the IP address returned by newegg.com changed and now pings are working just fine......???